Use of a Clinical Electrocardiographic Database to Enhance Atrial Fibrillation/Atrial Flutter Identification Algorithms Based on Administrative Data
Bibliographic record
Abstract
Background Administrative data have limited sensitivity for case finding of atrial fibrillation/atrial flutter (AF/AFL). Linkage with clinical repositories of interpreted ECGs may enhance diagnostic yield of AF/AFL. Methods and Results We retrieved 369 ECGs from the institutional Marquette Universal System for Electrocardiography (MUSE) repository as validation samples, with rhythm coded as AF (n=49), AFL (n=50), or other competing rhythm diagnoses (n=270). With blinded, duplicate review of ECGs as the reference comparison, we compared multiple MUSE coding definitions for identifying AF/AFL. We tested the agreement between MUSE diagnosis and reference comparison, and calculated the sensitivity and specificity. Using a data set linking clinical registries, administrative data, and the MUSE repository (n=11 662), we assessed the incremental diagnostic yield of AF/AFL by incorporating ECG data to administrative data-based algorithms. The agreement between MUSE diagnosis and reference comparison depended on the coding definitions applied, with the Cohen κ ranging from 0.57 to 0.75. Sensitivity ranged from 60.6% to 79.1%, and specificity ranged from 93.2% to 98.0%. A coding definition with AF/AFL appearing in the first 3 ECG statements had the highest sensitivity (79.1%), with little loss of specificity (94.5%). Compared with the algorithms with only administrative data, incorporating ECG data increased the diagnostic yield of preexisting AF/AFL by 14.5% and incident AF/AFL by 7.5% to 16.1%. Conclusions Routine ECG interpretation using MUSE coding is highly specific and moderately sensitive for AF/AFL detection. Inclusion of MUSE ECG data in AF/AFL case identification algorithms can identify cases missed using administrative data-based algorithms alone.
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.086 | 0.255 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.011 | 0.009 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".