Mobile Phone–Based Use of the Photoplethysmography Technique to Detect Atrial Fibrillation in Primary Care: Diagnostic Accuracy Study of the FibriCheck App
Bibliographic record
Abstract
BACKGROUND: Mobile phone apps using photoplethysmography (PPG) technology through their built-in camera are becoming an attractive alternative for atrial fibrillation (AF) screening because of their low cost, convenience, and broad accessibility. However, some important questions concerning their diagnostic accuracy remain to be answered. OBJECTIVE: This study tested the diagnostic accuracy of the FibriCheck AF algorithm for the detection of AF on the basis of mobile phone PPG and single-lead electrocardiography (ECG) signals. METHODS: A convenience sample of patients aged 65 years and above, with or without a known history of AF, was recruited from 17 primary care facilities. Patients with an active pacemaker rhythm were excluded. A PPG signal was obtained with the rear camera of an iPhone 5S. Simultaneously, a single‑lead ECG was registered using a dermal patch with a wireless connection to the same mobile phone. PPG and single-lead ECG signals were analyzed using the FibriCheck AF algorithm. At the same time, a 12‑lead ECG was obtained and interpreted offline by independent cardiologists to determine the presence of AF. RESULTS: A total of 45.7% (102/223) subjects were having AF. PPG signal quality was sufficient for analysis in 93% and single‑lead ECG quality was sufficient in 94% of the participants. After removing insufficient quality measurements, the sensitivity and specificity were 96% (95% CI 89%-99%) and 97% (95% CI 91%-99%) for the PPG signal versus 95% (95% CI 88%-98%) and 97% (95% CI 91%-99%) for the single‑lead ECG, respectively. False-positive results were mainly because of premature ectopic beats. PPG and single‑lead ECG techniques yielded adequate signal quality in 196 subjects and a similar diagnosis in 98.0% (192/196) subjects. CONCLUSIONS: The FibriCheck AF algorithm can accurately detect AF on the basis of mobile phone PPG and single-lead ECG signals in a primary care convenience sample.
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.004 | 0.022 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| 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".