CoChat

Blockchain vehicles for efficient Medical Record management

Open access

The DOI matches its Crossref record; 16 of the 16 references it cites were found in a registry or an index.

Abstract

The lack of interoperability in Britain’s medical records systems precludes the realisation of benefits generated by increased spending elsewhere in healthcare. Growing concerns regarding the security of online medical data following breaches, and regarding regulations governing data ownership, mandate strict parameters in the development of efficient methods to administrate medical records. Furthermore, consideration must be placed on the rise of connected devices, which vastly increase the amount of data that can be collected in order to improve a patient’s long-term health outcomes. Increasing numbers of healthcare systems are developing Blockchain-based systems to manage medical data. A Blockchain is a decentralised, continuously growing online ledger of records, validated by members of the network. Traditionally used to manage cryptocurrency records, distributed ledger technology can be applied to various aspects of healthcare. In this manuscript, we focus on how Electronic Medical Records in particular can be managed by Blockchain, and how the introduction of this novel technology can create a more efficient and interoperable infrastructure to manage records that leads to improved healthcare outcomes, while maintaining patient data ownership and without compromising privacy or security of sensitive data.

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1038/s41746-019-0211-0

Cites

16 of 16 references verified0 citation errors · 0 not checkable

Statistics

Figures

Fig. 1 Progress of a Blockchain transaction. Public-key cryptography creates a public and a private key for each user, using a one-way hash function to create the public from the private key. The public keys are used by the sender and receiver of a transaction to identify each other. Private keys remain undisclosed, and are used by the sender and receiver to sign and verify transactions, respectively. Here, User 1 sends a transaction to User 2, using User 2’s Public key. User 2 receives the transaction, identified as having been sent by User 1’s public key.
Fig. 1 Progress of a Blockchain transaction. Public-key cryptography creates a public and a private key for each user, using a one-way hash function to create the public from the private key. The public keys are used by the sender and receiver of a transaction to identify each other. Private keys remain undisclosed, and are used by the sender and receiver to sign and verify transactions, respectively. Here, User 1 sends a transaction to User 2, using User 2’s Public key. User 2 receives the transaction, identified as having been sent by User 1’s public key.CC BY · PubMed Central
Fig. 2 Interactions in the Blockchain-based healthcare system. Patients have full access to the data via the EMR Client. Data may be added or viewed by doctors and other providers, who require permissions to do so, and added by devices including wearables, which form a part of the Internet of Things (IoT). All interactions are stored on the Blockchain.
Fig. 2 Interactions in the Blockchain-based healthcare system. Patients have full access to the data via the EMR Client. Data may be added or viewed by doctors and other providers, who require permissions to do so, and added by devices including wearables, which form a part of the Internet of Things (IoT). All interactions are stored on the Blockchain.CC BY · PubMed Central
Fig. 3 Connecting independent healthcare providers. Each box represents a Blockchain ledger. The Patient Directory lists all pseudonymised patients about whom data is stored across all providers’ Blockchain ledgers. Associated with each patient is a pointer to all centres (represented by number) where that individual has had a medical interaction. Individual Centres store their own ledgers, containing more detailed metadata (represented by code, e.g. Data A1, which does not imply storage of sensitive medical information) about interactions with patients, including associated cloud-based data storage locations and access permission information. When a Centre joins the system (e.g. Centre 3), basic pseudonymised information about its patients is relayed to the Patient Directory, allowing other Centres to access that information, subject to any associated smart contract-based permissions.
Fig. 3 Connecting independent healthcare providers. Each box represents a Blockchain ledger. The Patient Directory lists all pseudonymised patients about whom data is stored across all providers’ Blockchain ledgers. Associated with each patient is a pointer to all centres (represented by number) where that individual has had a medical interaction. Individual Centres store their own ledgers, containing more detailed metadata (represented by code, e.g. Data A1, which does not imply storage of sensitive medical information) about interactions with patients, including associated cloud-based data storage locations and access permission information. When a Centre joins the system (e.g. Centre 3), basic pseudonymised information about its patients is relayed to the Patient Directory, allowing other Centres to access that information, subject to any associated smart contract-based permissions.CC BY · PubMed Central

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

4 more claims about this paper

Create a free account to see every claim other papers make about this one.

See all claims — free account

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 16 references

Cited by

See all 245

Metadata

Authors
Vazirani, A. A., O’Donoghue, O., Brindley, D., & Meinert, E.
Affiliations
University of Oxford (GB)
Corresponding author
Meinert, Edward
Venue
npj Digital Medicine
Published
2020-01-06
Volume
3
Issue
1
Pages
1-1
ISSN
2398-6352 (ISSN-L)
OpenAlex
W2990170027
Cited by
245
References
16
Citations by year
2026: 7 · 2025: 30 · 2024: 28 · 2023: 42 · 2022: 57 · 2021: 63 · 2020: 18
FWCI
6.64
Type
journal article
Language
en
Open access
Licence
Locations
  • npj Digital Medicine (publishedVersion, cc-by)
  • Europe PMC (PubMed Central) (publishedVersion, cc-by)
  • PubMed Central (publishedVersion, cc-by)
  • PubMed (publishedVersion)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion, cc-by-sa)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion)
  • Spiral (Imperial College London) (submittedVersion, cc-by)
  • Newcastle University ePrints (Newcastle Univesity) (cc-by)
Funders
  • Sir David Cooksey Fellowship in Healthcare Translation
  • Final Honour School of Medical Sciences, Cell & Systems, Biology and Neuroscience
Topics
  • Physical Sciences › Computer Science › Information Systems › Blockchain Technology Applications and Security
  • Health Sciences › Health Professions › Health Information Management › Electronic Health Records Systems
  • Physical Sciences › Computer Science › Information Systems › Blockchain Technology in Education and Learning
Keywords
blockchain, electronic health records, distributed ledger technology, patient data ownership, data security, privacy, connected health devices, health data management

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Blockchain vehicles for efficient Medical Record management. https://app.cochat.ai/papers/10.1038/s41746-019-0211-0
The paper
Vazirani, A. A., O’Donoghue, O., Brindley, D., & Meinert, E. (2020). Blockchain vehicles for efficient Medical Record management. npj Digital Medicine. https://doi.org/10.1038/s41746-019-0211-0

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.