Distributed Ledger Infrastructure to Verify Adverse Event Reporting (DeLIVER): Proposal for a Proof-of-Concept Study
Bibliographic record
Abstract
BACKGROUND: Adverse drug event reporting is critical for ensuring patient safety; however, numbers of reports have been declining. There is a need for a more user-friendly reporting system and for a means of verifying reports that have been filed. OBJECTIVE: This project has 2 main objectives: (1) to identify the perceived benefits and barriers in the current reporting of adverse events by patients and health care providers and (2) to develop a distributed ledger infrastructure and user interface to collect and collate adverse event reports to create a comprehensive and interoperable database. METHODS: A review of the literature will be conducted to identify the strengths and limitations of the current UK adverse event reporting system (the Yellow Card System). If insufficient information is found in this review, a survey will be created to collect data from system users. The results of these investigations will be incorporated into the development of a mobile and web app for adverse event reporting. A digital infrastructure will be built using distributed ledger technology to provide a means of linking reports with existing pharmaceutical tracking systems. RESULTS: The key outputs of this project will be the development of a digital infrastructure, including a backend distributed ledger system and an app-based user interface. CONCLUSIONS: This infrastructure is expected to improve the accuracy and efficiency of adverse event reporting systems by enabling the monitoring of specific medicines or medical devices over their life course while protecting patients' personal health data. INTERNATIONAL REGISTERED REPORT IDENTIFIER (IRRID): PRR1-10.2196/28616.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.040 | 0.026 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.005 | 0.006 |
| Open science | 0.006 | 0.006 |
| Research integrity | 0.005 | 0.004 |
| Insufficient payload (model declined to judge) | 0.017 | 0.006 |
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 itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".