Blockchain Implementation in Health Care: Protocol for a Systematic Review
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
BACKGROUND: A blockchain is a digitized, decentralized, distributed public ledger that acts as a shared and synchronized database that records cryptocurrency transactions. Despite the shift toward digital platforms enabled by electronic medical records, demonstrating a will to reform the health care sector, health systems face issues including security, interoperability, data fragmentation, timely access to patient data, and silos. The application of health care blockchains could enable data interoperability, enhancement of precision medicine, and reduction in prescription frauds through implementing novel methods in access and patient consent. OBJECTIVE: To summarize the evidence on the strategies and frameworks utilized to implement blockchains for patient data in health care to ensure privacy and improve interoperability and scalability. It is anticipated this review will assist in the development of recommendations that will assist key stakeholders in health care blockchain implementation, and we predict that the evidence generated will challenge the health care status quo, moving away from more traditional approaches and facilitating decision making of patients, health care providers, and researchers. METHODS: A systematic search of MEDLINE/PubMed, Embase, Scopus, ProQuest Technology Collection and Engineering Index will be conducted. Two experienced independent reviewers will conduct titles and abstract screening followed by full-text reading to determine study eligibility. Data will then be extracted onto data extraction forms before using the Cochrane Collaboration Risk of Bias Tool to appraise the quality of included randomized studies and the Risk of Bias in nonrandomized studies of Interventions to assess the quality of nonrandomized studies. Data will then be analyzed and synthesized. RESULTS: Database searches will be initiated in September 2018. We expect to complete the review in January 2019. CONCLUSIONS: This review will summarize the strategies and frameworks used to implement blockchains in health care to increase data privacy, interoperability, and scalability. This review will also help clarify if the strategies and frameworks required for the operationalization of blockchains in health care ensure the privacy of patient data while enabling efficiency, interoperability, and scalability. INTERNATIONAL REGISTERED REPORT IDENTIFIER (IRRID): PRR1-10.2196/10994.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.003 | 0.000 |
| Bibliometrics | 0.001 | 0.003 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.004 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it