Apache Spark for Analysis of Electronic Health Records: A Case Study of Diabetes Management
Bibliographic record
Abstract
Electronic Health Records (EHRs), heralded for their potential to revolutionize healthcare outcomes, function as repositories for invaluable data.This study offers a compelling exploration into the integration of Apache Spark for EHR analysis, with a specific focus on elevating diabetes care.Leveraging Apache Spark alongside a robust machine learning framework, we automated EHR analysis by processing extensive datasets, conducting thorough preprocessing, and extracting pertinent features.The inherent distributed processing capabilities of Apache Spark facilitated concurrent training and evaluation of machine learning models.Its in-memory data processing markedly reduced reliance on disk input/output, thereby enhancing performance and scalability.This methodology enabled swift and thorough EHR data analysis, with ensuing insights effectively visualized and reported.This empowered healthcare professionals to make informed decisions.The iterative nature of the process allowed for continuous refinement, enhancing healthcare outcomes based on insightful data.The synergy between Apache Spark and machine learning techniques in EHR analysis emerged as a potent and efficient strategy.This approach exhibits promise in significantly advancing healthcare outcomes by enabling effective prediction and management of diabetes, ultimately contributing to superior patient care and reducing healthcare costs.The findings underscore the transformative potential of integrating contemporary data analysis tools within the healthcare sector.
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.008 | 0.022 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
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".