Comparison of Blockchain Platforms A Systematic Re
Comparison of Blockchain Platforms A Systematic Re
doi: 10.1093/jamia/ocy185
Review
Review
Corresponding Author: Lucila Ohno-Machado, MD, PhD, UCSD Health Department of Biomedical Informatics, University
of California San Diego, La Jolla, California, USA ([email protected]).
Received 16 June 2018; Revised 2 December 2018; Editorial Decision 11 December 2018; Accepted 7 January 2019
ABSTRACT
Objectives: To introduce healthcare or biomedical blockchain applications and their underlying blockchain plat-
forms, compare popular blockchain platforms using a systematic review method, and provide a reference for
selection of a suitable blockchain platform given requirements and technical features that are common in
healthcare and biomedical research applications.
Target audience: Healthcare or clinical informatics researchers and software engineers who would like to learn
about the important technical features of different blockchain platforms to design and implement blockchain-
based health informatics applications.
Scope: Covered topics include (1) a brief introduction to healthcare or biomedical blockchain applications and
the benefits to adopt blockchain; (2) a description of key features of underlying blockchain platforms in health-
care applications; (3) development of a method for systematic review of technology, based on the PRISMA
(Preferred Reporting Items for Systematic Reviews and Meta-Analyses) statement, to investigate blockchain
platforms for healthcare and medicine applications; (4) a review of 21 healthcare-related technical features of 10
popular blockchain platforms; and (5) a discussion of findings and limitations of the review.
Key words: blockchain, distributed ledger technology, systematic review, PRISMA, health and Medicine
C The Author(s) 2019. Published by Oxford University Press on behalf of the American Medical Informatics Association.
V
This is an Open Access article distributed under the terms of the Creative Commons Attribution-NonCommercial-NoDerivs licence (http://creativecommons.org/licenses/by-
nc-nd/4.0/), which permits non-commercial reproduction and distribution of the work, in any medium, provided the original work is not altered or transformed in any way,
and that the work is properly cited. For commercial re-use, please [email protected] 462
Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5 463
Key benefits of blockchain for healthcare Hyperledger. An oncology clinical data sharing framework10 for
The main reason for the abovementioned applications to adopt patient care proposes to adopt the Hyperledger platform.43 Also,
blockchain relies on its “off-the-shelf” features that address many Hyperledger was included in the design of a framework to enforce
real-world health science’s needs. For example, decentralized man- Institutional Review Board regulations.11 Additionally, Hyperledger
agement is very useful for organizing digital assets produced by vari- is proposed for a mobile healthcare application44 and for medical
ous institutions (eg, biomedical data, software, and “recipes” or data storage or access45 applications. A working group was formed
workflows frequently used in predictive modeling and analytics). by Hyperledger to cultivate technical or business collaborations for
This allows operations without a hub (ie, no single point of healthcare blockchain applications.46
“ownership” or “control”). This characteristic is especially attrac- MultiChain. ModelChain29 was used to accelerate research and
tive for applications in which users prefer not to rely on a single cen- facilitate quality improvement initiatives by supporting decentral-
tral authority (eg, federated clinical data networks for quality ized cross-institutional predictive modeling. The use of blockchain
improvement, health insurance operations, cross-institutional con- in ModelChain makes it possible for different institutions to im-
sent management without the need for a coordinating center) and in prove predictive power by contributing data to a jointly developed
3. Approval
2. Request
1. Request Block Block Block
4. Approval
Patient P1 8. Inspect TC1 TC2 TC3 Clinician C1
(Emergency Department) Blockchain (Emergency Department)
(Transactions of Clinical Data Access)
(b)
Figure 1. Healthcare and research examples of immutable recording of transactions. Note that in both examples the actual patient data are stored off-chain and
only the access records (eg, requests for and receipts of records) are stored on-chain as transactions in blocks. (A) Health informatics exchange example: Patient
P1 requests use of data by Clinician C1, institution I1 provides access, and patient P1 and/or primary care clinician C2 are able to see the transaction. (B) Human
subject research example: researcher R1 requests use of trial data, institution I2 provides access, and participant P2 and/or principal investigator R2 are able to see
the transaction.
research frameworks,53 and systematic reviews of blockchain tech- provide a reference for selection of suitable blockchain plat-
nology articles,4 a systematic comparison of blockchain platforms forms for specific requirements encountered in healthcare and
that are relevant for healthcare is still lacking. Such systematic com- biomedicine.
parison can serve as a practical reference for healthcare blockchain
researchers and application designers to choose the appropriate plat-
form for their specific use case (eg, public health, administration,
clinical care), especially, as mentioned previously, in the setting of MATERIALS AND METHODS
healthcare or research institutions that prefer not to cede control to
We adapted the PRISMA (Preferred Reporting Items for System-
a central authority but want to work together.
atic Reviews and Meta-Analyses) statement54,55 to compare block-
chain platforms. PRISMA is a systematic review statement
Objective focusing on reviews that evaluate randomized trials.54,55 To re-
The objective of this study is to compare the most popular block- view blockchain platforms, we modified the checklist items (Sup-
chain platforms using a systematic method, considering the tech- plementary Table S1) and flow diagram (Figure 6) in PRISMA,
nical features that are relevant to healthcare applications, and to and conducted the systematic comparison based on adjusted items.
Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5 465
... Hash of Block B0 Header Nonce N1 Hash of Block B1 Header Nonce N2 ...
Hash of T11 Hash of T12 Hash of T13 Hash of T14 Hash of T15 Hash of T16 Hash of T17 Hash of T18
Figure 2. To reduce storage, if a block B is “voted” to be correct because the chain is long enough (ie, there are already many blocks created after B), we can dis-
card the transactions contained in B, without changing the hash of B’s header (otherwise all blocks after B would need to be changed). To do this, instead of sav-
ing the content of all transactions directly in a block, we first compute the hash values of each transaction, and then construct a tree structure (a Merkle tree),26–28
to “combine” (ie, hash again) all hash values, and store only the Merkle Root hash value at the block header. This way we can prune the transactions in the tree
later, without changing the Merkle Root and the block header. In other words, the size of the blockchain is now proportional to the number of blocks instead of be-
ing proportional to the number of transactions. (A) An example blockchain without a Merkle tree. The blocks enclose transactions without adopting a Merkle tree.
As a result, the size of a block will grow proportionally to the number of transactions (eg, transaction T12) that are enclosed. (B) A blockchain with a Merkle tree. A
Merkle tree is constructed by hashing paired data (the leaves) to create a parent node iteratively, until a single hash, the Merkle Root,1 remains. In this example,
the transactions (eg, T12) are first encoded into a binary raw-transaction format and then hashed to create the hashes (eg, Hash of T12). Then, hashes such as the
Hash of T12 are paired with other hashes such as the Hash of T11 (if a hash does not have a pair, it simply duplicates itself to be paired) to compute the hash as
their parent node (ie, Hash of T11–12). The pairing/hashing process repeats until only 1 hash (the Merkle Root) remains, and the Merkle tree construction process
is then completed. Finally, by only enclosing the Merkle Root in each block header, the storage space required to verify the integrity/validity of transactions can
be reduced.56 That is, if an attacker tries to change the content of any transaction such as T12, all of the related hashes (ie, Hash of T12, Hash of T11–12, and Hash of
T11–14), and eventually the Merkle Root (ie, Hash of T11–18) will also change and can be easily verified. To enclose this new Merkle Root to pass the verification pro-
cess, the attacker then needs to re-create block B1 and all blocks thereafter, which is computationally expensive and is enough to prevent such modification.2,57 A
Merkle tree is the basis of lightweight nodes described in Figure 3 (ie, the blockchain nodes that only need to verify transactions can store parts of the Merkle
trees to save space, while the full blockchain nodes that need to “mine” new blocks store all of the Merkle trees).
Eligibility criteria and information sources chain platforms names found in these webpages into a candidate list
General purpose blockchain platforms were included. We excluded (see the identification phase in Figure 6).
cryptocurrencies that could not serve as a general-purpose ledger, as
they are less important for biomedical informatics applications. This
way, the results of the systematic comparison could be utilized in Platform selection
healthcare or clinical application areas such as population health, To select the platforms names from the candidate list, we first re-
biomedical and health services research, and healthcare administra- moved all the duplicated blockchain platforms. Next, we aimed at
tion. We utilized Google.com58 as our main search engine, and con- “popular” blockchain platforms, because blockchain is still an
ducted all searches in July 2017. No major blockchain technology emerging technology and the widely used platforms are in general
has emerged as of November 2018. more mature in terms of the technical development, community sup-
port, and long-term maintenance. Intuitively, we could have used
the Google Count (ie, the number of webpages returned by search-
ing the platform name, such as “Bitcoin,” using Google.com) to
Search rank the popularity of the platforms. However, we realized that,
We used the phrase blockchain platforms as the initial search term while certain platform names were specific to the blockchain field
in Google.com. Realizing that the returning results were mostly (eg, “Ethereum”), other platform names were more general (eg,
about either “discussion of multiple blockchain platforms” or “Dash”). Thus, using just the Google Count of platform names
“general introduction of blockchain” (instead of the platforms might unfairly bias the results in favor of more general names.
themselves), we manually reviewed the top 30 ranked webpages To mitigate the bias introduced by common names, our strategy
returned by Google.com, and identified webpages that discussed was to first determine whether a platform name was a dictionary
more than 1 blockchain platform. We then collected all the block- word or not, using the following 2 online dictionary websites:
466 Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5
Figure 3. Another technique to reduce the need for each user to keep the full history of transactions is to use lightweight nodes together with a Merkle tree. For a
user who only wants to use coins but does not want to “mine” new blocks, the full transaction history (more than 150 GB as of January 2018) is too large, espe-
cially for smartphones. Therefore, a user can adopt lightweight nodes1 so that only the Merkle Branch1 that links the transactions that the user would like to verify
is used. An example of the Merkle Branch for transaction T12 stored on a blockchain lightweight node (eg, on a mobile device), in contrast to the data storage of a
full node (eg, on a personal computer), is shown in this figure. With the use of the Merkle tree, a lightweight node only stores data relevant to specific transactions
(eg, T12) to save space.1 For example, in addition to T12 itself, this lightweight node only needs to store related hashes (ie, Hash of T11, Hash of T13–14, and Hash of
T15–18), instead of storing the full Merkle tree, to make sure T12 is linked to block B1. That is, one can first compute the Hash of T12 using T12, and then compute the
Hash of T11–12 using the Hash of T11 and the Hash of T12. Eventually, one can compute the value of the Merkle Root (Hash of T11–18), and compare it with the one
stored in B1, to make sure T12 has been verified in B1. This way, a lot of required storage space for those lightweight nodes is saved, making applications such as
wallet apps on mobile devices feasible. This verifying process is also known as Simplified Payment Verification.1,59 As a result, users/nodes can be divided into 2
groups: full nodes (the ones storing the whole transaction history and performing mining) and lightweight nodes (ie, the nodes using Simplified Payment Verifi-
cation just for transactions, without mining), thus reducing the storage space for lightweight nodes and improving the scalability of a blockchain network.
(a)
General G4 Messengers M4
Messengers M1 General G1 When to Attack ?
Attack Attack
Enemy
Messengers M2 General G2 General G5
City Messengers M5
1pm
Messengers M3 Messengers M5
Block B1 Broadcast
7pm Messengers M6
Broadcast to Blockchain
PoW
Messengers M4
General G6
When-to-Attack is 7pm, PoW is Completed
General G4
Figure 5. The Byzantine Generals’ Problem refers to a distributed set of generals who need to reach a consensus/agreement on the timing of a simultaneous at-
tack by multiple divisions of an army. (A) A simplified example64 of the relaxed version of the Byzantine Generals’ Problem, showing the difficulty generals have
in agreeing on the proper time for an attack. There are several divisions of a Byzantine army camping outside an enemy city, and each division has its own com-
manding general who would like to, with other generals, reach consensus on the time to attack the city. That is, each general could make a decision about when
to attack the city, but to be successful the majority of generals have to come up with an agreement about the attack time. However, the generals can only commu-
nicate with each other via messengers, and such communication form is nonsynchronized (eg, if 2 generals announce 2 different preferred times within a very
close time frame, some generals may receive one time and other generals may receive another time). In this scenario, it is very difficult for the majority of generals
to find a consensus time and execute a successful attack. (B) A Proof-of-Work (PoW) solution to the relaxed version of the Byzantine Generals’ Problem. To deal
with Byzantine Generals’ Problem, many blockchain platforms have created consensus protocols to resolve disagreements within the chain. For example, PoW,
the consensus protocol of the Bitcoin Blockchain, can find a solution to the relaxed version of the Byzantine Generals’ Problem, as described by the author Satoshi
Nakamoto62 and proved by Miller and LaViola.65 The idea is for each general to first decide an attacking time (eg, at T0 in this example) and start to do PoW (eg, at
T1 to find a solution to a difficult-to-compute yet easy-to-verify problem2,66). Once the PoW is completed (eg, general G3 finds the solution at T2), the winning gen-
eral (G3) asks the messengers (M3) to broadcast the block containing G3’s proposed attack time T (1 PM in this example) to the blockchain. Since the verification of
PoW is relatively simple (ie, fast), other generals can verify the PoW easily. They pause their work because they would only be allowed to add their time after the
one proposed by G3. After confirming the PoW is valid, every other general agrees with G3 that the attack will be at 1 PM. (C) The process to reach consensus
among generals. After the first block (B1) with the time 1 PM is added to the blockchain, all generals restart PoW based on the hash of B1 to find the second block
(B2). One important protocol is that all generals will do PoW based on the longest chain, which ensures the consensus. That is, suppose general G4 also completed
the PoW to propose another attack time (7 PM) in block B1’: since another general (G5) has already created a block B2 to support 1 PM, the next general (G6) will only
work on the longest chain to support 1 PM instead of 7 PM, thus the consensus attack time would eventually be 1 PM. Finally, after the blockchain is long enough, ev-
ery general will be confident that the consensus attack time (1 PM) has been agreed by the majority of generals. This is because many generals have been working
on the longest chain, thus the probability of a successful consensus of attack time is now high enough to solve the distributed agreement problem.64
468 Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5
Identification
Records Identified through Database Searching Additional Records Identified through Other Sources
(n = 54) (n = 0)
Figure 6. The adjusted PRISMA flow diagram. We only included 3 phases (ie, identification, screening, and included), because the eligibility criteria were inte-
grated into the search strategy (ie, the PRISMA eligibility phase is integrated into the identification phase).
and Mastek.67 We collected the 54 blockchain platform names men- inspection.2,71–74 To improve this, Zcash uses a zero-knowledge proof
tioned in these 4 webpages into the candidate list. There were 35 plat- algorithm known as zk-SNARK, to ensure that the sender, recipient,
forms after removal of duplicates. We ranked the 35 blockchain and amount of a transaction remain private even on a publicly avail-
platforms using our “popularity” score, and manually selected 10 top able blockchain network, and thus improves the privacy or anonymity
ones. The process is shown in Figure 6, while the resulting 10 plat- of the transactions, while verifying the transactions privately to avoid
forms are described in Table 2. the double spending problem. This level of privacy or anonymity is
also highly desirable in healthcare applications. Also, Zcash addresses
Selected platform characteristics the mining centralization issue (Supplementary Appendix S3).75,76
In this subsection, we discuss the details of the 10 blockchain plat- However, as many health-related applications may be run on
forms selected for our systematic review, following the order of the permissioned networks, platforms like Zcash that use PoW are less at-
popularity score shown in Table 2. tractive than others that use different protocols.
Bitcoin Litecoin
Bitcoin, the first well-known and widely used distributed cryptocur- Litecoin is a decentralized global payment network.77 The major
rency, operates a peer-to-peer network without central authority or change of Litecoin, compared with Bitcoin, is that Litecoin has a
banks, and introduced the blockchain technology and platform to faster transaction speed (4 times quicker) at the expense of 4 times
the world.68 The management of transactions and the issuance of smaller storage space and reduced security.77 Also, Litecoin adopts
coins are carried out collectively by the blockchain network.68 Bit- the “Scrypt” hash algorithm77 for the PoW to mitigate the mining
coin uses PoW as its consensus protocol to verify transactions, and centralization issue (Supplementary Appendix S3). Speed could
thus consumes a lot of energy.1 Owing to the success of Bitcoin, become important in healthcare applications in which immediate
many other alternative cryptocurrencies and consensus protocols decisions are needed, but, so far, we have not seen examples of
were proposed and developed, including all other 9 platforms blockchain-based applications in health sciences in which this was a
reviewed in this study. critical factor. For example, we have not encountered situations in
which a healthcare blockchain needed to accommodate as many
Ethereum transactions per minute as credit cards or major retailers’ websites do.
Ethereum is a platform that lets anyone build and use smart-
contract-based decentralized applications that run on blockchain Dash
technology.69 Ethereum focuses on the capability of automatic digi- Dash (or Digital Cash) is a privacy-centric digital currency with in-
tal asset management, and, to do so, it supports smart contracts or stant transactions.78 It is based on the Bitcoin software, and adds an
properties (Supplementary Appendix S1), making the creation of the additional “Masternode” network tier on top of the Bitcoin Block-
asset managing programs easier than when using the scripting lan- chain network.79 The Masternode network is composed of nodes
guage in the Bitcoin Blockchain.25 Ethereum also adapts the PoW that are willing to put “collateral,” such as 1000 DASH coins, to
consensus protocol.25 serve as the full nodes to validate the transactions. The Masternode
offers additional privacy or anonymity to the users via “Darksend”
Zcash (based on the “CoinJoin” technology,79 a process of merging multi-
Zcash is a decentralized and open-source cryptocurrency that offers ple transactions together so that the attacker cannot link the transac-
privacy and anonymity of transactions.70 A challenge of the Bitcoin tions using histories).78,79 Also, the relatively few collateral nodes in
Blockchain is that, although the senders and recipients are repre- the Masternode network can speed-up the validation process, pro-
sented with a hashed address, given enough transaction data, the viding an instant transaction mechanism known as “InstantX.”79
transactions may still be linked or traced through careful analysis and The additional privacy for the users is attractive to healthcare
Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5 469
Basic Information 1 Official Website URL for the official website of the platform.
2 Software Website Online repository system that keeps track of the source code of the platform.
3 Explorer Website Special type of online website, “explorer,” that keeps track of all the transactions
for the platform. Note that, multiple explorers may exist for the platform which
also serves as a cryptocurrency. In this case, we only list the “official” or the
representative ones. Also, the living public websites do not exist for the non-
cryptocurrency platforms, however, the “explorer” code may be available; in
this case, we list the website of their “explorer” code instead.
4 Main Reference Main official white papers or the other types of articles discussing the platform.
5 Real-World Application Examples of the institutions or companies currently using the platform.
Note that we included cryptocurrency-related data items considering their future plausible use in healthcare/medicine applications.
Blockchain Platform Dictionary Word Google Count with Blockchain Google Count Without Blockchain Popularity Score
applications but the centralization introduced by Masternode is a PoW and eventually switch to Proof of Stake (PoS) (see Supplemen-
downside. tary Appendix S4). While more appropriate for health-related appli-
cations than PoW, PoS may also not be necessary, particularly when
operating in permissioned networks, as the threat of “fake” blocks
Peercoin is less severe. However, for public networks, Peercoin may offer a
Peercoin was derived from Bitcoin to reduce the energy required for good compromise by supporting PoS.
the coin mining process.83 That is, Bitcoin’s PoW algorithm depends
on energy consumption1,2 that, in the long run, will result in lower
motivation for miners to keep building blocks unless transactions Ripple
fees rise to high enough levels to sustain the high energy consump- Ripple is a low-latency blockchain network that atomically settles
tion.83 To avoid this situation, Peercoin proposed to initially adopt and records transactions on a secure distributed database, the Ripple
470 Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5
Network Permission • Permission-less network: A public blockchain network configuration designed to allow public participation
(eg, some applications that rely on patient-managed data).92
• Permissioned network: A private blockchain network configuration that includes only authorized partici-
pants (eg, networks that exchange information among hospitals).31,43
Consensus Protocol • Proof of Work: A compute-intensive protocol with proof of security; suitable for permission-less blockchain
networks but can also be used in permissioned blockchain networks to increase security. The Bitcoin block-
chain uses this protocol: unfortunately, many people mistakenly believe that all blockchain networks need
to use this typically high-energy consumption protocol, which is not true.1,66
• Proof of Stake: A low-energy consumption protocol that is suitable for healthcare applications operating on
permission-less or permissioned blockchain networks.93–95
Consensus Ledger.84 Ripple applies the Ripple Consensus Protocol the Sybil Attack.85,86 The blocks are only validated by the relatively
Algorithm, an alternative algorithm to the high-latency Bitcoin few “Chosen Validators” to enable low-latency transactions. While
Blockchain PoW, for handling the Byzantine Generals’ Problem and reaching consensus, the current distributed ledger is “closed” and
Table 5. Blockchain technology
Blockchain Main Improvement Network Consensus Protocol Special Hardware Requirement Smart Contracts Support
Platform over Bitcoin Permission
Blockchain Symbol Mining for Anonymous Rapid Payment Coin Limit Coin Value (in U.S. Dollars, Average Transaction
Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5
Because MultiChain and Hyperledger are not public cryptocurrencies, they do not have most of the technical features listed; however, for completeness we still include their transaction speed (ie, the Average Transactions
per Second column).
471
Blockchain Scripting Language Open Source? Main Implementation Languages Software License
Platform
considered the most recent one. Also, Ripple coins are “pre-mined” versity can provide consensus and mining securely on the private
and cannot be created during the consensus process.87 Again, if we blockchain network without the need for the computationally inten-
consider that most healthcare applications will use permissioned sive PoW algorithm.31 However, MultiChain does not provide addi-
networks, the advantages of using alternative consensus protocols tional privacy for users as do some other platforms.
are diminished.
Hyperledger
Monero Hyperledger is an open-source collaborative effort created to ad-
Monero is a secure, private, and untraceable cryptocurrency.88 vance permissioned or private, cross-industry blockchain technolo-
Monero offers privacy or anonymity to its users by using the “Ring gies.91 As the use of blockchain must respond to different needs,
Confidential Transactions” (a ring signature algorithm based on Hyperledger provides an infrastructure to include a range of mod-
CryptoNote89 that generates a group signature and in which the ac- ules, such as various smart contract engines.43 Specifically, Hyper-
tual signer cannot be identified) and the “Stealth Address” (an one- ledger includes differentiated blockchain frameworks and tools.43
time address for each transaction) technologies, to obfuscate the ori- Each framework supports different types of consensus protocols.43
gins, destinations, and amounts of all transactions.88 Therefore, the Hyperledger does not support PoW43 and the additional privacy
ability to “hide the destination and origin of transactions”90 is an protection is yet to be included. It should also be noted that Hyper-
important feature of Monero. This platform might be considered in ledger has global collaborations with various companies.
applications in which the privacy or anonymity of patient or partici-
pant users is at stake, although it only supports the high energy con- As we can see from the brief summaries, no platform is perfect,
sumption PoW protocol. and in the future the best features may be adopted by the platforms
that remain in the market. It is unlikely that more than 3 or 4 plat-
forms will become very relevant to healthcare. In terms of platforms
MultiChain
likely to continue to be used for healthcare applications, Ethereum,
MultiChain is a blockchain platform to create and deploy permis-
Hyperledger and MultiChain are at the top of the list because they
sioned or private blockchain networks.31 As a fork of the Bitcoin
combine the most relevant features at the moment.
Blockchain, MultiChain focuses on providing features such as inte-
grating user permission management and improve the data ledger
functions.34 Also, MultiChain supports both Bitcoin Blockchain Results of platform comparison
PoW and “Mining Diversity,” a round-robin-based consensus proto- The features most relevant for healthcare applications are summa-
col.31 The basic idea of Mining Diversity is that, within a private rized in Table 3, and the full comparison results of the extraction
blockchain network, the participants are already “trusted” to some of the 21 data items (Table 1) from the 10 blockchain platforms
extent because they are identifiable entities.31 Therefore, Mining Di- (Table 2) are shown in Tables 4–7.
Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5 473
Limitations
A limitation of this study is that the blockchain technology is rela-
FUNDING
tively new and still emerging, so documentation is somewhat very
limited (eg, out of date or not available because of the fast and con- T-TK and LO-M were partly funded by the National Institutes of Health
tinuing development process), and the applications for healthcare or (OT3OD025462). HZR was supported by the UCSD STARS Program, and
the iDASH Summer Internship Program funded by the National Institutes of
medicine are mostly in early stages (ie, most are proposed systems
Health (T15LM11271). Research reported in this publication was supported
that have yet to be implemented). Therefore, our systematic compar-
by the National Human Genome Research Institute of the National Institutes
ison is restricted by the data and information we could gather from
of Health under Award Number K99/R00HG009680. The content is solely
publicly available resources for each platform. Additionally, we fo- the responsibility of the authors and does not necessarily represent the official
cused on the most popular platforms, and therefore we only views of the National Institutes of Health or of the Veterans Health Adminis-
reviewed the first 30 webpages returned from the initial Google.com tration (VHA).
search (ie, blockchain platforms). After deduplication, we selected
10 of 35 platforms. This selection process may have introduced bias,
because we used not only a popularity ranking, but also a manual
CONTRIBUTORS
screening process. Finally, we extracted 21 data items in 4 categories
(ie, basic information, blockchain technology, public cryptocur- T-TK and HZR mainly conducted the systematic review and drafted
rency, and application programming), which may cover only the the manuscript. LO-M was principal investigator of this study: she
most critical aspects in the selection of the blockchain platforms for provided the original idea, performed overall supervision of the study,
healthcare applications, while several other minor technical features resolved the disagreements in the systematic review process, provided
are yet to be included. Finally, we have not run real controlled cases critical editing, and made several additions to the manuscript.
to verify that the stated speed of transactions is similar to the one
stated in the websites.
SUPPLEMENTARY MATERIAL
CONCLUSION Supplementary material is available at Journal of the American
Medical Informatics Association online.
In this study, we identified healthcare applications of blockchain, as
well as the platforms that have been proposed or implemented by
the state-of-the-art healthcare blockchain studies. To understand
which blockchain platform may be more feasible for healthcare or ACKNOWLEDGMENTS
clinical applications, we conducted a systematic comparison of 21 The authors would like to thank Xiaoqian Jiang, PhD, for organizing the
characteristics for 10 popular blockchain platforms, to support iDASH (integrating Data for Analysis, Anonymization, and SHaring) Summer
health informatics researchers in the selection of the most suitable Internship Program, and Elisa Maldonado, PhD, for organizing the Summer
platform for their specific application. We discussed critical block- Training Academy for Research Success (STARS) Program at University of
California, San Diego, in 2017. The authors would also like to thank Jeremy
chain implementation features, introduced these platforms, and
Blackstone for his support of HZR during his UCSD STARS internship.
compared the technical features that are most relevant to healthcare.
Our results show that most platforms share similar features, but Conflict of interest statement. None declared.
474 Journal of the American Medical Informatics Association, 2019, Vol. 26, No. 5
REFERENCES 21. Linn LA, Koo MB. Blockchain for Health Data and Its Potential Use in
Health It and Health Care Related Research. ONC/NIST Use of Block-
1. Nakamoto S. Bitcoin: a peer-to-peer electronic cash system. https://bit- chain for Healthcare and Research Workshop. Gaithersburg, MD:
coin.org/bitcoin.pdf. Accessed July 1, 2017. ONC/NIST; 2016.
2. Kuo T-T, Kim H-E, Ohno-Machado L. Blockchain distributed ledger 22. Goldwater J. The Use of a Blockchain to Foster the Development of
technologies for biomedical and health care applications. J Am Med In- Patient-Reported Outcome Measures. ONC/NIST Use of Blockchain for
form Assoc 2017; 24 (6): 1211–20. Healthcare and Research Workshop. Gaithersburg, MD: ONC/NIST;
3. Mettler M. Blockchain technology in healthcare: the revolution starts 2016.
here. In: 2016 IEEE 18th International Conference on e-Health Net- 23. Topol EJ. Money back guarantees for non-reproducible results? BMJ
working, Applications and Services (Healthcom). Munich, Germany: 2016; 353: i2270.
IEEE; 2016: 1–3. 24. Brodersen C, Kalis B, Leong C, et al. Blockchain: Securing a New Health
4. Yli-Huumo J, Ko D, Choi S, Park S, Smolander K. Where is current re- Interoperability Experience. United States: Accenture LLP; 2016.
search on blockchain technology?—A systematic review. PLoS One 25. Buterin V. A next-generation smart contract and decentralized applica-
2016; 11 (10): e0163477. tion platform. https://github.com/ethereum/wiki/wiki/White-Paper.
42. Griggs KN, Ossipova O, Kohlios CP, Baccarini AN, Howson EA, Hayaj- 63. Purkayastha S. Eight blockchain platforms for rapid prototyping. Radio-
neh T. Healthcare blockchain system using smart contracts for secure au- Studio. http://radiostud.io/eight-blockchain-platforms-comparison/.
tomated remote patient monitoring. J Med Syst 2018; 42 (7): 130. Accessed July 1, 2017.
43. The Linux Foundation. Hyperledger architecture. Volume I: Introduction 64. Nakamoto S. Re: Bitcoin P2P e-cash paper. Satoshi Nakamoto Institute.
to hyperledger business blockchain design philosophy and consensus. http://satoshi.nakamotoinstitute.org/emails/cryptography/11/. Accessed
https://www.hyperledger.org/wp-content/uploads/2017/08/Hyperledger_ July 1, 2017.
Arch_WG_Paper_1_Consensus.pdf. Accessed November 5, 2017. 65. Miller A, LaViola JJ Jr. Anonymous byzantine consensus from moder-
44. Liang X, Zhao J, Shetty S, Liu J, Li D. Integrating blockchain for data ately hard puzzles: a model for bitcoin. 2014. https://nakamotoinsti-
sharing and collaboration in mobile healthcare applications. In: IEEE tute.org/static/docs/anonymous-byzantine-consensus.pdf. Accessed:
28th Annual International Symposium on Personal, Indoor, and Mobile July 1, 2017.
Radio Communications (PIMRC), 2017. Piscataway, NJ: Institute of 66. Kelsey J. Introduction to Blockchains. ONC/NIST Use of Blockchain in
Electrical and Electronics Engineers; 2017: 1–5. Healthcare and Research Workshop. Gaithersburg, MD: ONC/NIST;
45. Kovach A, Ronai G. MyMEDIS: a new medical data storage and access 2016.
system. 2018. https://mymedis.in/documents/MEDIS-White-Paper.pdf. 67. Jethwani KD. Four key blockchain platforms: their use cases in finan-
87. Piasecki P. A counter argument to the value proposition of Ripple’s XRP 115. Blockchain Luxembourg S.A. Block Explorer. 2017. https://blockchain.
token. https://www.coindesk.com/counterargument-value-proposition- info/. Accessed July 1, 2017.
ripples-xrp-token/. Accessed July 1, 2017. 116. Everex. Ethplorer. 2017. https://ethplorer.io/. Accessed July 1, 2017.
88. Monero. Monero private digital currency. https://getmonero.org/. 117. Bitfly GmbH. Zchain. 2017. https://explorer.zcha.in/. Accessed July 1,
Accessed July 1, 2017. 2017.
89. Saberhagen NV. CryptoNote v2.0. https://cryptonote.org/whitepaper. 118. BlockCypher, Inc. Litecoin explorer. https://live.blockcypher.com/ltc/.
pdf. Accessed July 1, 2017. Accessed July 1, 2017.
90. Noether S, Mackenzie A, Team MC. Ring confidential transactions. 119. The Abe Developers. Dash Blockchain Explorer. https://explorer.dash.
https://lab.getmonero.org/pubs/MRL-0005.pdf. Accessed July 1, 2017. org/chain/Dash. Accessed July 1, 2017.
91. The Linux Foundation. Hyperledger. https://www.hyperledger.org/. 120. CryptoID.info. Peercoin blockchain explorer. https://chainz.cryptoid.
Accessed July 1, 2017. info/ppc/. Accessed July 1, 2017.
92. The Ethereum Community. Connecting to the network. http://ethdocs. 121. Ripple Labs, Inc. Ripple XRP Charts - Transactions. https://xrpcharts.
org/en/latest/network/connecting-to-the-network.html-public-private- ripple.com/#/transactions. Accessed July 1, 2017.
and-consortium-blockchains. Accessed July 1, 2017. 122. Moneroblocks.info. Monero Blocks. 2017. https://moneroblocks.info/.
141. The Ethereum Community. Frequently Asked Questions. http://ethdocs. 166. The Peercoin Developers and the Bitcoin Developers. Peercoin FAQ.
org/en/latest/frequently-asked-questions/frequently-asked-questions.html? https://github.com/peercoin/peercoin/wiki/FAQ. Accessed July 31, 2017.
highlight=privacy-how-do-i-get-a-list-of-transactions-into-out-of-an-ad- 167. Buntinx JP. Top 5 cryptocurrencies that can’t be mined. https://themer-
dress. Accessed December 1, 2017. kle.com/top-5-cryptocurrencies-that-cant-be-mined/. Accessed July 1,
142. Zerocoin Electric Coin Company. Zcash. 2017. https://z.cash/. Accessed 2017.
July 1, 2017. 168. Levy A. Bitcoin rival Ripple is suddenly sitting on billions of dollars
143. Wilcox Z, Grigg J. Why Equihash? https://z.cash/blog/why-equihash. worth of cryptocurrency. https://www.cnbc.com/2017/05/26/bitcoin-ri-
html. Accessed July 1, 2017. val-ripple-is-sitting-on-many-billions-of-dollars-of-xrp.html. Accessed
144. Wikipedia. Litecoin. https://en.wikipedia.org/wiki/Litecoin. Accessed July 1, 2017.
July 1, 2017. 169. Moneroinfo.org. MoneroInfo. https://moneroinfo.org/eng-about/.
145. Balazs Kiraly. Dash Mining. Dash Core Group, Inc. https://dashpay. Accessed July 1, 2017.
atlassian.net/wiki/spaces/DOC/pages/1146945/Mining. Accessed July 1, 170. BitInfoChart. Bitcoin Transactions Historical Chart. https://bitinfo-
2017. charts.com/comparison/bitcoin-transactions.html#3m. Accessed Decem-
146. The Dash Network. Mining of Dash. https://www.dash.org/mining/. ber 5, 2017.
190. The Ethereum Community. Fast, light, robust Ethereum implementa- 193. The Peercoin Developers and the Bitcoin Developers. Peercoin Official
tion. https://github.com/paritytech/parity. Accessed July 1, 2017. Development Tree. https://github.com/peercoin/peercoin. Accessed July
191. The Bitcoin Core Developers, the Bitcoin Developers, and the Litecoin 1, 2017.
Core Developers. Litecoin source tree. https://github.com/litecoin-proj- 194. The Bitcoin Core Developers and the Bitcoin Developers. bitcoin/COPY-
ect/litecoin. Accessed July 1, 2017. ING. 2017. https://github.com/bitcoin/bitcoin/blob/master/COPYING.
192. The Bitcoin Core Developers and the Dash Core Developers. Dash Accessed July 1, 2017.
Core staging tree. https://github.com/dashpay/dash. Accessed July 1, 195. The Monero Project. Monero: the secure, private, untraceable cryptocur-
2017. rency. https://github.com/monero-project/monero. Accessed July 1, 2017.