2021
DOI: 10.1007/s00521-020-05519-w
|View full text |Cite
|
Sign up to set email alerts
|

Blockchain for healthcare data management: opportunities, challenges, and future recommendations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
215
0
1

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
3
1

Relationship

2
6

Authors

Journals

citations
Cited by 311 publications
(217 citation statements)
references
References 53 publications
1
215
0
1
Order By: Relevance
“…In academia, discussions on the application of blockchain technology to medical information systems have continued for several years, and most scholars have given positive answers and raised challenges [66], [67], [68], [69]. Asaph Azaria and his colleagues proposed MedRec [40] in 2016, a decentralized record management system using the blockchain technology.…”
Section: Comparison To Other Related Workmentioning
confidence: 99%
“…In academia, discussions on the application of blockchain technology to medical information systems have continued for several years, and most scholars have given positive answers and raised challenges [66], [67], [68], [69]. Asaph Azaria and his colleagues proposed MedRec [40] in 2016, a decentralized record management system using the blockchain technology.…”
Section: Comparison To Other Related Workmentioning
confidence: 99%
“…• We implement functional smart contracts of hospitalregulated healthcare systems, deploy the smart contracts, and perform extensive experiments and tests to analyze the functionality of our algorithms. The smart contract code along with testing scripts is publicly made available 1 .…”
Section: B Approach and Contributionsmentioning
confidence: 99%
“…2) Requesting EMR document: The doctor generates a request token and gets its keccak256 hash. The hash and the range of verifiers [1,4] are used in calling requestExternalEMR from HSC A . The network processes the request to validate the doctor parameters, resulting in constructing the desired range of verifiers [2,4] because the minimum number of acceptable verifiers by the network is 2.…”
Section: A Qualitative Functionality Evaluationmentioning
confidence: 99%
See 1 more Smart Citation
“…1) Requesting EMR document: The doctor generates a request token and gets its keccak256 hash. The hash and the range of verifiers [1,4] are used in calling requestExternalEMR from HSC A . The network processes the request to validate the doctor parameters, resulting in constructing the desired range of verifiers [2,4] because the minimum number of acceptable verifiers by the network is 2.…”
Section: A Qualitative Functionality Evaluationmentioning
confidence: 99%