Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Data Analytics & AI · Reviewing an emerging technology

Reviewing a Hype-Prone Technology: Blockchain for Biomedical Data Sharing

Writing a literature review on an emerging technology is a different job from writing one on a drug or a diagnostic test. The literature is mostly proposals rather than results, and the review’s central finding is usually the shape of that gap, not a synthesis of outcomes. Blockchain for biomedical data sharing is the clearest current example.

Pubrica AcademyWritten by the medical writing and biostatistics teams Reviewed byPubrica biostatistics team Published9 October 2026 Last checked9 October 2026 Reading time12 minutes Sources38 peer-reviewed

A reviewer asked to summarise “the evidence on blockchain for health data sharing’ will find hundreds of papers and almost no outcomes. The field’s own scoping reviews report that most published work sits at the conceptual or architectural stage, and that real-world demonstrations are rare enough to count individually. That is not a reason to abandon the review. It is the review’s most useful result — provided you design the review to establish it rather than to paper over it. This article uses blockchain as the worked subject to show how to review any technology whose literature runs ahead of its evidence.

What you will learn

  • How to frame a review question when the field has proposals rather than outcomes, so the review has a defensible answer either way
  • Why maturity stage belongs in your data-extraction form alongside the usual study characteristics, and how to code it
  • How to report a near-empty evidence base without either overstating the promise or dismissing the field
  • What the published blockchain-in-health reviews actually found, and how their numbers differ depending on how they screened
  • Why tracking whether an initiative is still running matters more in technology reviews than in clinical ones
  • How to write the limitations paragraph so a reviewer sees judgement rather than hedging

What to unlearn

  • “If there is a large literature, there must be evidence to synthesise.” Volume and evidence are different quantities. One scoping review of 47 biomedical blockchain articles found a single real-world demonstration among them; the rest were conceptual designs and architectures. A review that pools those as though they were studies is reporting an illusion.
  • “A technology review should conclude whether the technology works.” Often the honest conclusion is that the question is not yet answerable, and the contribution is to say precisely what would have to be measured before it could be. Editors accept that conclusion when it is argued; they reject it when it arrives as a shrug.
  • “Screening strategy is a methods detail that does not change the findings.” In this field it changes them substantially. Reviews of the same subject report 15 included papers, 16, 47, and 70, because they drew their eligibility lines in different places. Your inclusion criteria are your finding, so state them where a reader can see them working.
  • “Published once, counted forever.” Technology initiatives stop. A classification of 42 medical data-sharing initiatives found 14 of them already inactive at follow-up. A review that counts announcements rather than survivors overstates the field by a third.
  • “Privacy claims can be taken at face value.” Distributed storage and de-identification are frequently asserted as solved in this literature. They are not: re-identification risk for privacy-preserving linkage encodings rises with population size, and HIPAA’s own Safe Harbor route requires the removal of 18 identifier categories before data counts as de-identified at all.

Why an emerging-technology review is a different exercise

A review of, say, anticoagulant therapy in atrial fibrillation starts from a body of trials that measured comparable outcomes in comparable patients. The methodological work is in appraising and pooling them. A review of blockchain for biomedical data sharing starts from a body of papers that mostly propose architectures, and the methodological work is in characterising what kind of claim each paper is making 3,27.

This matters because the standard apparatus assumes outcomes exist. Risk-of-bias instruments ask how participants were allocated. Effect-size extraction assumes an effect was estimated. Applied to a conceptual architecture paper, these tools return nothing, and a reviewer who presses on anyway ends up with an empty evidence table and a discussion section that fills the space with the authors’ enthusiasm instead.

The alternative is to make maturity itself the primary variable. Instead of asking “what is the pooled effect”, ask “what proportion of this literature has been built, deployed, evaluated, or merely drawn”. That question has a real answer, the answer is informative to anyone deciding whether to invest, and it is answerable from the papers as they actually exist. Our guidance on reporting guidelines for a biomedical literature review applies here too, but the extraction form needs the extra column described below.

47biomedical blockchain articles in one scoping review
1reported a real-world demonstration

The gap between publication volume and deployed evidence, as that review’s own authors reported it.

Framing a question that survives either answer

The failure mode is a question that presupposes evidence: “How effective is blockchain at improving health data interoperability?” If the literature contains no comparative evaluations, that question has no answer and the review has no finding.

A question framed around the state of the field survives both outcomes 21. “What applications of distributed-ledger technology to biomedical data sharing have been proposed, which have been implemented, and what has been measured about them?” If it turns out that twenty controlled evaluations exist, you synthesise them. If it turns out that one deployment exists, that is the answer, and it is worth publishing.

This is the same discipline as a well-built PICO question, adapted to a subject where the intervention is a technology and the outcome is often an engineering property rather than a clinical one. Where PICO strains, say so in the methods and state the framework you used instead rather than forcing the acronym.

Health-technology subjects sit across biomedical and engineering databases, and the two index differently. A Medline and Embase search on blockchain in health care returned 152 non-duplicate peer-reviewed manuscripts, of which 15 met the inclusion criteria 15,17. A broader strategy on a related question identified 800 articles and took 70 forward for detailed review 2,26. Neither number is wrong; they describe different questions and different lines.

Two practical consequences. First, biomedical databases alone will miss much of the engineering literature, and engineering databases alone will miss the clinical framing — so record which you searched and accept the limitation explicitly rather than implying completeness. Second, terminology drifts fast: “blockchain”, “distributed ledger”, “smart contract” and now federated architectures overlap unevenly across years. A search run in August 2018, as one scoping review’s was, cannot speak to what the field looks like now, and a review that does not date its search invites the reader to assume it does 7,21,27.

Why published reviews of this subject report such different counts

Review approachRecords screenedPapers includedWhat the difference reflects
Medline and Embase, peer-reviewed only, narrow eligibility152 non-duplicate15Tight clinical framing; security and interoperability were the commonest themes, four papers each
PRISMA-ScR scoping review, search run August 2018not reported as a single figure47Scoping intent, so conceptual papers were eligible — and only one real-world demonstration was found among them
Broad empirical search across application areas800 identified70Wider net; 51 per cent concerned medical information systems and 53 per cent security and privacy
Systematic review restricted to empirical EHR worknot reported16Empirical-only filter; the included work was predominantly prototypes and pilots

Counts as reported in the four published reviews; the comparison is ours.

Adding maturity to the extraction form

This is the single change that makes an emerging-technology review useful. Alongside the usual fields, code every included paper for what stage it reached. A workable five-level scheme runs: conceptual proposal; architecture or protocol specification; prototype built; pilot deployed with real data; evaluated against a comparator 10,27.

Code it from what the paper demonstrates, not from what it claims. Papers in this field routinely describe a system in the present tense that exists only as a diagram, so the test is whether the paper reports it running on data 3,27. Where two reviewers disagree on the level, that disagreement is usually informative and belongs in your discrepancy log rather than being resolved silently.

Two further fields repay the effort. Record the platform, because concentration is itself a finding — across smart-contract implementations for clinical trials, seven of ten used private Ethereum-based networks, which tells a reader that the literature is narrower technically than its volume suggests 2. And record whether the initiative was still operating when you checked.

A maturity scale for coding an emerging-technology literature

LevelWhat the paper demonstratesWhat you can legitimately conclude from it
1. ConceptualA proposed use case, argued in proseThat someone has suggested it. Nothing about feasibility
2. ArchitectureA specified design, protocol or data modelThat the design is internally coherent, if it has been checked
3. PrototypeA built system, usually on synthetic dataThat it can be implemented; nothing about operation at scale
4. PilotDeployment with real data in a real settingFeasibility in that setting, plus whatever was measured
5. EvaluatedComparison against an incumbent or controlAn effect, within the limits of the comparison

Checking whether the thing still exists

Clinical reviews do not usually need to ask whether a trial is still running; the paper reports a completed study. Technology reviews do, because a published architecture may describe a project that was abandoned two years ago, and the paper will never say so 1.

A classification of 42 medical data-sharing initiatives found 28 still active and 14 inactive 1. Reporting only the 42 would have overstated the live field by a third. The check is tedious — project pages, repository commit history, follow-up publications, sometimes a direct enquiry — but it converts a bibliography into a picture of what actually exists, and no other step in the review adds as much for the effort.

Date the check and say how you made it, exactly as you would date a search. An initiative counted as active in your review may be gone by the time it is read, and a dated method lets the reader adjust rather than mistrust.

42medical data-sharing initiatives classified
28still active when checked
14already inactive

Counting announcements rather than survivors overstated this field by a third. The active-status check is what separates the two numbers.

Appraising privacy and security claims rather than repeating them

Papers in this field make two recurring claims that a review should test rather than relay: that distribution removes the need to trust a custodian, and that the data on the ledger is de-identified and therefore safe to share 30.

Both deserve scrutiny. Re-identification risk is a function of population size and of what is shared alongside the encoded identifiers: for privacy-preserving record-linkage encodings released with de-identified demographics, modelled risk rose from under 1 per cent at populations below a million to roughly 10 to 20 per cent at 250 million 2,5. And de-identification is a legal standard, not a gesture — HIPAA recognises two permitted methods, the Safe Harbor route requiring removal of 18 categories of identifier 34. A paper that says “patient data are de-identified before being written to the chain” without saying by which method has not established the claim.

It is also worth noting what the alternatives achieve, because reviews in this field often omit the comparator 17,20,22. A controlled-access archive model distributes sensitive genomic data at very large scale — more than 4,500 studies and 6,800 datasets, approaching 15 petabytes — without any open release and without a distributed ledger 15,17. A review that never mentions the incumbent cannot assess whether the new architecture is needed.

Writing up a thin evidence base honestly

The discussion section is where these reviews are usually lost. Two failure modes recur. The first is advocacy: the evidence is thin, so the authors argue from potential, and the review reads as a prospectus. The second is dismissal: the evidence is thin, so the authors conclude the technology is overhyped, which the review has not actually shown either.

The defensible middle is specific. Say what stage the literature has reached, with counts. Say what has been measured and what has not. Then say what would change the picture — which comparison, in which setting, reporting which outcome, would move the field from architecture to evidence. That last move is what makes the review citable, because it gives the next group something to do.

Where you have human-factors evidence, use it: in-depth interviews with 38 physicians on blockchain-based health information exchange surfaced concerns that no architecture paper raises 13. Qualitative work is often the only empirical material available in an immature field, and it should be reported as evidence rather than as background colour 8,13.

The results paragraph of a technology review

Reports volume as though it were evidence

Our search identified a rapidly growing body of research demonstrating the significant potential of blockchain technology to transform biomedical data sharing. Numerous studies have shown that blockchain can improve data security, patient control and interoperability across institutions, and the literature indicates that adoption is accelerating.

“Significant potential”, “numerous studies” and “the literature indicates” are unfalsifiable. None of them can be checked against the extraction table, which is the test a reviewer applies.

“Studies have shown that blockchain can improve data security” converts architectural claims into demonstrated outcomes. If no included paper measured security against a comparator, this sentence is not supported by the review that contains it.

“Adoption is accelerating” is a claim about the world, not about the literature, and the review has no data bearing on it — particularly with a third of initiatives in the adjacent classification already inactive.

Reports maturity, which is what was actually found

Our search returned 152 non-duplicate peer-reviewed manuscripts, of which 15 met the inclusion criteria. Fourteen of the 15 were at conceptual or prototype stage; one reported deployment with real patient data, and none compared the architecture against the institution’s existing data-sharing arrangement. Security and interoperability were the dominant themes, four papers each. We therefore characterise the field as pre-evaluative: the design space has been explored, and the comparative evidence base has not yet been started.

Every number is traceable to the extraction table, so a reviewer can verify the paragraph rather than take it on trust.

“Pre-evaluative” is a finding with content: it says the design work has happened and the comparative work has not, which is exactly what a reader deciding whether to fund a pilot needs to know.

Naming what is absent — no comparison against the incumbent arrangement — tells the next research group what to do, which is where a review of an immature field earns its citations.

Reviewers in this field have read many enthusiastic summaries and few disciplined ones; the second version is harder to write and considerably harder to reject.

What a reviewer will look for

Editors handling these reviews tend to probe the same four places. Is the search dated, and are both the biomedical and engineering sides accounted for? Are inclusion criteria stated tightly enough to explain why your count differs from the neighbouring review’s? Is the maturity of the included work characterised, or has it been flattened into “studies”? And does the conclusion follow from the extraction table rather than from the introduction’s enthusiasm?

A review that answers those four cleanly will survive peer review even with fifteen included papers and no pooled estimate. One that answers none of them will struggle with seventy.

Take-home message

Take-home message

When a technology’s literature runs ahead of its evidence, the review’s job changes from synthesising outcomes to characterising maturity, and that is a legitimate, publishable finding rather than a failed review. Frame the question so it survives either answer, search both the biomedical and the engineering sides and date the search, add a maturity level and an active-status check to the extraction form, and appraise privacy and security claims against the actual legal and statistical standards instead of relaying them. Published blockchain reviews of the same subject report 15, 16, 47 and 70 included papers because they drew eligibility differently — so state your criteria where the reader can see them working. Then write a discussion that says what stage the field has reached, what has not been measured, and which single comparison would move it forward.

How to apply this to your study

How to apply this to your own study

  1. Rewrite your question until it survives a null finding. If the honest answer turns out to be “one deployment exists”, your question should still have been worth asking. If it would not, reframe it around what has been proposed, built and measured.
  2. Add two columns to your extraction form. A maturity level from the five-point scale above, coded from what the paper demonstrates rather than what it asserts, and whether the initiative was still operating on the date you checked.
  3. Search both literatures and say so. Record the biomedical databases and the engineering ones separately, date the search, and list the term variants you covered — distributed ledger and smart contract as well as blockchain.
  4. Test every privacy claim against a named standard. If a paper says data were de-identified, note by which method; if it claims re-identification is infeasible, note at what population size, because the risk is not constant.
  5. Name the incumbent. Identify how the problem is currently solved without the new technology, and say whether any included paper compared the two. Usually none has, and that absence is a finding.
  6. End with the missing study. Specify the comparison, setting and outcome that would convert this literature from architecture into evidence, in enough detail that a reader could design it.

Common questions

Yes, provided the review is designed to establish that and says so plainly. Reviews reporting that a field is predominantly conceptual are published regularly and cited heavily, because funders and research groups need to know where a technology actually stands. What editors reject is a review that found a thin evidence base and wrote the discussion as though it had found a strong one. Characterise the maturity of what you found, give the counts, and state what would have to be measured next.

Because they drew their eligibility lines in different places, and in an immature field that choice dominates the count. One Medline and Embase review screened 152 non-duplicate manuscripts and included 15. A PRISMA-ScR scoping review, which by design admits conceptual papers, included 47. A broader empirical search identified 800 records and took 70 forward. A review restricted to empirical electronic health record work included 16. None of these is incorrect; they answer different questions. The implication for your own review is that inclusion criteria are a finding in their own right and need to be stated where a reader can see them operating.

Three things. A maturity level, coded from what the paper demonstrates rather than claims, which lets you report the stage distribution of the field. The platform or technical approach, because concentration is informative — across smart-contract implementations for clinical trials, seven of ten used private Ethereum-based networks. And the operating status of the initiative on a stated date, since technology projects stop without publishing a retraction. A classification of 42 medical data-sharing initiatives found 14 already inactive.

Ask by which method, and at what scale. De-identification under HIPAA is a legal standard with two permitted routes, the Safe Harbor route requiring removal of 18 categories of identifier, so a paper that asserts de-identification without naming a method has not established it. Re-identification risk also varies with population size rather than being fixed: for privacy-preserving record-linkage encodings shared alongside de-identified demographics, modelled risk rose from under 1 per cent below a million individuals to roughly 10 to 20 per cent at 250 million. Record what the paper actually tested, and treat untested assertions as assertions.

Not as a criticism, no — every technology passes through that stage, and prototype work is how a design space gets explored. The criticism is reserved for papers that present prototype work in language implying deployment, and for reviews that aggregate prototypes as though they were evaluations. Reporting that a literature is predominantly prototypes and pilots is a neutral description of where the field has got to, and it is the most useful single sentence such a review can contain.

Yes, and in an immature field they are often the only empirical material available. In-depth interviews with 38 physicians about blockchain-based health information exchange surfaced adoption concerns that no architecture paper addresses, and a survey-based adoption model was tested across 199 hospitals. Treat these as evidence and extract from them properly rather than relegating them to the introduction. Our guidance on qualitative research alongside quantitative work applies.

You cannot entirely, and the fix is transparency rather than speed. Date the search, date the operating-status check, and state the window your conclusions cover. A scoping review whose search ran in August 2018 described the field as it stood then, which is a legitimate contribution provided it is read that way. Reviews that omit these dates invite readers to assume currency they do not have, which is what makes them age badly rather than simply age.

Whether the conclusion is traceable to the extraction table. Reviewers in this area have read a great many summaries arguing from potential, so a review that reports stage distributions with counts, names what has not been measured, and specifies the comparison that would advance the field stands out immediately. The citable contribution in an immature field is rarely a pooled estimate; it is a clear statement of where the frontier sits and what sits just beyond it.

References and sources

  1. Cunningham J, Davies N, Devaney S, Harding M, Holm S, Neumann V, Smith C, Ainsworth J. A Review of Medical Data Sharing Initiatives With a Focus on the Use of Blockchain Technologies: Qualitative Comparative Analysis. Journal of Medical Internet Research. 2026;28:e63575. doi:10.2196/63575 read 9 October 2026. doi.org/10.2196/63575
  2. Sheikh Z, Samarth G, Jaffer U. Blockchain Smart Contracts for Automating Clinical Trials: Systematic Review and Proposed System Architecture. JMIR Medical Informatics. 2026;14(1):e76980. doi:10.2196/76980 read 9 October 2026. doi.org/10.2196/76980
  3. Chandak A, Chandak P, Soni N. Blockchain applications in electronic health records: a systematic review of qualitative and quantitative evidence. BMC Medical Informatics and Decision Making. 2026;26(1):176. doi:10.1186/s12911-026-03476-3 read 9 October 2026. doi.org/10.1186/s12911-026-03476-3
  4. European Data Protection Board. Guidelines 1/2026 on processing of personal data for scientific research purposes (version for public consultation). European Data Protection Board. 2026. read 9 October 2026. edpb.europa.eu
  5. Eliazar A, Brown JT, Cinamon S, Kantarcioglu M, Malin B. Re-identification risk for common privacy preserving patient matching strategies when shared with de-identified demographics. Journal of the American Medical Informatics Association. 2026;33(2):336-346. doi:10.1093/jamia/ocaf183 read 9 October 2026. doi.org/10.1093/jamia/ocaf183
  6. European Medicines Agency. Real-world evidence (Data Analysis and Real World Interrogation Network, DARWIN EU). European Medicines Agency. 2026. read 9 October 2026. ema.europa.eu
  7. Wang X, Xie Y, Chen X, Yang J, Li R, Gao W, Yan Z, Zhou H, Ye Z. Securing Federated Learning With Blockchain in the Medical Field: Systematic Literature Review. Journal of Medical Internet Research. 2026;28(1):e79052. doi:10.2196/79052 read 9 October 2026. doi.org/10.2196/79052
  8. Bazel MA, Mohammed F, Ahmad M, Baarimah AO, Al Maskari T, et al. Blockchain technology adoption in healthcare: an integrated model. Scientific Reports. 2025;15(1):14111. doi:10.1038/s41598-025-95253-x read 9 October 2026. doi.org/10.1038/s41598-025-95253-x
  9. Cheng AC, Shyr C, Lewis A, Delacqua F, Bosler T, Banasiewicz MK, Taylor R, Lindsell CJ, Harris PA. Opportunities, barriers, and remedies for implementing REDCap integration with electronic health records via Fast Healthcare Interoperability Resources (FHIR). JAMIA Open. 2025;8(5):ooaf111. doi:10.1093/jamiaopen/ooaf111 read 9 October 2026. doi.org/10.1093/jamiaopen/ooaf111
  10. Lacson R, Yu Y, Kuo TT, Ohno-Machado L. Biomedical blockchain with practical implementations and quantitative evaluations: a systematic review. 2024. doi:10.1093/jamia/ocae084 read 9 October 2026. doi.org/10.1093/jamia/ocae084
  11. Parker G. Future of Electronic Health Records: A Challenge to Maximize Their Utility. SSRN Electronic Journal. 2023. doi:10.2139/ssrn.4457214 read 9 October 2026. doi.org/10.2139/ssrn.4457214
  12. Walker DM, Tarver WL, Jonnalagadda P, Ranbom L, Ford EW, Rahurkar S. Perspectives on Challenges and Opportunities for Interoperability: Findings From Key Informant Interviews With Stakeholders in Ohio. JMIR Medical Informatics. 2023;11(1):e43848. doi:10.2196/43848 read 9 October 2026. doi.org/10.2196/43848
  13. Esmaeilzadeh P. Benefits and concerns associated with blockchain-based health information exchange (HIE): a qualitative study from physicians' perspectives. BMC Medical Informatics and Decision Making. 2022;22(1):80. doi:10.1186/s12911-022-01815-8 read 9 October 2026. doi.org/10.1186/s12911-022-01815-8
  14. Hu C, Li C, Zhang G, Lei Z, Shah M, Zhang Y, Xing C, Jiang J, et al. CrowdMed-II: a blockchain-based framework for efficient consent management in health data sharing. World Wide Web. 2022;25(3):1489-1515. doi:10.1007/s11280-021-00923-1 read 9 October 2026. doi.org/10.1007/s11280-021-00923-1
  15. Schmeelk S, Kanabar M, Peterson K, Pathak J. Electronic health records and blockchain interoperability requirements: a scoping review. JAMIA Open. 2022;5(3):ooac068. doi:10.1093/jamiaopen/ooac068 read 9 October 2026. doi.org/10.1093/jamiaopen/ooac068
  16. Zeng B, Bove R, Carini S, Lee JSJ, Pollak JP, Schleimer E, Sim I. Standardized Integration of Person-Generated Data Into Routine Clinical Care. JMIR mHealth and uHealth. 2022;10(2):e31048. doi:10.2196/31048 read 9 October 2026. doi.org/10.2196/31048
  17. Freeberg MA, Fromont LA, D'Altri T, Foix Romero A, Izquierdo Ciges J, Jene A, Kerry G, Moldes M, et al. The European Genome-phenome Archive in 2021. Nucleic Acids Research. 2022;50(D1):D980-D987. doi:10.1093/nar/gkab1059 read 9 October 2026. doi.org/10.1093/nar/gkab1059
  18. Lingard L, Colquhoun H. The story behind the synthesis: writing an effective introduction to your scoping review. Perspectives on Medical Education. 2022;11(5):289-294. doi:10.1007/s40037-022-00719-7 read 9 October 2026. doi.org/10.1007/s40037-022-00719-7
  19. Albalwy F, Brass A, Davies A. A Blockchain-Based Dynamic Consent Architecture to Support Clinical Genomic Data Sharing (ConsentChain): Proof-of-Concept Study. JMIR Medical Informatics. 2021;9(11):e27816. doi:10.2196/27816 read 9 October 2026. doi.org/10.2196/27816
  20. Sarma KV, Harmon S, Sanford T, Roth HR, Xu Z, Tetreault J, Xu D, Flores MG, Raman AG, Kulkarni R, Wood BJ, Choyke PL, Priester AM, Marks LS, Raman SS, Enzmann D, Turkbey B, Speier W, Arnold CW. Federated learning improves site performance in multicenter deep learning without data sharing. Journal of the American Medical Informatics Association. 2021;28(6):1259-1264. doi:10.1093/jamia/ocaa341 read 9 October 2026. doi.org/10.1093/jamia/ocaa341
  21. Peters MDJ, Marnie C, Colquhoun H, Garritty CM, Hempel S, Horsley T, Langlois EV, Lillie E, O'Brien KK, Tuncalp O, Wilson MG, Zarin W, Tricco AC. Scoping reviews: reinforcing and advancing the methodology and application. Systematic Reviews. 2021;10(1):263. doi:10.1186/s13643-021-01821-3 read 9 October 2026. doi.org/10.1186/s13643-021-01821-3
  22. Froelicher D, Troncoso-Pastoriza JR, Raisaro JL, Cuendet MA, Sa Sousa J, Cho H, Berger B, Fellay J, et al., Hubaux JP. Truly privacy-preserving federated analytics for precision medicine with multiparty homomorphic encryption. Nature Communications. 2021;12(1):5910. doi:10.1038/s41467-021-25972-y read 9 October 2026. doi.org/10.1038/s41467-021-25972-y
  23. Office of the National Coordinator for Health Information Technology, U.S. Department of Health and Human Services. 21st Century Cures Act: Interoperability, Information Blocking, and the ONC Health IT Certification Program (final rule). Federal Register. 2020;85:25642-25961. read 9 October 2026. federalregister.gov
  24. Dubovitskaya A, Baig F, Xu Z, Shukla R, Zambani PS, Swaminathan A, Jahangir MM, Chowdhry K, Lachhani R, Idnani N, Schumacher M, Aberer K, Stoller SD, Ryu S, Wang F. ACTION-EHR: Patient-Centric Blockchain-Based Electronic Health Record Data Management for Cancer Care. Journal of Medical Internet Research. 2020;22(8):e13598. doi:10.2196/13598 read 9 October 2026. doi.org/10.2196/13598
  25. Chang SE, Chen Y. Blockchain in Health Care Innovation: Literature Review and Case Study From a Business Ecosystem Perspective. Journal of Medical Internet Research. 2020;22(8):e19480. doi:10.2196/19480 read 9 October 2026. doi.org/10.2196/19480
  26. Durneva P, Cousins K, Chen M. The Current State of Research, Challenges, and Future Research Directions of Blockchain Technology in Patient Care: Systematic Review. Journal of Medical Internet Research. 2020;22(7):e18619. doi:10.2196/18619 read 9 October 2026. doi.org/10.2196/18619
  27. Drosatos G, Kaldoudi E. Blockchain Applications in the Biomedical Domain: A Scoping Review. 2019. read 9 October 2026. client.nup.ac.cy
  28. Ronquillo JG, Winterholler JE, Cwikla K, Szymanski R, Levy C. Health IT, hacking, and cybersecurity: national trends in data breaches of protected health information. JAMIA Open. 2018;1(1):15-19. doi:10.1093/jamiaopen/ooy019 read 9 October 2026. doi.org/10.1093/jamiaopen/ooy019
  29. Maslove DM, Klein J, Brohman K, Martin P. Using Blockchain Technology to Manage Clinical Trials Data: A Proof-of-Concept Study. JMIR Medical Informatics. 2018;6(4):e11949. doi:10.2196/11949 read 9 October 2026. doi.org/10.2196/11949
  30. Kuo TT, Kim HE, Ohno-Machado L. Blockchain distributed ledger technologies for biomedical and health care applications. Journal of the American Medical Informatics Association. 2017;24(6):1211-1220. doi:10.1093/jamia/ocx068 read 9 October 2026. doi.org/10.1093/jamia/ocx068
  31. Benchoufi M, Ravaud P. Blockchain technology for improving clinical research quality. Trials. 2017;18(1):335. doi:10.1186/s13063-017-2035-z read 9 October 2026. doi.org/10.1186/s13063-017-2035-z
  32. Wilkinson MD, Dumontier M, Aalbersberg IJ, et al. (53 authors; Mons B last). The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data. 2016;3:160018. doi:10.1038/sdata.2016.18 read 9 October 2026. doi.org/10.1038/sdata.2016.18
  33. Adler-Milstein J, Jha A. Health information exchange among U.S. hospitals: who's in, who's out and why? Healthcare. 2014;2(1):26-32. read 9 October 2026. help.senate.gov
  34. Office for Civil Rights, U.S. Department of Health and Human Services. Guidance Regarding Methods for De-identification of Protected Health Information in Accordance with the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule. U.S. Department of Health and Human Services. 2012. read 9 October 2026. hhs.gov
  35. Widdows H, Cordell S. The Ethics of Biobanking: Key Issues and Controversies. Health Care Analysis. 2011;19(3):207-219. doi:10.1007/s10728-011-0184-x read 9 October 2026. doi.org/10.1007/s10728-011-0184-x
  36. Kuraitis V, McNicoll I. read 9 October 2026. e-caremanagement.com
  37. Journal of the American Medical Informatics Association. doi:10.1093/jamia/ocab289 read 9 October 2026. doi.org/10.1093/jamia/ocab289
  38. Directorate-General for Health and Food Safety, European Commission. Reuse of health data (European Health Data Space: secondary use of health data). European Commission. read 9 October 2026. health.ec.europa.eu

Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.

How to cite this article

Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.

Pubrica Academy. (2026, October 9). Reviewing a Hype-Prone Technology: Blockchain for Biomedical Data Sharing. Pubrica. https://pubrica.com/academy/latest-topics/advancement-in-block-chain-technology-for-data-sharing-in-biomedical-research-the-key-factors-in-writing-a-literature-review/

This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.

Extraction form additions and a results paragraph stub

The two columns a technology review needs that a clinical one does not, plus a results-paragraph skeleton that forces every claim back to the table. Fill the blanks from your own extraction sheet.

EXTRACTION FORM -- ADDITIONAL COLUMNS

  MATURITY LEVEL  (code from what the paper DEMONSTRATES, not what it claims)
    [ ] 1 conceptual   -- a use case argued in prose
    [ ] 2 architecture -- a specified design, protocol or data model
    [ ] 3 prototype    -- built, usually on synthetic data
    [ ] 4 pilot        -- deployed with real data in a real setting
    [ ] 5 evaluated    -- compared against an incumbent or control
    Coder 1: ____   Coder 2: ____   Agreed: ____   Disagreement logged? [ ]

  PLATFORM / APPROACH  ______________________________________
    public ledger [ ]   private / permissioned [ ]   consortium [ ]
    off-chain storage used? [ ] yes  [ ] no  [ ] not stated

  OPERATING STATUS
    Still running on ____________ (date checked)?  [ ] yes [ ] no [ ] cannot tell
    Evidence used: project page [ ]  repository activity [ ]
                   follow-up publication [ ]  direct enquiry [ ]

  PRIVACY CLAIM MADE?  [ ] yes  [ ] no
    De-identification method named?  [ ] yes  [ ] no
    Re-identification risk quantified, and at what population size? ________
    Compared against the incumbent arrangement?  [ ] yes  [ ] no


RESULTS PARAGRAPH STUB

  "Our search of ____________________ (databases), run on ____________
   (date), returned ______ non-duplicate records, of which ______ met the
   inclusion criteria.

   Of the ______ included papers, ______ were at conceptual or architecture
   stage, ______ reported a prototype, ______ reported a pilot with real
   data, and ______ reported a comparison against an existing arrangement.

   The dominant themes were ______________________ (n=__) and
   ______________________ (n=__).

   Of the ______ initiatives we could trace, ______ were still operating as
   at ____________ (date checked).

   We therefore characterise this literature as ____________________
   (pre-evaluative / early-evaluative / mature), and note that no included
   study measured ______________________ against ______________________."


DISCUSSION -- THE MISSING STUDY  (close with this, not with potential)

  "The comparison that would move this field from design to evidence is
   ______________________ (intervention) against ______________________
   (incumbent), in ______________________ (setting), reporting
   ______________________ (outcome) over ____________ (period)."

Pubrica AcademyWritten and maintained by the subject matter experts of Pubrica who do this work. Articles are revised when the standard underneath them moves, and each one carries the date it was last checked.

How Pubrica helps

Pubrica’s medical writing and biostatistics teams build the extraction framework before the screening starts, which is where emerging-technology reviews are usually won or lost. We code maturity independently in duplicate, run the operating-status check, and write the results and discussion so that every claim is traceable to a row in the table.

Find something else

Search the rest of the Academy.

Open with no account. Type what you are working on, or open the full library to filter by category, sub-topic or resource type.

Send us your review question and we will return the extraction framework and a realistic view of what the literature can support.

A scoping read costs nothing and takes two business days. You get a written view of what the work needs and who would hold it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.