<?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">J Med Internet Res</journal-id><journal-id journal-id-type="publisher-id">jmir</journal-id><journal-id journal-id-type="index">1</journal-id><journal-title>Journal of Medical Internet Research</journal-title><abbrev-journal-title>J Med Internet Res</abbrev-journal-title><issn pub-type="epub">1438-8871</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v28i1e96098</article-id><article-id pub-id-type="doi">10.2196/96098</article-id><article-categories><subj-group subj-group-type="heading"><subject>Review</subject></subj-group></article-categories><title-group><article-title>Blockchain for Digital Health Governance: Evidence Gap Map and Scoping Review</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Yaghobian</surname><given-names>Sarina</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sulkowski</surname><given-names>Nina</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Galambos</surname><given-names>Gary</given-names></name><degrees>Prof Dr Med, MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Scarazzini</surname><given-names>Linda</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Maloumian</surname><given-names>Nicolas</given-names></name><degrees>MSc, MA, MBA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Verhaeghe</surname><given-names>Stephane</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib></contrib-group><aff id="aff1"><institution>T&#x00E9;l&#x00E9;m&#x00E9;decine 360, TLM360 SAS</institution><addr-line>55 Avenue Marceau</addr-line><addr-line>Paris</addr-line><addr-line>Ile-de-France</addr-line><country>France</country></aff><aff id="aff2"><institution>Independent researcher</institution><addr-line>Sydney</addr-line><addr-line>NSW</addr-line><country>Australia</country></aff><aff id="aff3"><institution>Department of Psychiatry, The University of Notre Dame Australia</institution><addr-line>Sydney</addr-line><addr-line>NSW</addr-line><country>Australia</country></aff><aff id="aff4"><institution>Lewis Katz School of Medicine, Temple University</institution><addr-line>Philadelphia</addr-line><addr-line>PA</addr-line><country>United States</country></aff><aff id="aff5"><institution>School of Medicine, Adelaide University</institution><addr-line>Adelaide</addr-line><addr-line>South Australia</addr-line><country>Australia</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Brini</surname><given-names>Stefano</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Golamari</surname><given-names>Bala Vinay Kumar</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Pavaloiu</surname><given-names>Ionel-Bujorel</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Sarina Yaghobian, MSc, T&#x00E9;l&#x00E9;m&#x00E9;decine 360, TLM360 SAS,, 55 Avenue Marceau, Paris, Ile-de-France, 75116, France, 33 643610937; <email>sarinayag@gmail.com</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>7</day><month>10</month><year>2026</year></pub-date><volume>28</volume><elocation-id>e96098</elocation-id><history><date date-type="received"><day>25</day><month>03</month><year>2026</year></date><date date-type="rev-recd"><day>13</day><month>08</month><year>2026</year></date><date date-type="accepted"><day>19</day><month>08</month><year>2026</year></date></history><copyright-statement>&#x00A9; Sarina Yaghobian, Nina Sulkowski, Gary Galambos, Linda Scarazzini, Nicolas Maloumian, Stephane Verhaeghe. Originally published in the Journal of Medical Internet Research (<ext-link ext-link-type="uri" xlink:href="https://www.jmir.org">https://www.jmir.org</ext-link>), 7.10.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 the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/">https://www.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://www.jmir.org/2026/1/e96098"/><abstract><sec><title>Background</title><p>Digital health increasingly depends on data exchange across institutions, technologies, and jurisdictions, creating persistent challenges for the governance of access, consent, interoperability, provenance, and accountability. Blockchain and distributed ledger technology (DLT) systems have been proposed as mechanisms for coordinating and verifying governance processes across distributed actors. However, existing research has examined individual applications or technical domains, leaving unclear how blockchain/DLT systems function as governance infrastructure across health care, and whether these systems have progressed toward real-world implementation.</p></sec><sec><title>Objective</title><p>This evidence gap map and scoping review aim to characterize how blockchain/DLT systems are applied to health data governance, identify the health care application domains, and governance functions addressed by these systems, and assess their evidence maturity.</p></sec><sec sec-type="methods"><title>Methods</title><p>We searched PubMed/MEDLINE, Embase, Scopus, and Dimensions (Digital Science), and conducted backward and forward citation searching to identify peer-reviewed studies reporting blockchain/DLT systems in health care with an implemented artifact, technical evaluation, simulation, benchmark, pilot/usability assessment, or operational deployment, published between January 1, 2010, and February 28, 2026. Conceptual or architecture-only papers were excluded. Studies were charted by application domain, governance function, and evidence maturity (proof-of-concept/prototype, simulated/benchmarked evaluation, pilot/usability-tested implementation, or operational/real-world deployment). A focused narrative synthesis was conducted for studies reporting pilot/usability-tested implementation or operational/real-world deployment.</p></sec><sec sec-type="results"><title>Results</title><p>Of 892 included studies, the evidence base was dominated by proof-of-concept/prototype (n=418) and simulated/benchmarked evaluation (n=455) work; only 18 reported pilot/usability-tested implementation, and 1 reported operational/real-world deployment. Studies were concentrated in electronic health record management/health information exchange (n=372) and telemedicine/distributed care/Internet of Things (IoT)&#x2013;enabled remote monitoring (n=250), followed by clinical decision support/smart health care (n=82), public health surveillance/certification (n=72), clinical trials/research governance (n=67), and health data marketplace/monetization (n=49). Across 3273 nonmutually exclusive governance-function codes, the most frequent functions were privacy/security, interoperability/data sharing, access control, data/model integrity, and identity/authentication. Publication activity increased over time, with the highest annual volumes in 2022 and 2025. This growth was not accompanied by a shift toward higher-maturity evidence. Privacy/security and interoperability/data sharing remained prominent across publication years, while other governance functions varied over time. Higher-maturity evidence was unevenly distributed across application domains, particularly clinical trials/research governance and electronic health record management/health information exchange. Within the 19 higher-maturity studies, evidence remained limited by small-scale evaluations, short follow-up, and a lack of sustained routine use beyond the evaluation period.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Across digital health, blockchain/DLT systems were positioned as governance infrastructure for verifiable access, consent, provenance, identity, and audit trails, rather than as repositories for health data. Despite a growing literature, real-world implementation evidence remained limited. Whether blockchain/DLT systems improve governance outcomes over conventional architectures remains largely untested. Future research should prioritize comparative, implementation-focused evaluation of whether these systems can be integrated, sustained, and shown to provide governance benefits in real-world settings.</p></sec></abstract><kwd-group><kwd>blockchain</kwd><kwd>distributed ledger technology</kwd><kwd>digital health</kwd><kwd>data governance</kwd><kwd>scoping review</kwd><kwd>evidence gap map</kwd><kwd>interoperability</kwd><kwd>health information exchange</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>The rapid digitalization of health care has transformed how health information is generated, exchanged, and reused across clinical care, research, and public health. Electronic health records (EHRs), remote monitoring technologies, connected devices, and AI-enabled analytics have expanded opportunities for data sharing and coordination. However, their use has brought challenges related to interoperability, trust, and accountability into sharper focus [<xref ref-type="bibr" rid="ref1">1</xref>]. Health information remains fragmented across institutions and jurisdictions, complicating data exchange and dispersing responsibility for access, consent, and oversight. Regulatory initiatives such as the European Health Data Space (EHDS) reflect growing recognition that secure and accountable secondary use of health data depends on effective governance [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>].</p><p>These challenges also extend beyond technical considerations. Digital health systems depend on patients&#x2019; ability and willingness to engage with their care and their trust in how their data are used. This is particularly relevant to chronic disease management, a major application of remote monitoring and other digital health technologies [<xref ref-type="bibr" rid="ref4">4</xref>]. In a recent Organisation for Economic Co-operation and Development (OECD) survey examining people-centered and coordinated care across 19 countries, 58.9% of primary care patients living with chronic conditions reported feeling confident managing their own health [<xref ref-type="bibr" rid="ref5">5</xref>]. Trust in digital health, shaped by concerns about privacy, data use, accuracy, and accountability, remains a key determinant of adoption [<xref ref-type="bibr" rid="ref6">6</xref>]. Together, these considerations reinforce the need for clear rules governing who may access health data, for what purposes, under what conditions, and through which mechanisms of oversight.</p><p>Governance, as used here, refers to the rules, processes, and accountability mechanisms that shape how health data are accessed, shared, controlled, and monitored across actors and organizations [<xref ref-type="bibr" rid="ref7">7</xref>-<xref ref-type="bibr" rid="ref9">9</xref>]. Proprietary platforms and siloed infrastructures continue to impede data sharing [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], while the increasing use of health data for secondary purposes raises concerns about transparency, consent, oversight, and patient control. Effective governance must therefore balance data access for care, research, and innovation with legal, ethical, and privacy obligations.</p><p>Distributed ledger technology (DLT) systems, including blockchain, have been proposed as a means of supporting some of these governance functions [<xref ref-type="bibr" rid="ref10">10</xref>]. Blockchain systems create tamper-evident, time-stamped records and can support programmable rules for data access and exchange [<xref ref-type="bibr" rid="ref11">11</xref>]. These properties have prompted applications in consent management, access control, identity verification, provenance tracking, auditability, and cross-organizational coordination [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. Although pilot implementations have demonstrated technical feasibility in areas such as health information exchange, clinical trials, and patient-controlled data sharing, evidence of sustained real-world implementation remains limited [<xref ref-type="bibr" rid="ref15">15</xref>].</p><p>A substantial body of literature has examined blockchain applications in health care [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>] and within specific areas, including EHR interoperability [<xref ref-type="bibr" rid="ref18">18</xref>], patient care [<xref ref-type="bibr" rid="ref19">19</xref>], design choices and implementation trade-offs [<xref ref-type="bibr" rid="ref20">20</xref>], genomics [<xref ref-type="bibr" rid="ref21">21</xref>], consent management [<xref ref-type="bibr" rid="ref22">22</xref>], and COVID-19-related applications [<xref ref-type="bibr" rid="ref23">23</xref>]. Recent reviews have assessed health care blockchain implementation and performance more generally [<xref ref-type="bibr" rid="ref24">24</xref>]. However, existing reviews remain largely organized around specific applications, clinical domains, or technical architectures. Governance functions are generally discussed within individual use cases rather than systematically compared across digital health contexts, and their relationship with evidence maturity remains unclear.</p><p>We therefore conducted an evidence gap map and scoping review of blockchain/DLT applications in digital health governance. The objectives of this study were to identify recurring governance functions, map evidence maturity across health care domains, and highlight priorities for future research, implementation, and policy.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Protocol and Registration</title><p>This scoping review was reported in accordance with the PRISMA-ScR (Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for Scoping Reviews; <xref ref-type="supplementary-material" rid="app5">Checklist 1</xref>) [<xref ref-type="bibr" rid="ref25">25</xref>]. The search strategy was reported in accordance with the PRISMA-S (Preferred Reporting Items for Systematic Reviews and Meta-Analyses literature search extension) to improve transparency and reproducibility [<xref ref-type="bibr" rid="ref26">26</xref>]. A scoping review design was selected given that the literature on blockchain/DLT systems in digital health is heterogeneous. A protocol was not registered.</p><p>We aimed to map and synthesize peer-reviewed literature on blockchain/DLT systems in digital health governance. Specifically, we examined recurring governance functions, implementation patterns, evidence maturity, and limitations across health care application domains. Governance-layer infrastructure was defined as systems that record, verify, or coordinate permissions, access events, consent decisions, provenance, and audit trails across distributed actors, rather than storing clinical data. In this study, &#x201C;on-chain&#x201D; refers to information recorded directly on a blockchain/DLT, whereas &#x201C;off-chain&#x201D; refers to data stored outside the ledger, such as in clinical databases, institutional repositories, cloud storage, or distributed file systems. In these architectures, the ledger typically records hashes, permissions, metadata, transactions, or consent events.</p></sec><sec id="s2-2"><title>Eligibility Criteria</title><p>Eligibility criteria were structured using the population/concept/context approach recommended for scoping reviews [<xref ref-type="bibr" rid="ref25">25</xref>]. Studies were included if they (1) examined blockchain/DLT systems, smart contracts, or decentralized ledger infrastructure; (2) were situated within health care, medicine, public health, digital health, telemedicine, clinical research, AI in health, EHR, or health data exchange; (3) addressed at least one governance-related function, including data sharing, consent management, access control, auditability, accountability, identity management, provenance, interoperability, regulatory compliance, data stewardship, or cross-organizational coordination; (4) reported an implemented or evaluated system, including a prototype, simulation, benchmark, pilot, usability study, evaluation study, or operational implementation; and (5) were peer-reviewed publications in English published within the specified date range. Reviews were used to inform the background, search strategy, and backward and forward citation searching but were not included as primary evidence records. Gray literature was excluded to support reproducibility and consistency in eligibility assessment, given the substantial variation in reporting detail, methodological transparency, and implementation verification across nonpeer-reviewed sources.</p><p>Studies were excluded if they (1) did not examine blockchain, DLT, smart contracts, or decentralized ledger mechanisms; (2) were not situated within a relevant health care or digital health context; (3) focused exclusively on cryptocurrency, finance, nonhealth care supply chains, logistics, education, or other nonhealth care applications; (4) focused solely on cryptographic design, consensus algorithms, performance optimization, or technical engineering without relevance to governance; (5) did not address any governance-related function; (6) were conceptual, theoretical, or architecture-only papers that did not report an implemented artifact, simulation, benchmark, pilot, usability assessment, evaluation, or operational deployment; (7) were editorials, commentaries, opinion pieces, news items, dissertations, theses, preprints, white papers, book chapters, conference abstracts without sufficient detail, or other nonpeer-reviewed sources; (8) were retracted, withdrawn, or otherwise invalid publications; or (9) were not published in English or fell outside the inclusion date range.</p></sec><sec id="s2-3"><title>Information Sources</title><p>Searches were conducted in PubMed/MEDLINE, Embase via Ovid, Scopus, and Dimensions (Digital Science). Searches were limited to English-language publications from January 1, 2010, to February 28, 2026. Peer-review status was assessed during eligibility screening. The final database searches were conducted on May 25, 2026.</p><p>Supplementary searching was conducted through backward and forward citation searching. Backward citation searching involved screening the reference lists of included studies and relevant review articles. Forward citation searching was conducted using Dimensions to identify citing articles. Records identified through citation searching were deduplicated and screened using the same eligibility criteria as database-derived records.</p></sec><sec id="s2-4"><title>Search</title><p>The search strategy was developed using controlled vocabulary terms and free-text synonyms for three core concepts: (1) blockchain/DLT systems; (2) health care and digital health contexts; and (3) governance-related functions. Search terms were informed by seed articles, prior reviews, and terminology identified in titles, abstracts, index terms, and author keywords.</p><p>Across databases, the search used synonyms and related terms for blockchain technologies, including &#x201C;blockchain,&#x201D; &#x201C;distributed ledger,&#x201D; &#x201C;distributed ledger technology,&#x201D; &#x201C;smart contract,&#x201D; &#x201C;decentralized identity,&#x201D; &#x201C;self-sovereign identity,&#x201D; &#x201C;tokenization,&#x201D; and &#x201C;Web3&#x201D;; health care terms, including &#x201C;digital health,&#x201D; &#x201C;eHealth,&#x201D; &#x201C;mHealth,&#x201D; &#x201C;telemedicine,&#x201D; &#x201C;telehealth,&#x201D; &#x201C;electronic health records,&#x201D; &#x201C;clinical trial,&#x201D; &#x201C;biomedical research,&#x201D; &#x201C;artificial intelligence,&#x201D; &#x201C;machine learning,&#x201D; and &#x201C;health data&#x201D;; and governance-related terms, including &#x201C;data governance,&#x201D; &#x201C;consent,&#x201D; &#x201C;dynamic consent,&#x201D; &#x201C;access control,&#x201D; &#x201C;audit trail,&#x201D; &#x201C;auditability,&#x201D; &#x201C;provenance,&#x201D; &#x201C;traceability,&#x201D; &#x201C;interoperability,&#x201D; &#x201C;privacy,&#x201D; &#x201C;security,&#x201D; &#x201C;accountability,&#x201D; &#x201C;regulation,&#x201D; &#x201C;regulatory compliance,&#x201D; &#x201C;data stewardship,&#x201D; &#x201C;data sharing,&#x201D; &#x201C;data exchange,&#x201D; and &#x201C;health information exchange.&#x201D;</p><p>PubMed/MEDLINE and Embase searches via Ovid combined controlled vocabulary terms, including MeSH and Emtree terms, along with free-text terms. Scopus searches were conducted in the title, abstract, and keyword fields, and Dimensions searches were conducted in the title and abstract fields. Fully reproducible database-specific search strategies, including field tags, controlled vocabulary terms, date and language limits, search dates, and records retrieved, are provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. The overall database search structure is summarized in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p></sec><sec id="s2-5"><title>Selection of Sources of Evidence</title><p>All records identified through database searching and supplementary citation searching were imported into Rayyan (Qatar Computing Research Institute) for deduplication and screening. Duplicate records were removed before title and abstract screening. Two reviewers independently screened titles and abstracts against the eligibility criteria. Records that met the inclusion criteria, or for which eligibility could not be determined from the title and abstract alone, were retained for full-text review.</p><p>Full-text articles were independently assessed by the same reviewers. During full-text screening, records were also checked for retraction, withdrawal, or an invalid publication status, and any such records were excluded. Records identified through backward and forward citation searching were screened using the same eligibility criteria as database-derived records. Disagreements at both screening stages were resolved through discussion and consensus. The study selection process, including the numbers of records identified, screened, assessed for eligibility, excluded, and included, is reported in the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flow diagram.</p></sec><sec id="s2-6"><title>Data Charting Process</title><p>A standardized data charting form was developed and piloted on a subset of included studies. The form was refined during piloting to ensure that it captured both descriptive study characteristics and governance-related information relevant to the review objectives. Data charting was performed by one reviewer and checked by a second reviewer for completeness and consistency. Discrepancies were resolved through discussion and consensus.</p></sec><sec id="s2-7"><title>Data Items</title><p>Extracted data included bibliographic information, year of publication, publication type, study design, health care or digital health context, application domain, governance challenge addressed, blockchain/DLT mechanism described, on-chain or off-chain architecture, where reported, implementation status and follow-up, evaluation methods, reported outcomes, limitations, and relevance to cross-domain governance functions. Evidence maturity was categorized as proof-of-concept/prototype, simulated/benchmarked evaluation, pilot/usability-tested implementation, or operational/real-world deployment.</p></sec><sec id="s2-8"><title>Critical Appraisal of Individual Sources of Evidence</title><p>A formal risk-of-bias assessment was not conducted because the included literature was methodologically heterogeneous and consisted largely of system design studies, prototypes, simulated/benchmarked evaluations, and early-stage pilot implementations for which standard risk-of-bias tools are not typically applicable. Consistent with the purpose of a scoping review, studies were not excluded on the basis of methodological quality.</p></sec><sec id="s2-9"><title>Synthesis of Results</title><p>Data were synthesized using a thematic approach. First, studies were mapped by health care application domain, governance function, and evidence maturity to develop the evidence gap map. This mapping was used to identify areas with concentrated evidence, areas dominated by proof-of-concept/prototype studies or simulations/benchmarked evaluations, and areas where pilot/usability-tested implementation and operational/real-world deployment evidence remains limited.</p><p>Because the mapped evidence base was large and heterogeneous, the focused narrative synthesis was restricted to studies reporting pilot/usability-tested implementation or operational/real-world deployment. Proof-of-concept/prototype studies and simulated/benchmarked evaluations were retained in the evidence gap map but were not included in the focused narrative synthesis.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Study Selection</title><p>Database searches identified 12,016 records: 1727 from PubMed/MEDLINE, 2827 from Embase via Ovid, 3777 from Scopus, and 3685 from Dimensions (<xref ref-type="fig" rid="figure1">Figure 1</xref>). After the removal of 4916 duplicate records, 7100 records were screened by title and abstract. Of these, 5552 were excluded, leaving 1548 full-text articles for eligibility assessment. All 1548 full-text articles were retrieved and assessed.</p><p>Following full-text assessment of the database-derived records, 888 studies met the inclusion criteria. Backward and forward citation searching identified 145 additional records. After deduplication and screening, 6 full-text articles were assessed, of which 4 met the inclusion criteria and 2 were excluded. Overall, 892 studies were included in the evidence gap map. Of these, 19 studies reported pilot/usability-tested implementation or operational/real-world deployment and were included in the focused narrative synthesis. The complete list of included studies and their classifications by health care application domain, governance function, and evidence-maturity category is provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) 2020 flow diagram of the study selection for blockchain/distributed ledger technology (DLT) systems in digital health governance. <sup>a</sup>Studies that reported an implemented artifact, technical evaluation, pilot/usability assessment, or operational deployment were included. <sup>b</sup>The wrong publication type category included reviews, editorials, commentaries, opinion pieces, letters, protocols, conference abstracts without sufficient methodological detail, and other nonprimary research outputs.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e96098_fig01.png"/></fig></sec><sec id="s3-2"><title>Evidence Gap Map: Application Domains, Governance Functions, and Evidence Maturity</title><p>The evidence base remained concentrated in early-stage and technical-evaluation studies. Overall, 418 studies were categorized as proof-of-concept/prototype studies, and 455 as simulated/benchmarked evaluations. Eighteen studies reported pilot/usability-tested implementation, and 1 reported an operational/real-world deployment (<xref ref-type="fig" rid="figure2">Figure 2A</xref>).</p><p>Studies were distributed across 6 health care application domains: EHR management and health information exchange (n=372), telemedicine/distributed care/Internet of Things (IoT)&#x2013;enabled remote monitoring (n=250), clinical decision support/smart health care (n=82), public health surveillance/certification (n=72), clinical trials/research governance (n=67), and health data marketplace/monetization (n=49; <xref ref-type="fig" rid="figure2">Figure 2A</xref>).</p><p>Across domains, pilot/usability-tested implementation or operational/real-world deployment evidence remained limited and unevenly distributed. EHR management/health information exchange included 6 pilot/usability-tested implementation studies. Telemedicine/distributed care/IoT-enabled remote monitoring included 1 pilot/usability-tested implementation study and 1 operational/real-world deployment study. Clinical trials/research governance included 9 pilot/usability-tested implementation studies. Health data marketplace/monetization and clinical decision support/smart health care each included 1 pilot/usability-tested implementation study. No public health surveillance/certification studies were classified as higher maturity. Blockchain/DLT systems had, therefore, been proposed and technically evaluated across all 6 domains, but implementation evidence remained scarce.</p><p>Governance functions were coded as nonmutually exclusive because individual studies often addressed more than 1 governance mechanism. Across the included studies, 3273 governance-function codes were identified. The most frequent functions were privacy/security (n=750), interoperability/data sharing (n=679), access control (n=420), data/model integrity (n=386), and identity/authentication (n=349). Less frequent functions included auditability (n=224), AI/data governance (n=135), provenance/traceability (n=103), accountability/compliance (n=100), consent management (n=68), and incentives/value exchange (n=59). Governance-function codes were concentrated in proof-of-concept/prototype studies and simulated/benchmarked evaluations, with substantially fewer codes identified in pilot/usability-tested implementation or operational/real-world deployment studies (<xref ref-type="fig" rid="figure2">Figure 2B</xref>).</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Evidence maturity of blockchain/distributed ledger technology studies by health care application domain (panel A) and governance function (panel B). Cell values indicate the number of included studies. Evidence maturity was categorized as proof-of-concept/prototype, simulated/benchmarked evaluation, pilot/usability-tested implementation, or operational/real-world deployment<italic>.</italic> EHR: electronic health record; IoT: Internet of Things.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e96098_fig02.png"/></fig></sec><sec id="s3-3"><title>Governance Functions Across Health Care Application Domains</title><p>Governance functions were most frequently mapped to EHR management/health information exchange and telemedicine/distributed care/IoT-enabled remote monitoring (<xref ref-type="fig" rid="figure3">Figure 3</xref>). Across domains, privacy/security and interoperability/data sharing were the most widely represented functions, while the distribution of other functions varied by application domain.</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Distribution of blockchain-enabled governance functions across health care application domains. Cell values indicate the number of governance-function codes within each health care application domain. Governance functions were coded as nonmutually exclusive; individual studies could contribute to more than 1 function<italic>.</italic> EHR: electronic health record; IoT: Internet of Things.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e96098_fig03.png"/></fig></sec><sec id="s3-4"><title>Temporal Distribution of the Evidence Base</title><p>Publication activity increased from 2017, with the highest annual volumes observed in 2022 and 2025, while the distribution of evidence maturity remained broadly similar over time. Proof-of-concept/prototype studies and simulated/benchmarked evaluations predominated across publication years, whereas pilot/usability-tested implementation studies remained uncommon and operational/real-world deployment was rare (<xref ref-type="fig" rid="figure4">Figure 4</xref>).</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Temporal distribution of included blockchain/distributed ledger technology studies by publication volume (panel A) and evidence maturity (panel B). <sup>a</sup>2026 includes only publications through February 28, 2026.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e96098_fig04.png"/></fig><p>The temporal distribution of governance functions showed that privacy/security and interoperability/data sharing remained prominent across publication years, while the representation of other governance functions, including AI/data governance, accountability/compliance, consent management, and provenance/traceability, varied over time (<xref ref-type="fig" rid="figure5">Figure 5</xref>).</p><fig position="float" id="figure5"><label>Figure 5.</label><caption><p>Temporal distribution of governance functions addressed by blockchain/distributed ledger technology studies. <sup>a</sup>2026 includes only publications through February 28, 2026. Governance functions were nonmutually exclusive; individual studies could contribute to more than 1 function. Bubble size and color intensity indicate the number of governance-function codes within each publication year.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v28i1e96098_fig05.png"/></fig></sec><sec id="s3-5"><title>Domain-Level Synthesis of Governance Mechanisms</title><p>Across health care application domains, blockchain/DLT systems were primarily positioned as infrastructure for coordinating and verifying data-related governance processes among distributed actors, with more specific roles varying by context. EHR/health information exchange studies focused on fragmented records, interoperability, and access permissions; telemedicine/distributed care/IoT-enabled remote monitoring studies emphasized identity, authentication, and secure patient-generated data flows; clinical trials/research governance studies addressed transparency, consent, and auditability; public health surveillance/certification studies focused on verification, certification, and cross-institutional trust; clinical decision support/smart health care studies emphasized provenance, data integrity, and accountability in AI-enabled workflows; and health data marketplace/monetization studies focused on patient control, consent, and value distribution.</p><p>Across domains, blockchain/DLT systems were mostly used as a coordination and verification layer rather than repositories for identifiable clinical data. Recurring mechanisms included access-control logging, consent recording, identity/authentication, auditability, provenance tracking, integrity verification, and interoperability support. <xref ref-type="table" rid="table1">Table 1</xref> summarizes the main governance challenges, blockchain-enabled mechanisms, evidence maturity, and remaining limitations across the 6 health care application domains.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Domain-level synthesis of governance challenges, blockchain-enabled mechanisms, and evidence maturity across digital health application domains<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup>.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain</td><td align="left" valign="bottom">Key governance challenges</td><td align="left" valign="bottom">Blockchain-enabled governance mechanisms</td><td align="left" valign="bottom">Evidence maturity and limitations</td></tr></thead><tbody><tr><td align="left" valign="top">EHR<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup> management/health information exchange (n=372)</td><td align="left" valign="top">Fragmented records; limited interoperability; insecure data exchange; unclear access permissions across institutions</td><td align="left" valign="top">Permissioned data exchange; access-control logs; patient-mediated sharing; on-chain hashes or transaction records; off-chain EHR storage</td><td align="left" valign="top">Largest domain; dominated by proof-of-concept/prototype and simulated/benchmarked evaluation studies; limited pilot/usability-tested implementation or operational/real-world deployment evidence; persistent integration challenges with existing EHR infrastructure</td></tr><tr><td align="left" valign="top">Telemedicine/distributed care/IoT<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup>-enabled remote monitoring (n=250)</td><td align="left" valign="top">Remote identity verification; device authentication; insecure patient-generated data flows; fragmented patient-provider interactions</td><td align="left" valign="top">Decentralized identity; secure remote data exchange; authentication of patients, providers, and devices; smart-contract access permissions</td><td align="left" valign="top">Substantial technical evidence, mainly proof-of-concept/prototype and simulated/benchmarked evaluation studies; limited pilot/usability-tested implementation and operational/real-world deployment evidence; barriers in scalability, latency, and interoperability</td></tr><tr><td align="left" valign="top">Clinical decision support/smart health care (n=82)</td><td align="left" valign="top">Data provenance for AI/ML<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup>; secure model training; accountability for data/model use; fragmented data pipelines</td><td align="left" valign="top">Blockchain-enabled federated learning coordination; audit trails for data/model processes; data integrity verification; smart-contract access control</td><td align="left" valign="top">Emerging and technically focused domain; mostly simulated/benchmarked studies; very limited pilot/usability-tested evidence; blockchain&#x2019;s role in addressing model bias, data quality, or clinical effectiveness remains unevaluated</td></tr><tr><td align="left" valign="top">Public health surveillance/certification (n=72)</td><td align="left" valign="top">Verification of test or vaccination records; public-health data integrity; privacy-preserving certification; cross-border or cross-institutional trust</td><td align="left" valign="top">Verifiable credentials; tamper-evident certificates; identity/authentication systems; privacy-preserving data exchange; audit trails</td><td align="left" valign="top">Evidence concentrated in proof-of-concept/prototype and simulated/benchmarked evaluation studies; no confirmed pilot/usability-tested implementation or operational/real-world deployment evidence as a primary domain; implementation depends heavily on legal, institutional, and public-trust conditions</td></tr><tr><td align="left" valign="top">Clinical trials/research governance (n=67)</td><td align="left" valign="top">Trial transparency; protocol adherence; consent management; data integrity; auditability across multicenter research</td><td align="left" valign="top">Smart contracts for protocol rules; dynamic consent platforms; immutable audit trails; time-stamped records of research events and data access</td><td align="left" valign="top">Smaller but governance-relevant domain; comparatively higher concentration of pilot/usability-tested implementation studies; limited integration into routine trial infrastructure; regulatory and institutional adoption remain uncertain</td></tr><tr><td align="left" valign="top">Health data marketplace/monetization (n=49)</td><td align="left" valign="top">Patient control over secondary data use; transparency of data transactions; value distribution; consent tracking; risk of commodification</td><td align="left" valign="top">Tokenized data exchange; smart-contract payments or permissions; decentralized<break/>marketplaces; consent tracking; incentive mechanisms</td><td align="left" valign="top">Smallest domain; mostly proof-of-concept/prototype and simulated/benchmarked evaluation studies; limited pilot/usability-tested implementation evidence; no operational/real-world deployment; ethical, regulatory, and equity concerns remain unresolved</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>Domains are ordered by the number of included studies (n).</p></fn><fn id="table1fn2"><p><sup>b</sup>EHR: electronic health record.</p></fn><fn id="table1fn3"><p><sup>c</sup>IoT: Internet of Things.</p></fn><fn id="table1fn4"><p><sup>d</sup>ML: machine learning.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-6"><title>Characteristics and Focused Synthesis of Higher-Maturity Studies</title><p><xref ref-type="table" rid="table2">Table 2</xref> summarizes the 19 studies classified as pilot/usability-tested implementation or operational/real-world deployment and included in the focused narrative synthesis. These studies varied in setting, sample size, duration, evaluation focus, and implementation status and were unevenly distributed across application domains. Full study-level extraction details are provided in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Summary of pilot/usability-tested and operational blockchain/distributed ledger technology studies included in the focused narrative synthesis.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Primary domain</td><td align="left" valign="bottom">Higher-maturity studies<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></td><td align="left" valign="bottom">Main evaluation focus</td><td align="left" valign="bottom">Blockchain/DLT<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup> governance role</td><td align="left" valign="bottom">Main implementation limitations</td></tr></thead><tbody><tr><td align="left" valign="top">EHR<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup> management/health information exchange (n=6)</td><td align="left" valign="top">PatientDataChain (Setrio Soft SRL, Modex Ltd) [<xref ref-type="bibr" rid="ref27">27</xref>]; iWellChain (Taipei Medical University Hospital) [<xref ref-type="bibr" rid="ref28">28</xref>]; Homeless data platform (Dell Medical School, The University of Texas at Austin) [<xref ref-type="bibr" rid="ref29">29</xref>]; PAGR<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup> e-prescribing (EirSystem Inc) [<xref ref-type="bibr" rid="ref30">30</xref>]; MediLinker (The University of Texas at Austin) [<xref ref-type="bibr" rid="ref31">31</xref>]; HealthPocket (Seoul National University, MediBloc Inc) [<xref ref-type="bibr" rid="ref32">32</xref>]</td><td align="left" valign="top">System functionality, access logs, feasibility, e-prescribing workflow, usability, and patient-mediated information exchange</td><td align="left" valign="top">Permissioned data sharing, access logging, identity/credential management, consent or authorization recording, and integrity verification</td><td align="left" valign="top">Mostly small pilots or usability studies; limited sites, short follow-up, partial uptake, EHR integration challenges, scalability concerns, and limited evidence of sustained routine use</td></tr><tr><td align="left" valign="top">Telemedicine/distributed care/IoT<sup><xref ref-type="table-fn" rid="table2fn5">e</xref></sup>-enabled remote monitoring (n=2)</td><td align="left" valign="top">Dovetail digital consent (Dovetail Digital Ltd) [<xref ref-type="bibr" rid="ref33">33</xref>]; IoHCS<sup><xref ref-type="table-fn" rid="table2fn6">f</xref></sup>/NUMED System (Naresuan University, 2nd Health Region, Ministry of Public Health) [<xref ref-type="bibr" rid="ref34">34</xref>]</td><td align="left" valign="top">Patient/staff perceptions, staff satisfaction, system performance, and secure remote access</td><td align="left" valign="top">Consent traceability, secure patient-data access, identity and permission control, and cross-provider data availability</td><td align="left" valign="top">Limited independent evaluation of blockchain contribution; scalability, interoperability, technical reliability, and workflow integration remain uncertain</td></tr><tr><td align="left" valign="top">Clinical decision support/smart health care (n=1)</td><td align="left" valign="top">BRCA-CN consortium blockchain (National Institutes for Food and Drug Control [NIFDC]) [<xref ref-type="bibr" rid="ref35">35</xref>]</td><td align="left" valign="top">Cross-institutional BRCA<sup><xref ref-type="table-fn" rid="table2fn7">g</xref></sup> variant interpretation, interlaboratory concordance, VUS<sup><xref ref-type="table-fn" rid="table2fn8">h</xref></sup>-rate reduction, reporting time, expert consensus, and system performance</td><td align="left" valign="top">Multi-institutional consensus coordination, provenance, audit trails, data-sovereignty support, and accountability across laboratories</td><td align="left" valign="top">Limited to 6 laboratories and a defined deployment period; broader geographic representativeness, long-term sustainability, and full implementation of advanced privacy features remain uncertain</td></tr><tr><td align="left" valign="top">Public health surveillance/certification (n=0)</td><td align="left" valign="top">No higher-maturity studies identified</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">Proposed functions in the wider evidence map included certification, verification, privacy-preserving credentials, and surveillance-data integrity</td><td align="left" valign="top">No higher-maturity studies identified; limited evidence of testing with real users, public-health workflows, or health authorities</td></tr><tr><td align="left" valign="top">Clinical trials/research governance (n=9)</td><td align="left" valign="top">SUSMED mobile health (SUSMED Inc) [<xref ref-type="bibr" rid="ref36">36</xref>]; SUSMED regulatory sandbox [<xref ref-type="bibr" rid="ref37">37</xref>]; METORY platform (Jeonbuk National University Hospital and Seoul National University Hospital, Linux Foundation) [<xref ref-type="bibr" rid="ref38">38</xref>]; METORY dynamic-consent trial [<xref ref-type="bibr" rid="ref39">39</xref>]; Boehringer/IBM consent pilot (Boehringer Ingelheim, IBM, Linux Foundation) [<xref ref-type="bibr" rid="ref40">40</xref>]; MediBloc change-monitoring app (Yonsei University College of Medicine and MediBloc Inc)[<xref ref-type="bibr" rid="ref41">41</xref>]; Cancer Gene Trust (University of California) [<xref ref-type="bibr" rid="ref42">42</xref>]; decentralized biobanking app (de-bi, co) [<xref ref-type="bibr" rid="ref43">43</xref>]; MyHealthData platform (Seoul National University Hospital, MediBloc) [<xref ref-type="bibr" rid="ref44">44</xref>]</td><td align="left" valign="top">Data integrity, fraud/tampering detection, electronic consent, protocol amendments, participant engagement, usability, monitoring time/cost, data sharing, and research transparency</td><td align="left" valign="top">Consent/event recording, immutable audit trails, hash-based integrity verification, provenance tracking, participant-facing transparency, and research-data accountability</td><td align="left" valign="top">Mostly pilot/feasibility studies; limited samples; short follow-up; uncertain regulatory acceptance; limited long-term integration into trial infrastructure; unresolved usability/comprehension issues</td></tr><tr><td align="left" valign="top">Health data marketplace/monetization (n=1)</td><td align="left" valign="top">Decentralized biobanking operational-feasibility case study [<xref ref-type="bibr" rid="ref45">45</xref>]</td><td align="left" valign="top">Donor engagement, biospecimen tracking, participant engagement, app uptake, and blockchain-enabled access to specimen information</td><td align="left" valign="top">Transparency, donor recognition, provenance, participant engagement, and foundations for future incentive or data-governance models</td><td align="left" valign="top">Real-world feasibility evidence only; sustainability, governance, workflow integration, communications, ethical oversight, and scalability remain unresolved</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>Developer/supplier information and blockchain platforms are reported as specified in the cited studies; underlying blockchain technologies and technical dependencies are not exhaustively detailed.</p></fn><fn id="table2fn2"><p><sup>b</sup>DLT: distributed ledger technology<italic>.</italic></p></fn><fn id="table2fn3"><p><sup>c</sup>EHR: electronic health record.</p></fn><fn id="table2fn4"><p><sup>d</sup>PAGR: prescription abuse greatly reduced.</p></fn><fn id="table2fn5"><p><sup>e</sup>IoT: Internet of Things.</p></fn><fn id="table2fn6"><p><sup>f</sup>IoHCS: Internet-of-Healthcare System.</p></fn><fn id="table2fn7"><p><sup>g</sup>BRCA: breast cancer susceptibility gene.</p></fn><fn id="table2fn8"><p><sup>h</sup>VUS: variant of uncertain significance.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-7"><title>EHR Management/Health Information Exchange</title><p>Six higher-maturity studies were categorized as EHR management/health information exchange [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref32">32</xref>]. These studies examined blockchain/DLT systems for personal health records, referral data exchange, identity and document sharing, electronic prescribing, decentralized identifiers, verifiable credentials, and patient-mediated health information exchange. PatientDataChain and iWellChain were evaluated in clinical settings and used off-chain storage with blockchain-based mechanisms to support data integrity, permissions, and patient-authorized access [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>]. Other studies examined identity and document portability for people experiencing homelessness [<xref ref-type="bibr" rid="ref29">29</xref>], blockchain-supported electronic prescribing in family medicine clinics [<xref ref-type="bibr" rid="ref30">30</xref>], decentralized identity and credential sharing through MediLinker, a blockchain-based decentralized health information management platform [<xref ref-type="bibr" rid="ref31">31</xref>], and Fast Healthcare Interoperability Resources (FHIR)&#x2013;based patient-mediated information exchange through HealthPocket, a blockchain-based mobile health information exchange platform [<xref ref-type="bibr" rid="ref32">32</xref>].</p><p>Across these studies, blockchain/DLT systems supported permissioned access, patient authorization, identity management, data integrity, auditability, and interoperability. However, implementation remained limited to pilots, usability studies, or early clinical demonstrations, with short follow-up, restricted settings, partial uptake, and unresolved integration challenges with existing EHR infrastructure (<xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>).</p></sec><sec id="s3-8"><title>Telemedicine/Distributed Care/IoT-Enabled Remote Monitoring</title><p>Two higher-maturity studies were categorized in the telemedicine, distributed care, and IoT-enabled remote monitoring domain [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref34">34</xref>]. Dovetail, a blockchain-based digital consent mobile application for patients with diabetes, was evaluated in a UK general practice, focusing on patient-managed consent for data sharing between the practice and diabetes self-management tools [<xref ref-type="bibr" rid="ref33">33</xref>]. The Internet-of-Healthcare System (IoHCS), a blockchain-supported health information network implemented across more than 350 hospitals, provided secure patient access in Thailand, with staff feedback reporting high satisfaction with usability, installation, maintenance, and security [<xref ref-type="bibr" rid="ref34">34</xref>].</p><p>These studies used blockchain/DLT systems to support consent management, secure remote access, identity and permission control, data integrity, and cross-provider data availability. Evidence remained limited to 1 digital consent pilot and 1 operational health information access network, with uncertainty around scalability, interoperability, technical reliability, and integration into clinical workflows.</p></sec><sec id="s3-9"><title>Clinical Trials/Research Governance</title><p>Nine higher-maturity studies examined applications of blockchain/DLT systems in clinical trials/research governance [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref44">44</xref>]. These studies addressed consent management, participant engagement, data integrity, auditability, data validation, protocol amendments, and research-data sharing. Motohashi et al [<xref ref-type="bibr" rid="ref36">36</xref>] applied cryptographic hash chains in an insomnia clinical trial and demonstrated detection of simulated fraudulent access. Hirano et al [<xref ref-type="bibr" rid="ref37">37</xref>] evaluated blockchain-based data validation in a breast cancer clinical trial conducted within a Japanese regulatory sandbox.</p><p>Other studies focused on participant-facing governance. METORY was developed as a blockchain-based dynamic consent platform [<xref ref-type="bibr" rid="ref38">38</xref>] and subsequently evaluated in a decentralized multicenter trial involving 60 participants [<xref ref-type="bibr" rid="ref39">39</xref>]. Mak et al [<xref ref-type="bibr" rid="ref40">40</xref>] piloted a Hyperledger Fabric system for informed consent and patient engagement among 12 patients with moderate to severe psoriasis. Additional applications included monitoring changes to medical records [<xref ref-type="bibr" rid="ref41">41</xref>], authenticated sharing of deidentified genomic and clinical cancer data [<xref ref-type="bibr" rid="ref42">42</xref>], decentralized biobanking [<xref ref-type="bibr" rid="ref43">43</xref>], and patient-facing access to health records and research eligibility information [<xref ref-type="bibr" rid="ref44">44</xref>].</p><p>Across these studies, blockchain/DLT systems were used less as repositories for research data than as accountability layers for recording consent, preserving data integrity, validating submissions, tracking access or amendments, and supporting transparent participant engagement. Most studies remained small-scale pilots, usability studies, or early demonstrations, with limited evidence of long-term integration into trial-management systems, regulatory workflows, ethics-review processes, or routine research infrastructure.</p></sec><sec id="s3-10"><title>Public Health Surveillance and Certification</title><p>No higher-maturity studies were categorized as public health surveillance or certification. The wider evidence gap map included studies on vaccination and testing certificates, outbreak surveillance, public-health data integrity, cross-border verification, and privacy-preserving credentials. However, these remained at the proof-of-concept/prototype or simulated/benchmarked evaluation stage. Evidence of testing with real users, implementation in public-health workflows, or adoption across health authorities was limited.</p></sec><sec id="s3-11"><title>Clinical Decision Support/Smart Health Care/AI-Enabled Data Governance</title><p>One higher-maturity study was categorized in the clinical decision support, smart health care, and AI-enabled data governance domains [<xref ref-type="bibr" rid="ref35">35</xref>]. The breast cancer susceptibility gene-China (BRCA-CN) study deployed a consortium blockchain framework for cross-institutional breast cancer susceptibility gene variant interpretation in the Chinese population. Six clinical genetics laboratories shared and curated variant evidence through a permissioned blockchain network incorporating smart-contract governance, expert consensus review, audit trails, and AI-supported variant assessment [<xref ref-type="bibr" rid="ref35">35</xref>]. The study positioned blockchain/DLT as governance infrastructure for standardizing data contribution, preserving provenance, coordinating expert review, and supporting cross-institutional accountability. However, evidence in this domain remained limited to a single deployment, and blockchain did not resolve broader challenges involving model validity, bias, data quality, clinical effectiveness, or routine integration.</p></sec><sec id="s3-12"><title>Health Data Marketplace, Monetization, and Incentives</title><p>One higher-maturity study was categorized in the health data marketplace/monetization domain [<xref ref-type="bibr" rid="ref45">45</xref>]. This mixed methods case study evaluated the operational feasibility of a decentralized biobanking application at a US academic medical center. The study recruited 1080 biobank members over 10 weeks; 405 downloaded the application, and 140 tested the blockchain component. Of these, 89.3% (125/140) successfully claimed a nonfungible token representing their connection to donated biospecimens and access to related specimen information [<xref ref-type="bibr" rid="ref45">45</xref>].</p><p>Rather than functioning as a conventional data marketplace, the platform used blockchain to support transparency, donor recognition, participant engagement, and future incentive and governance models. The study suggests that blockchain/DLT systems may support patient-facing transparency and value recognition in biobanking; however, sustainability, workflow integration, communication, scalability, and ethical oversight remain unresolved [<xref ref-type="bibr" rid="ref45">45</xref>].</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings and Contribution</title><p>This study aimed to characterize how blockchain/DLT systems have been applied to health-data governance, identify the application domains and governance functions addressed, and assess the maturity of the supporting evidence. Collectively, the findings reveal 3 key insights. First, the literature is expansive but concentrated at low maturity: only 19 of 892 studies reported a pilot, usability-tested, or operational deployment, and a single study was classified as an operational/real-world deployment. Second, blockchain/DLT systems were rarely positioned as repositories for identifiable clinical data or as direct clinical interventions. Instead, they functioned as governance-layer infrastructure intended to coordinate access, verify transactions, record permissions, preserve audit trails, and support trust across distributed actors. Third, higher-maturity evidence was unevenly distributed across domains. EHR/health information exchange, clinical trials/research governance, and telemedicine/distributed care accounted for most applied studies, whereas public health surveillance/certification, health data marketplace/monetization, and clinical decision support/smart health care were dominated by early-stage technical work.</p><p>Previous reviews have mapped blockchain/DLT applications across health care but have less often examined their governance role or the maturity of the supporting evidence [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. This review maps application domains, governance functions, and evidence maturity together, showing that the scale of the literature risks overstating the field&#x2019;s progress. In other words, many systems have been prototyped, simulated, or benchmarked, but few have been evaluated in routine settings [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. This is consistent with Yeung et al [<xref ref-type="bibr" rid="ref46">46</xref>] findings that health care blockchain applications had shown little real transformative deployment and 5 years on, the gap persists.</p><p>Beyond validating that gap, this review reveals 2 novel contributions. By coding governance function and evidence maturity together, this study shows that some of the field&#x2019;s most frequently reported strengths, privacy/security, interoperability/data sharing, and access control are concentrated where the evidence is least mature: in proof-of-concept and simulated/benchmarked evaluation studies rather than implemented or deployed systems. Additionally, this study demonstrates that the specific contribution of DLT properties to measured outcomes could generally not be isolated from that of interface design, system integration, and conventional infrastructure [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref45">45</xref>]. In line with this, systems in which the ledger was most central did not reach sustained use [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref37">37</xref>-<xref ref-type="bibr" rid="ref45">45</xref>]. We state this as an observed pattern, not a causal relationship as the evidence is based on limited studies, several of which evaluate the same or closely related architecture, and is confined to indexed literature that may underrepresent operational deployments.</p></sec><sec id="s4-2"><title>Blockchain/DLT Systems as Governance-Layer Infrastructure</title><p>The recurring mechanisms were similar across domains: access-control logs, consent and authorization records, identity and authentication credentials, provenance records, integrity checks, audit trails, and transaction histories [<xref ref-type="bibr" rid="ref47">47</xref>-<xref ref-type="bibr" rid="ref51">51</xref>]. In each case, identifiable health data remained off-chain, while the ledger held only hashes, metadata, permissions, or transactions to support verification and accountability [<xref ref-type="bibr" rid="ref48">48</xref>-<xref ref-type="bibr" rid="ref50">50</xref>]. This locates blockchain&#x2019;s contribution not in replacing existing health information systems but in providing a coordination and verification layer across fragmented data environments [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. Blockchain/DLT systems may therefore be most relevant where governance itself is distributed and where multiple organizations, professionals, patients, researchers, regulators, or commercial actors must exchange, authorize, validate, or audit data without relying on a single central authority [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref52">52</xref>]. Such settings include cross-institutional health information exchange [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref51">51</xref>], multicenter clinical trials [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref42">42</xref>], decentralized research platforms [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref52">52</xref>], genomic databases [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref42">42</xref>], biobanks [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref45">45</xref>], and patient-mediated data-sharing systems [<xref ref-type="bibr" rid="ref31">31</xref>,<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref53">53</xref>].</p></sec><sec id="s4-3"><title>From Technical Demonstration to Implementation</title><p>A central finding is the gap between technical possibility and implemented governance. A technically functional system is not necessarily a usable, trusted, sustainable, or governable intervention [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. The higher-maturity studies suggest that blockchain/DLT systems may support consent management, auditability, data validation, patient-facing transparency, and cross-institutional coordination. These functions are particularly relevant to clinical trials and research governance, where transparency, protocol adherence, and accountability remain persistent concerns [<xref ref-type="bibr" rid="ref54">54</xref>,<xref ref-type="bibr" rid="ref55">55</xref>].</p><p>Notably, however, the measured benefits across these studies typically arose from interface design, system integration, remote monitoring, or conventional data infrastructure rather than from distributed-ledger properties themselves [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref45">45</xref>], and none of the included higher-maturity studies reported evidence of sustained routine use beyond the evaluation period [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref45">45</xref>]. Where blockchain/DLT contributed, it did so by producing more traceable records of consent, amendments, access, and trial events when embedded within appropriate regulatory and institutional frameworks, not by independently delivering the measured outcome [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref56">56</xref>]. Implementation is less dependent on the ledger than on institutional participation, EHR integration, governance authority, user trust, workflow fit, legal accountability, cost, and long-term maintenance [<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref58">58</xref>].</p><p>The value of blockchain/DLT systems is therefore highly context-dependent. Their use is most justified where governance involves multiple institutions, low baseline trust, distributed authority, or audit requirements that must be met without a single central actor, and blockchain/DLT systems should not be treated as default solutions [<xref ref-type="bibr" rid="ref46">46</xref>]. In centralized or highly integrated systems, similar objectives are often achievable through conventional databases, federated architectures, access-control systems, secure audit logs, or trusted institutional governance, without the added complexity of DLT infrastructure [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref51">51</xref>]. Reviews and implementation studies consistently identify constraints around scalability, latency, throughput, storage design, interoperability, cost, technical complexity, standardization, and regulatory uncertainty [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref57">57</xref>,<xref ref-type="bibr" rid="ref58">58</xref>]. Recent systematic reviews continue to identify the same implementation barriers despite the growing literature, suggesting that many of the obstacles reported several years ago remain unresolved [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]. These constraints are especially consequential in clinical environments, where added workflow burden, delay, or fragmentation can undermine adoption.</p><p>Even where they support verification and traceability, blockchain/DLT systems do not resolve the broader governance challenges of digital health. Legal accountability, regulatory compliance, data stewardship, and ethical oversight remain external to the technology: a ledger can record that consent was given, amended, or withdrawn, but cannot ensure that consent was informed or that power imbalances between patients, institutions, and commercial actors have been addressed [<xref ref-type="bibr" rid="ref53">53</xref>]. This is particularly important in health data marketplaces, incentive models, and AI-enabled health care. Incentives alone may be insufficient to promote sensitive data sharing while privacy, security, trust, and regulatory concerns remain unresolved [<xref ref-type="bibr" rid="ref61">61</xref>]. Marketplace prototypes remain constrained by unresolved questions of governance, regulation, interoperability, data quality, ownership, and compensation standards [<xref ref-type="bibr" rid="ref62">62</xref>,<xref ref-type="bibr" rid="ref63">63</xref>]. Governance frameworks must therefore be designed around the full sociotechnical system, not the ledger alone.</p></sec><sec id="s4-4"><title>Implications for Policy, Implementation, and Future Research</title><p>These findings suggest blockchain/DLT systems should be evaluated as components of broader governance frameworks rather than stand-alone innovations. For policymakers and health-system leaders, the relevant question is not whether blockchain is technically novel but whether it improves governance performance in measurable ways, consent traceability, transparency, accountability, access-control reliability, interoperability, administrative efficiency, user trust, cost-effectiveness, and sustainability [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Future research should move beyond proof-of-concept and simulated/benchmarked evaluation studies toward implementation-focused evaluation, reporting adoption, usability, integration with existing systems, governance roles, data-protection compliance, costs, unintended consequences, and long-term maintenance. Recent reviews likewise emphasize the need for more empirical evaluations, real-world deployments, and human-centered implementation studies rather than additional conceptual architectures [<xref ref-type="bibr" rid="ref59">59</xref>,<xref ref-type="bibr" rid="ref60">60</xref>]. Comparative studies are needed to establish when blockchain/DLT systems offer genuine advantages over conventional alternatives. For emerging areas such as data marketplaces, incentive models, and AI-enabled governance, future work should address ethical and regulatory questions directly, including data commodification, equity, consent withdrawal, and accountability for secondary use [<xref ref-type="bibr" rid="ref52">52</xref>,<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref61">61</xref>].</p></sec><sec id="s4-5"><title>Limitations</title><p>Several limitations should be acknowledged. First, evidence was restricted to peer-reviewed English-language publications. Relevant implementation activity may appear in gray literature, policy documents, industry reports, white papers, or regulatory submissions, particularly in fast-moving areas such as data marketplaces and public health certification. Second, the evidence base was heterogeneous across domains, technologies, governance functions, and evaluation methods, limiting comparability. Third, no formal risk-of-bias or quality appraisal was conducted, consistent with scoping review methodology [<xref ref-type="bibr" rid="ref25">25</xref>]; evidence maturity should not be interpreted as equivalent to methodological quality or effectiveness. Fourth, classifying domains, governance functions, and maturity required interpretive judgment. Although coding categories were defined and applied consistently, some studies spanned multiple domains, and the primary-domain classification may have simplified cross-domain studies.</p><p>In conclusion, this study identified that blockchain/DLT systems are most consistently positioned as governance-layer infrastructure for recording, verifying, and coordinating data-related actions across distributed actors. Their most active role is currently to support coordination, verification, consent traceability, auditability, and accountable data exchange within complex digital health ecosystems, rather than replacing clinical systems or storing identifiable health data on-chain. The broader implication is that blockchain/DLT systems should be judged by their contribution to governance performance rather than by technological novelty.</p><p>For health care systems, regulators, researchers, and patients, the relevant question is whether blockchain-enabled systems can make data access more accountable, consent more transparent, data exchange more trustworthy, and distributed collaboration more reliable. To our knowledge, peer-reviewed evidence supporting these outcomes remains limited, and where higher-maturity systems reported benefits, the specific contribution of the distributed ledger was often difficult to isolate. Future work should move beyond technical demonstration and test whether blockchain/DLT systems can be integrated, sustained, and shown to improve accountability, consent traceability, and trusted data exchange in mature, deployed systems.</p></sec></sec></body><back><ack><p>The authors thank Meher Kafalian (AcaciaTools) for his graphic design. The authors declare the use of generative AI (GenAI) in the research and writing process. According to the Generative AI Delegation Taxonomy (GAIDeT; 2025), the following tasks were delegated to GenAI tools under full human supervision for proofreading and editing and for publication support. The GenAI tool used was ChatGPT (GPT-5.5, OpenAI). Responsibility for the final manuscript lies entirely with the authors. GenAI tools are not listed as authors and do not bear responsibility for the final outcomes. The declaration was submitted by all authors.</p></ack><notes><sec><title>Funding</title><p>The authors declared no financial support was received for this work.</p></sec><sec><title>Data Availability</title><p>The data underlying the evidence gap map, including the classifications of included studies by domain, governance function, and evidence maturity, are provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: SY</p><p>Data curation: SY, NM, SV</p><p>Investigation: SY, NM</p><p>Methodology: SY</p><p>Supervision: SV</p><p>Validation: SY, NS, LS, GG, NM, SV</p><p>Writing &#x2013; original draft: SY</p><p>Writing &#x2013; review &#x0026; editing: SY, NS, LS, GG, NM, SV</p><p>All authors have read and approved the final version of the manuscript and agree to be accountable for all aspects of the work.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">DLT</term><def><p>distributed ledger technology</p></def></def-item><def-item><term id="abb2">EHDS</term><def><p>European Health Data Space</p></def></def-item><def-item><term id="abb3">EHR</term><def><p>electronic health record</p></def></def-item><def-item><term id="abb4">FHIR</term><def><p>Fast Healthcare Interoperability Resources</p></def></def-item><def-item><term id="abb5">IoHCS</term><def><p>Internet-of-Healthcare System</p></def></def-item><def-item><term id="abb6">IoT</term><def><p>Internet of Things</p></def></def-item><def-item><term id="abb7">OECD</term><def><p>Organisation for Economic Co-operation and Development</p></def></def-item><def-item><term id="abb8">PRISMA</term><def><p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p></def></def-item><def-item><term id="abb9">PRISMA-S</term><def><p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses literature search extension</p></def></def-item><def-item><term id="abb10">PRISMA-ScR</term><def><p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses extension for Scoping Reviews</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>Fr&#x00F6;hlich</surname><given-names>H</given-names> </name><name name-style="western"><surname>Funck Hansen</surname><given-names>A</given-names> </name><name name-style="western"><surname>Hilvo</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Reality check: the aspirations of the European Health Data Space amidst challenges in decentralized data analysis</article-title><source>J Med Internet Res</source><year>2025</year><month>09</month><day>19</day><volume>27</volume><fpage>e76491</fpage><pub-id pub-id-type="doi">10.2196/76491</pub-id><pub-id pub-id-type="medline">40971544</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>Cervera de la Cruz</surname><given-names>P</given-names> </name><name name-style="western"><surname>Lalova-Spinks</surname><given-names>T</given-names> </name><name name-style="western"><surname>Shabani</surname><given-names>M</given-names> </name></person-group><article-title>The European Health Data Space: an opportunity to strengthen citizen rights and engage citizens in health data governance</article-title><source>Front Med</source><year>2026</year><volume>12</volume><fpage>1699941</fpage><pub-id pub-id-type="doi">10.3389/fmed.2025.1699941</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>Raab</surname><given-names>R</given-names> </name><name name-style="western"><surname>K&#x00FC;derle</surname><given-names>A</given-names> </name><name name-style="western"><surname>Zakreuskaya</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Federated electronic health records for the European Health Data Space</article-title><source>Lancet Digit Health</source><year>2023</year><month>11</month><volume>5</volume><issue>11</issue><fpage>e840</fpage><lpage>e847</lpage><pub-id pub-id-type="doi">10.1016/S2589-7500(23)00156-5</pub-id><pub-id pub-id-type="medline">37741765</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>Leo</surname><given-names>DG</given-names> </name><name name-style="western"><surname>Buckley</surname><given-names>BJR</given-names> </name><name name-style="western"><surname>Chowdhury</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Interactive remote patient monitoring devices for managing chronic health conditions: systematic review and meta-analysis</article-title><source>J Med Internet Res</source><year>2022</year><month>11</month><day>3</day><volume>24</volume><issue>11</issue><fpage>e35508</fpage><pub-id pub-id-type="doi">10.2196/35508</pub-id><pub-id pub-id-type="medline">36326818</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="report"><article-title>Does healthcare deliver?: results from the patient-reported indicator surveys (PaRIS)</article-title><year>2025</year><access-date>2026-09-17</access-date><publisher-name>OECD Publishing</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2025/02/does-healthcare-deliver_978507f1/c8af05a5-en.pdf?">https://www.oecd.org/content/dam/oecd/en/publications/reports/2025/02/does-healthcare-deliver_978507f1/c8af05a5-en.pdf?</ext-link></comment></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>Catapan</surname><given-names>S de C</given-names> </name><name name-style="western"><surname>Sazon</surname><given-names>H</given-names> </name><name name-style="western"><surname>Zheng</surname><given-names>S</given-names> </name><etal/></person-group><article-title>A systematic review of consumers&#x2019; and healthcare professionals&#x2019; trust in digital healthcare</article-title><source>NPJ Digit Med</source><year>2025</year><month>02</month><day>21</day><volume>8</volume><issue>1</issue><fpage>115</fpage><pub-id pub-id-type="doi">10.1038/s41746-025-01510-8</pub-id><pub-id pub-id-type="medline">39984678</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>Kerasidou</surname><given-names>A</given-names> </name><name name-style="western"><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>2023</year><month>07</month><day>14</day><volume>24</volume><issue>1</issue><fpage>51</fpage><pub-id pub-id-type="doi">10.1186/s12910-023-00922-z</pub-id><pub-id pub-id-type="medline">37452393</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>Saberi</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Mcheick</surname><given-names>H</given-names> </name><name name-style="western"><surname>Adda</surname><given-names>M</given-names> </name></person-group><article-title>From data silos to health records without borders: a systematic survey on patient-centered data interoperability</article-title><source>Information</source><year>2025</year><volume>16</volume><issue>2</issue><fpage>106</fpage><pub-id pub-id-type="doi">10.3390/info16020106</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>Ambalavanan</surname><given-names>R</given-names> </name><name name-style="western"><surname>Snead</surname><given-names>RS</given-names> </name><name name-style="western"><surname>Marczika</surname><given-names>J</given-names> </name><name name-style="western"><surname>Towett</surname><given-names>G</given-names> </name><name name-style="western"><surname>Malioukis</surname><given-names>A</given-names> </name><name name-style="western"><surname>Mbogori-Kairichi</surname><given-names>M</given-names> </name></person-group><article-title>Challenges and strategies in building a foundational digital health data integration ecosystem: a systematic review and thematic synthesis</article-title><source>Front Health Serv</source><year>2025</year><volume>5</volume><fpage>1600689</fpage><pub-id pub-id-type="doi">10.3389/frhs.2025.1600689</pub-id><pub-id pub-id-type="medline">40621432</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Saeed</surname><given-names>H</given-names> </name><name name-style="western"><surname>Malik</surname><given-names>H</given-names> </name><name name-style="western"><surname>Bashir</surname><given-names>U</given-names> </name><etal/></person-group><article-title>Blockchain technology in healthcare: a systematic review</article-title><source>PLoS ONE</source><year>2022</year><volume>17</volume><issue>4</issue><fpage>e0266462</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0266462</pub-id><pub-id pub-id-type="medline">35404955</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Nakamoto</surname><given-names>S</given-names> </name></person-group><article-title>Bitcoin: a peer-to-peer electronic cash system</article-title><year>2008</year><access-date>2026-09-17</access-date><publisher-name>Bitcoin.org</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://bitcoin.org/bitcoin.pdf">https://bitcoin.org/bitcoin.pdf</ext-link></comment></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Marino</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Diaz Paz</surname><given-names>C</given-names> </name></person-group><article-title>Smart contracts and shared platforms in sustainable health care: systematic review</article-title><source>JMIR Med Inform</source><year>2025</year><month>01</month><day>31</day><volume>13</volume><fpage>e58575</fpage><pub-id pub-id-type="doi">10.2196/58575</pub-id><pub-id pub-id-type="medline">39889283</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>H&#x00F6;lbl</surname><given-names>M</given-names> </name><name name-style="western"><surname>Kompara</surname><given-names>M</given-names> </name><name name-style="western"><surname>Kami&#x0161;ali&#x0107;</surname><given-names>A</given-names> </name><name name-style="western"><surname>Nemec Zlatolas</surname><given-names>L</given-names> </name></person-group><article-title>A systematic review of the use of blockchain in healthcare</article-title><source>Symmetry (Basel)</source><year>2018</year><volume>10</volume><issue>10</issue><fpage>470</fpage><pub-id pub-id-type="doi">10.3390/sym10100470</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kuo</surname><given-names>TT</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>HE</given-names> </name><name name-style="western"><surname>Ohno-Machado</surname><given-names>L</given-names> </name></person-group><article-title>Blockchain distributed ledger technologies for biomedical and health care applications</article-title><source>J Am Med Inform Assoc</source><year>2017</year><month>11</month><day>1</day><volume>24</volume><issue>6</issue><fpage>1211</fpage><lpage>1220</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocx068</pub-id><pub-id pub-id-type="medline">29016974</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>Shaikh</surname><given-names>M</given-names> </name><name name-style="western"><surname>Memon</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Ebrahimi</surname><given-names>A</given-names> </name><name name-style="western"><surname>Wiil</surname><given-names>UK</given-names> </name></person-group><article-title>A systematic literature review for blockchain-based healthcare implementations</article-title><source>Health Care (Don Mills)</source><year>2025</year><volume>13</volume><issue>9</issue><fpage>1087</fpage><pub-id pub-id-type="doi">10.3390/healthcare13091087</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Abu-Elezz</surname><given-names>I</given-names> </name><name name-style="western"><surname>Hassan</surname><given-names>A</given-names> </name><name name-style="western"><surname>Nazeemudeen</surname><given-names>A</given-names> </name><name name-style="western"><surname>Househ</surname><given-names>M</given-names> </name><name name-style="western"><surname>Abd-Alrazaq</surname><given-names>A</given-names> </name></person-group><article-title>The benefits and threats of blockchain technology in healthcare: a scoping review</article-title><source>Int J Med Inform</source><year>2020</year><month>10</month><volume>142</volume><fpage>104246</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2020.104246</pub-id><pub-id pub-id-type="medline">32828033</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tandon</surname><given-names>A</given-names> </name><name name-style="western"><surname>Dhir</surname><given-names>A</given-names> </name><name name-style="western"><surname>Islam</surname><given-names>AKMN</given-names> </name><name name-style="western"><surname>M&#x00E4;ntym&#x00E4;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>2020</year><month>11</month><volume>122</volume><fpage>103290</fpage><pub-id pub-id-type="doi">10.1016/j.compind.2020.103290</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Schmeelk</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kanabar</surname><given-names>M</given-names> </name><name name-style="western"><surname>Peterson</surname><given-names>K</given-names> </name><name name-style="western"><surname>Pathak</surname><given-names>J</given-names> </name></person-group><article-title>Electronic health records and blockchain interoperability requirements: a scoping review</article-title><source>JAMIA Open</source><year>2022</year><month>10</month><volume>5</volume><issue>3</issue><fpage>ooac068</fpage><pub-id pub-id-type="doi">10.1093/jamiaopen/ooac068</pub-id><pub-id pub-id-type="medline">35911668</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Durneva</surname><given-names>P</given-names> </name><name name-style="western"><surname>Cousins</surname><given-names>K</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>M</given-names> </name></person-group><article-title>The current state of research, challenges, and future research directions of blockchain technology in patient care: systematic review</article-title><source>J Med Internet Res</source><year>2020</year><month>07</month><day>20</day><volume>22</volume><issue>7</issue><fpage>e18619</fpage><pub-id pub-id-type="doi">10.2196/18619</pub-id><pub-id pub-id-type="medline">32706668</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Donoghue</surname><given-names>O</given-names> </name><name name-style="western"><surname>Vazirani</surname><given-names>AA</given-names> </name><name name-style="western"><surname>Brindley</surname><given-names>D</given-names> </name><name name-style="western"><surname>Meinert</surname><given-names>E</given-names> </name></person-group><article-title>Design choices and trade-offs in health care blockchain implementations: systematic review</article-title><source>J Med Internet Res</source><year>2019</year><month>05</month><day>10</day><volume>21</volume><issue>5</issue><fpage>e12426</fpage><pub-id pub-id-type="doi">10.2196/12426</pub-id><pub-id pub-id-type="medline">31094344</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Beyene</surname><given-names>M</given-names> </name><name name-style="western"><surname>Toussaint</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Thiebes</surname><given-names>S</given-names> </name><name name-style="western"><surname>Schlesner</surname><given-names>M</given-names> </name><name name-style="western"><surname>Brors</surname><given-names>B</given-names> </name><name name-style="western"><surname>Sunyaev</surname><given-names>A</given-names> </name></person-group><article-title>A scoping review of distributed ledger technology in genomics: thematic analysis and directions for future research</article-title><source>J Am Med Inform Assoc</source><year>2022</year><month>07</month><day>12</day><volume>29</volume><issue>8</issue><fpage>1433</fpage><lpage>1444</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocac077</pub-id><pub-id pub-id-type="medline">35595301</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kakarlapudi</surname><given-names>PV</given-names> </name><name name-style="western"><surname>Mahmoud</surname><given-names>QH</given-names> </name></person-group><article-title>A systematic review of blockchain for consent management</article-title><source>Health Care</source><year>2021</year><volume>9</volume><issue>2</issue><fpage>137</fpage><pub-id pub-id-type="doi">10.3390/healthcare9020137</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ng</surname><given-names>WY</given-names> </name><name name-style="western"><surname>Tan</surname><given-names>TE</given-names> </name><name name-style="western"><surname>Movva</surname><given-names>PVH</given-names> </name><etal/></person-group><article-title>Blockchain applications in health care for COVID-19 and beyond: a systematic review</article-title><source>Lancet Digit Health</source><year>2021</year><month>12</month><volume>3</volume><issue>12</issue><fpage>e819</fpage><lpage>e829</lpage><pub-id pub-id-type="doi">10.1016/S2589-7500(21)00210-7</pub-id><pub-id pub-id-type="medline">34654686</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ungson</surname><given-names>GR</given-names> </name><name name-style="western"><surname>Soorapanth</surname><given-names>S</given-names> </name><name name-style="western"><surname>Wong</surname><given-names>YY</given-names> </name></person-group><article-title>An assessment of blockchain performance in healthcare: an extensive literature review</article-title><source>J Health Organ Manag</source><year>2025</year><month>01</month><day>14</day><fpage>1</fpage><lpage>29</lpage><pub-id pub-id-type="doi">10.1108/JHOM-08-2024-0328</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tricco</surname><given-names>AC</given-names> </name><name name-style="western"><surname>Lillie</surname><given-names>E</given-names> </name><name name-style="western"><surname>Zarin</surname><given-names>W</given-names> </name><etal/></person-group><article-title>PRISMA extension for scoping reviews (PRISMA-ScR): checklist and explanation</article-title><source>Ann Intern Med</source><year>2018</year><month>10</month><day>2</day><volume>169</volume><issue>7</issue><fpage>467</fpage><lpage>473</lpage><pub-id pub-id-type="doi">10.7326/M18-0850</pub-id><pub-id pub-id-type="medline">30178033</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rethlefsen</surname><given-names>ML</given-names> </name><name name-style="western"><surname>Kirtley</surname><given-names>S</given-names> </name><name name-style="western"><surname>Waffenschmidt</surname><given-names>S</given-names> </name><etal/></person-group><article-title>PRISMA-S: an extension to the PRISMA statement for reporting literature searches in systematic reviews</article-title><source>Syst Rev</source><year>2021</year><month>01</month><day>26</day><volume>10</volume><issue>1</issue><fpage>39</fpage><pub-id pub-id-type="doi">10.1186/s13643-020-01542-z</pub-id><pub-id pub-id-type="medline">33499930</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cernian</surname><given-names>A</given-names> </name><name name-style="western"><surname>Tiganoaia</surname><given-names>B</given-names> </name><name name-style="western"><surname>Sacala</surname><given-names>I</given-names> </name><name name-style="western"><surname>Pavel</surname><given-names>A</given-names> </name><name name-style="western"><surname>Iftemi</surname><given-names>A</given-names> </name></person-group><article-title>Patientdatachain: a blockchain-based approach to integrate personal health records</article-title><source>Sensors (Basel)</source><year>2020</year><month>11</month><day>16</day><volume>20</volume><issue>22</issue><fpage>6538</fpage><pub-id pub-id-type="doi">10.3390/s20226538</pub-id><pub-id pub-id-type="medline">33207620</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lo</surname><given-names>YS</given-names> </name><name name-style="western"><surname>Yang</surname><given-names>CY</given-names> </name><name name-style="western"><surname>Chien</surname><given-names>HF</given-names> </name><name name-style="western"><surname>Chang</surname><given-names>SS</given-names> </name><name name-style="western"><surname>Lu</surname><given-names>CY</given-names> </name><name name-style="western"><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>2019</year><month>12</month><day>4</day><volume>21</volume><issue>12</issue><fpage>e13563</fpage><pub-id pub-id-type="doi">10.2196/13563</pub-id><pub-id pub-id-type="medline">31799935</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khurshid</surname><given-names>A</given-names> </name><name name-style="western"><surname>Rajeswaren</surname><given-names>V</given-names> </name><name name-style="western"><surname>Andrews</surname><given-names>S</given-names> </name></person-group><article-title>Using blockchain technology to mitigate challenges in service access for the homeless and data exchange between providers: qualitative study</article-title><source>J Med Internet Res</source><year>2020</year><month>06</month><day>4</day><volume>22</volume><issue>6</issue><fpage>e16887</fpage><pub-id pub-id-type="doi">10.2196/16887</pub-id><pub-id pub-id-type="medline">32348278</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Seaberg</surname><given-names>RW</given-names> </name><name name-style="western"><surname>Seaberg</surname><given-names>TR</given-names> </name><name name-style="western"><surname>Seaberg</surname><given-names>DC</given-names> </name></person-group><article-title>Use of blockchain technology for electronic prescriptions</article-title><source>Blockchain Healthc Today</source><year>2021</year><volume>4</volume><pub-id pub-id-type="doi">10.30953/bhty.v4.183</pub-id><pub-id pub-id-type="medline">36777487</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bautista</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Harrell</surname><given-names>DT</given-names> </name><name name-style="western"><surname>Hanson</surname><given-names>L</given-names> </name><etal/></person-group><article-title>MediLinker: a blockchain-based decentralized health information management platform for patient-centric healthcare</article-title><source>Front Big Data</source><year>2023</year><volume>6</volume><fpage>1146023</fpage><pub-id pub-id-type="doi">10.3389/fdata.2023.1146023</pub-id><pub-id pub-id-type="medline">37426689</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bae</surname><given-names>YS</given-names> </name><name name-style="western"><surname>Park</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>SM</given-names> </name><etal/></person-group><article-title>Development of blockchain-based health information exchange platform using HL7 FHIR standards: usability test</article-title><source>IEEE Access</source><year>2022</year><volume>10</volume><fpage>79264</fpage><lpage>79271</lpage><pub-id pub-id-type="doi">10.1109/ACCESS.2022.3194159</pub-id></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Despotou</surname><given-names>G</given-names> </name><name name-style="western"><surname>Evans</surname><given-names>J</given-names> </name><name name-style="western"><surname>Nash</surname><given-names>W</given-names> </name><name name-style="western"><surname>Eavis</surname><given-names>A</given-names> </name><name name-style="western"><surname>Robbins</surname><given-names>T</given-names> </name><name name-style="western"><surname>Arvanitis</surname><given-names>TN</given-names> </name></person-group><article-title>Evaluation of patient perception towards dynamic health data sharing using blockchain based digital consent with the Dovetail digital consent application: a cross sectional exploratory study</article-title><source>Digit Health</source><year>2020</year><volume>6</volume><fpage>2055207620924949</fpage><pub-id pub-id-type="doi">10.1177/2055207620924949</pub-id><pub-id pub-id-type="medline">32435503</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yongjoh</surname><given-names>S</given-names> </name><name name-style="western"><surname>So-In</surname><given-names>C</given-names> </name><name name-style="western"><surname>Kompunt</surname><given-names>P</given-names> </name><name name-style="western"><surname>Muneesawang</surname><given-names>P</given-names> </name><name name-style="western"><surname>Morien</surname><given-names>RI</given-names> </name></person-group><article-title>Development of an internet-of-healthcare system using blockchain</article-title><source>IEEE Access</source><year>2021</year><volume>9</volume><fpage>113017</fpage><lpage>113031</lpage><pub-id pub-id-type="doi">10.1109/ACCESS.2021.3103443</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Qu</surname><given-names>S</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>R</given-names> </name><name name-style="western"><surname>Li</surname><given-names>S</given-names> </name><etal/></person-group><article-title>BRCA-CN: a blockchain-based framework to support public variant databases sharing in multi-center community for diagnostic reference and China regulatory science</article-title><source>Hum Genet</source><year>2025</year><month>08</month><volume>144</volume><issue>8</issue><fpage>877</fpage><lpage>898</lpage><pub-id pub-id-type="doi">10.1007/s00439-025-02764-8</pub-id><pub-id pub-id-type="medline">40886259</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Motohashi</surname><given-names>T</given-names> </name><name name-style="western"><surname>Hirano</surname><given-names>T</given-names> </name><name name-style="western"><surname>Okumura</surname><given-names>K</given-names> </name><name name-style="western"><surname>Kashiyama</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ichikawa</surname><given-names>D</given-names> </name><name name-style="western"><surname>Ueno</surname><given-names>T</given-names> </name></person-group><article-title>Secure and scalable mHealth data management using blockchain combined with client hashchain: system design and validation</article-title><source>J Med Internet Res</source><year>2019</year><month>05</month><day>16</day><volume>21</volume><issue>5</issue><fpage>e13385</fpage><pub-id pub-id-type="doi">10.2196/13385</pub-id><pub-id pub-id-type="medline">31099337</pub-id></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hirano</surname><given-names>T</given-names> </name><name name-style="western"><surname>Motohashi</surname><given-names>T</given-names> </name><name name-style="western"><surname>Okumura</surname><given-names>K</given-names> </name><etal/></person-group><article-title>Data validation and verification using blockchain in a clinical trial for breast cancer: regulatory sandbox</article-title><source>J Med Internet Res</source><year>2020</year><month>06</month><day>2</day><volume>22</volume><issue>6</issue><fpage>e18938</fpage><pub-id pub-id-type="doi">10.2196/18938</pub-id><pub-id pub-id-type="medline">32340974</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Huh</surname><given-names>KY</given-names> </name><name name-style="western"><surname>Jeong</surname><given-names>SU</given-names> </name><name name-style="western"><surname>Moon</surname><given-names>SJ</given-names> </name><etal/></person-group><article-title>METORY: development of a demand-driven blockchain-based dynamic consent platform tailored for clinical trials</article-title><source>Front Med</source><year>2022</year><volume>9</volume><fpage>837197</fpage><pub-id pub-id-type="doi">10.3389/fmed.2022.837197</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Huh</surname><given-names>KY</given-names> </name><name name-style="western"><surname>Moon</surname><given-names>SJ</given-names> </name><name name-style="western"><surname>Jeong</surname><given-names>SU</given-names> </name><etal/></person-group><article-title>Evaluation of a blockchain&#x2010;based dynamic consent platform (METORY) in a decentralized and multicenter clinical trial using virtual drugs</article-title><source>Clin Transl Sci</source><year>2022</year><month>05</month><volume>15</volume><issue>5</issue><fpage>1257</fpage><lpage>1268</lpage><pub-id pub-id-type="doi">10.1111/cts.13246</pub-id><pub-id pub-id-type="medline">35157788</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mak</surname><given-names>BC</given-names> </name><name name-style="western"><surname>Addeman</surname><given-names>BT</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Leveraging blockchain technology for informed consent process and patient engagement in a clinical trial pilot</article-title><source>Blockchain Healthc Today</source><year>2021</year><volume>4</volume><pub-id pub-id-type="doi">10.30953/bhty.v4.182</pub-id><pub-id pub-id-type="medline">36777482</pub-id></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sung</surname><given-names>M</given-names> </name><name name-style="western"><surname>Park</surname><given-names>S</given-names> </name><name name-style="western"><surname>Jung</surname><given-names>S</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>E</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>J</given-names> </name><name name-style="western"><surname>Park</surname><given-names>YR</given-names> </name></person-group><article-title>Developing a mobile app for monitoring medical record changes using blockchain: development and usability study</article-title><source>J Med Internet Res</source><year>2020</year><month>08</month><day>14</day><volume>22</volume><issue>8</issue><fpage>e19657</fpage><pub-id pub-id-type="doi">10.2196/19657</pub-id><pub-id pub-id-type="medline">32795988</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Glicksberg</surname><given-names>BS</given-names> </name><name name-style="western"><surname>Burns</surname><given-names>S</given-names> </name><name name-style="western"><surname>Currie</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Blockchain-authenticated sharing of genomic and clinical outcomes data of patients with cancer: a prospective cohort study</article-title><source>J Med Internet Res</source><year>2020</year><month>03</month><day>20</day><volume>22</volume><issue>3</issue><fpage>e16810</fpage><pub-id pub-id-type="doi">10.2196/16810</pub-id><pub-id pub-id-type="medline">32196460</pub-id></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sanchez</surname><given-names>W</given-names> </name><name name-style="western"><surname>Dewan</surname><given-names>A</given-names> </name><name name-style="western"><surname>Budd</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Decentralized biobanking apps for patient tracking of biospecimen research: real-world usability and feasibility study</article-title><source>JMIR Bioinform Biotech</source><year>2025</year><volume>6</volume><fpage>e70463</fpage><pub-id pub-id-type="doi">10.2196/70463</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bae</surname><given-names>YS</given-names> </name><name name-style="western"><surname>Park</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Development and pilot-test of blockchain-based MyHealthData platform</article-title><source>Appl Sci</source><year>2021</year><volume>11</volume><issue>17</issue><fpage>8209</fpage><pub-id pub-id-type="doi">10.3390/app11178209</pub-id></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dewan</surname><given-names>A</given-names> </name><name name-style="western"><surname>Altiery De Jesus</surname><given-names>V</given-names> </name><name name-style="western"><surname>Budd</surname><given-names>E</given-names> </name><etal/></person-group><article-title>Decentralized biobanking to empower patient engagement in biospecimen research: operational feasibility case study</article-title><source>Biopreserv Biobank</source><year>2026</year><month>06</month><volume>24</volume><issue>3</issue><fpage>257</fpage><lpage>271</lpage><pub-id pub-id-type="doi">10.1177/19475535251384429</pub-id><pub-id pub-id-type="medline">41161689</pub-id></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yeung</surname><given-names>K</given-names> </name></person-group><article-title>The health care sector&#x2019;s experience of blockchain: a cross-disciplinary investigation of its real transformative potential</article-title><source>J Med Internet Res</source><year>2021</year><month>12</month><day>20</day><volume>23</volume><issue>12</issue><fpage>e24109</fpage><pub-id pub-id-type="doi">10.2196/24109</pub-id><pub-id pub-id-type="medline">34932009</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ullah</surname><given-names>F</given-names> </name><name name-style="western"><surname>He</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhu</surname><given-names>N</given-names> </name><etal/></person-group><article-title>Blockchain-enabled EHR access auditing: enhancing healthcare data security</article-title><source>Heliyon</source><year>2024</year><month>08</month><day>30</day><volume>10</volume><issue>16</issue><fpage>e34407</fpage><pub-id pub-id-type="doi">10.1016/j.heliyon.2024.e34407</pub-id><pub-id pub-id-type="medline">39253236</pub-id></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Margheri</surname><given-names>A</given-names> </name><name name-style="western"><surname>Masi</surname><given-names>M</given-names> </name><name name-style="western"><surname>Miladi</surname><given-names>A</given-names> </name><name name-style="western"><surname>Sassone</surname><given-names>V</given-names> </name><name name-style="western"><surname>Rosenzweig</surname><given-names>J</given-names> </name></person-group><article-title>Decentralised provenance for healthcare data</article-title><source>Int J Med Inform</source><year>2020</year><month>09</month><volume>141</volume><fpage>104197</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2020.104197</pub-id><pub-id pub-id-type="medline">32540775</pub-id></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Elvas</surname><given-names>LB</given-names> </name><name name-style="western"><surname>Serr&#x00E3;o</surname><given-names>C</given-names> </name><name name-style="western"><surname>Ferreira</surname><given-names>JC</given-names> </name></person-group><article-title>Sharing health information using a blockchain</article-title><source>Health Care (Don Mills)</source><year>2023</year><volume>11</volume><issue>2</issue><fpage>170</fpage><pub-id pub-id-type="doi">10.3390/healthcare11020170</pub-id></nlm-citation></ref><ref id="ref50"><label>50</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kwon</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>T</given-names> </name><name name-style="western"><surname>Cho</surname><given-names>S</given-names> </name></person-group><article-title>Privacy preservation in patient information exchange systems based on blockchain: system design study</article-title><source>J Med Internet Res</source><year>2022</year><month>03</month><day>22</day><volume>24</volume><issue>3</issue><fpage>e29108</fpage><pub-id pub-id-type="doi">10.2196/29108</pub-id><pub-id pub-id-type="medline">35315778</pub-id></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Spanakis</surname><given-names>EG</given-names> </name><name name-style="western"><surname>Sfakianakis</surname><given-names>S</given-names> </name><name name-style="western"><surname>Bonomi</surname><given-names>S</given-names> </name><name name-style="western"><surname>Ciccotelli</surname><given-names>C</given-names> </name><name name-style="western"><surname>Magalini</surname><given-names>S</given-names> </name><name name-style="western"><surname>Sakkalis</surname><given-names>V</given-names> </name></person-group><article-title>Emerging and established trends to support secure health information exchange</article-title><source>Front Digit Health</source><year>2021</year><volume>3</volume><fpage>636082</fpage><pub-id pub-id-type="doi">10.3389/fdgth.2021.636082</pub-id><pub-id pub-id-type="medline">34713107</pub-id></nlm-citation></ref><ref id="ref52"><label>52</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Porsdam Mann</surname><given-names>S</given-names> </name><name name-style="western"><surname>Savulescu</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ravaud</surname><given-names>P</given-names> </name><name name-style="western"><surname>Benchoufi</surname><given-names>M</given-names> </name></person-group><article-title>Blockchain, consent and prosent for medical research</article-title><source>J Med Ethics</source><year>2021</year><month>04</month><day>13</day><volume>47</volume><issue>4</issue><fpage>244</fpage><lpage>250</lpage><pub-id pub-id-type="doi">10.1136/medethics-2019-105963</pub-id><pub-id pub-id-type="medline">32366703</pub-id></nlm-citation></ref><ref id="ref53"><label>53</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Welzel</surname><given-names>C</given-names> </name><name name-style="western"><surname>Ostermann</surname><given-names>M</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>HL</given-names> </name><name name-style="western"><surname>Minssen</surname><given-names>T</given-names> </name><name name-style="western"><surname>Kirsten</surname><given-names>T</given-names> </name><name name-style="western"><surname>Gilbert</surname><given-names>S</given-names> </name></person-group><article-title>Enabling secure and self determined health data sharing and consent management</article-title><source>NPJ Digit Med</source><year>2025</year><month>08</month><day>30</day><volume>8</volume><issue>1</issue><fpage>560</fpage><pub-id pub-id-type="doi">10.1038/s41746-025-01945-z</pub-id><pub-id pub-id-type="medline">40885802</pub-id></nlm-citation></ref><ref id="ref54"><label>54</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhang</surname><given-names>F</given-names> </name><name name-style="western"><surname>Zhu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Zhao</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Discordant information on blinding in trial registries and published research: a systematic review</article-title><source>JAMA Netw Open</source><year>2024</year><month>12</month><day>2</day><volume>7</volume><issue>12</issue><fpage>e2452274</fpage><pub-id pub-id-type="doi">10.1001/jamanetworkopen.2024.52274</pub-id><pub-id pub-id-type="medline">39724369</pub-id></nlm-citation></ref><ref id="ref55"><label>55</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Huang</surname><given-names>RQ</given-names> </name><name name-style="western"><surname>Zhou</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Zheng</surname><given-names>HX</given-names> </name><etal/></person-group><article-title>Transparency of clinical trials in pancreatic cancer: an analysis of availability of trial results from the ClinicalTrials.gov database</article-title><source>Front Oncol</source><year>2022</year><volume>12</volume><fpage>1026268</fpage><pub-id pub-id-type="doi">10.3389/fonc.2022.1026268</pub-id><pub-id pub-id-type="medline">36686766</pub-id></nlm-citation></ref><ref id="ref56"><label>56</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nucciarelli</surname><given-names>L</given-names> </name><name name-style="western"><surname>Gottardelli</surname><given-names>B</given-names> </name><name name-style="western"><surname>Gatta</surname><given-names>R</given-names> </name><name name-style="western"><surname>Damiani</surname><given-names>A</given-names> </name></person-group><article-title>Securing reproducibility and accountability in distributed healthcare analytics: a framework based on blockchain and cryptography</article-title><source>Stud Health Technol Inform</source><year>2024</year><month>08</month><day>22</day><volume>316</volume><fpage>1269</fpage><lpage>1273</lpage><pub-id pub-id-type="doi">10.3233/SHTI240643</pub-id><pub-id pub-id-type="medline">39176613</pub-id></nlm-citation></ref><ref id="ref57"><label>57</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Dinc</surname><given-names>R</given-names> </name><name name-style="western"><surname>Ardic</surname><given-names>N</given-names> </name></person-group><article-title>An evaluation of opportunities and challenges of blockchain technology in healthcare</article-title><source>Br J Hosp Med</source><year>2024</year><month>11</month><day>30</day><volume>85</volume><issue>11</issue><fpage>1</fpage><lpage>19</lpage><pub-id pub-id-type="doi">10.12968/hmed.2024.0355</pub-id></nlm-citation></ref><ref id="ref58"><label>58</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kasyapa</surname><given-names>MSB</given-names> </name><name name-style="western"><surname>Vanmathi</surname><given-names>C</given-names> </name></person-group><article-title>Blockchain integration in healthcare: a comprehensive investigation of use cases, performance issues, and mitigation strategies</article-title><source>Front Digit Health</source><year>2024</year><volume>6</volume><fpage>1359858</fpage><pub-id pub-id-type="doi">10.3389/fdgth.2024.1359858</pub-id><pub-id pub-id-type="medline">38736708</pub-id></nlm-citation></ref><ref id="ref59"><label>59</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chafik</surname><given-names>K</given-names> </name><name name-style="western"><surname>Hanine</surname><given-names>M</given-names> </name><name name-style="western"><surname>Ouaguid</surname><given-names>A</given-names> </name><name name-style="western"><surname>Alshuhri</surname><given-names>S</given-names> </name></person-group><article-title>Blockchain technology to enhance clinical data management in healthcare: a systematic literature review</article-title><source>Blockchain Healthc Today</source><year>2026</year><volume>9</volume><issue>1</issue><pub-id pub-id-type="doi">10.30953/bhty.v9.471</pub-id><pub-id pub-id-type="medline">42205848</pub-id></nlm-citation></ref><ref id="ref60"><label>60</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Phuyal</surname><given-names>S</given-names> </name><name name-style="western"><surname>Bhandari</surname><given-names>M</given-names> </name><name name-style="western"><surname>Bista</surname><given-names>R</given-names> </name><name name-style="western"><surname>Ferreira</surname><given-names>JC</given-names> </name></person-group><article-title>Blockchain-based dynamic and revocable consent for secondary health data use: systematic review</article-title><source>JMIR Med Inform</source><year>2026</year><month>06</month><day>22</day><volume>14</volume><fpage>e88536</fpage><pub-id pub-id-type="doi">10.2196/88536</pub-id><pub-id pub-id-type="medline">42332966</pub-id></nlm-citation></ref><ref id="ref61"><label>61</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Esmaeilzadeh</surname><given-names>P</given-names> </name><name name-style="western"><surname>Mirzaei</surname><given-names>T</given-names> </name></person-group><article-title>Role of incentives in the use of blockchain-based platforms for sharing sensitive health data: experimental study</article-title><source>J Med Internet Res</source><year>2023</year><month>08</month><day>18</day><volume>25</volume><fpage>e41805</fpage><pub-id pub-id-type="doi">10.2196/41805</pub-id><pub-id pub-id-type="medline">37594783</pub-id></nlm-citation></ref><ref id="ref62"><label>62</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kim</surname><given-names>K</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Park</surname><given-names>Y</given-names> </name><etal/></person-group><article-title>A blockchain-based healthcare data marketplace: prototype and demonstration</article-title><source>JAMIA Open</source><year>2024</year><month>07</month><volume>7</volume><issue>2</issue><fpage>ooae029</fpage><pub-id pub-id-type="doi">10.1093/jamiaopen/ooae029</pub-id><pub-id pub-id-type="medline">38617993</pub-id></nlm-citation></ref><ref id="ref63"><label>63</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Subramanian</surname><given-names>H</given-names> </name></person-group><article-title>A decentralized marketplace for patient-generated health data: design science approach</article-title><source>J Med Internet Res</source><year>2023</year><month>02</month><day>27</day><volume>25</volume><fpage>e42743</fpage><pub-id pub-id-type="doi">10.2196/42743</pub-id><pub-id pub-id-type="medline">36848185</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Search strategies used in database searches.</p><media xlink:href="jmir_v28i1e96098_app1.docx" xlink:title="DOCX File, 29 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Summary of database search strategy.</p><media xlink:href="jmir_v28i1e96098_app2.docx" xlink:title="DOCX File, 22 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Complete list of included studies, health care application domains, governance functions, and evidence maturity levels.</p><media xlink:href="jmir_v28i1e96098_app3.xlsx" xlink:title="XLSX File, 142 KB"/></supplementary-material><supplementary-material id="app4"><label>Multimedia Appendix 4</label><p>Study-level characteristics, evaluation focus, blockchain/distributed ledger technology governance role, and implementation limitations of the 19 higher-maturity studies included in the focused narrative synthesis.</p><media xlink:href="jmir_v28i1e96098_app4.docx" xlink:title="DOCX File, 68 KB"/></supplementary-material><supplementary-material id="app5"><label>Checklist 1</label><p>PRISMA-ScR fillable checklist.</p><media xlink:href="jmir_v28i1e96098_app5.pdf" xlink:title="PDF File, 152 KB"/></supplementary-material></app-group></back></article>