Atrial Fibrillation History Feature
Apple Inc. • Cardiovascular • 06/03/2022
Device Purpose
The Atrial Fibrillation History Feature is an over-the-counter software application designed for individuals with a pre-existing AFib diagnosis to retrospectively track their AFib burden using photoplethysmography data from an Apple Watch. It employs a convolutional neural network to analyze pulse rhythms, providing users with estimated AFib burden percentages and lifestyle data visualizations to enhance their understanding and management of their condition.
Summary
The Atrial Fibrillation History Feature is an over-the-counter (OTC) software-only mobile medical application designed for users aged 22 and older who have a prior diagnosis of atrial fibrillation (AFib). It operates in conjunction with compatible Apple Watch models (Series 4, 5, SE) and the Health app on an iPhone, utilizing the watch's photoplethysmography (PPG) sensor, which employs green LED lights and light-sensitive photodiodes, to detect changes in blood flow at the wrist and thereby measure beat-to-beat intervals from pulse rate data. The feature opportunistically analyzes this data to identify episodes of irregular heart rhythms suggestive of AFib, subsequently providing users with a retrospective estimate of their AFib burden, defined as the amount of time spent in AFib during periods of Apple Watch wear. The core of the AFib History Feature is its rhythm classification algorithm, which is based on a convolutional neural network (machine learning) trained on an extensive dataset comprising over 2500 subjects and more than 3 million pulse rate recordings, and has been specifically optimized for individuals with a pre-existing AFib diagnosis. In addition to tracking AFib burden over time—presenting estimates weekly, by day of the week over the past 42 days, and by time of day in 4-hour segments over the past 42 days—the feature incorporates lifestyle data visualizations to help users understand potential correlations between their habits and AFib occurrences. Clinical validation, involving 413 participants (with 280 contributing to the primary endpoint analysis), demonstrated the feature's accuracy in estimating weekly AFib burden when compared to a reference electrocardiogram (ECG) patch, yielding Bland-Altman limits of agreement of -11.4% and 12.8%, an average difference of 0.67%, and showing that 92.9% of subjects had paired weekly AFib burden differences within ±5%. The classification algorithm itself achieved 92.6% sensitivity and 98.8% specificity in this clinical validation study.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the opportunistic analysis of pulse rate data account for periods when the Apple Watch is not worn or when data quality is insufficient for analysis, and how might this impact the accuracy of the retrospective AFib burden estimate?; What specific lifestyle factors are tracked and visualized alongside AFib burden, and what is the evidence supporting their clinical relevance in influencing AFib burden in the target population?; Given the algorithm's optimization for users with a prior AFib diagnosis, what is its performance (sensitivity and specificity) in differentiating AFib from other common arrhythmias or ectopic beats in this specific population?; How does the feature's 'Day of Week' and 'Time of Day' AFib burden estimation account for variability in watch wear time across different days or times, and how is this communicated to the user?; What were the criteria for including/excluding subjects from the primary endpoint analysis (280 out of 413 enrolled) in the clinical validation study, and how might this selection have influenced the reported Bland-Altman limits of agreement?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class C (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM, SaaSBOM, HBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Not detected in AI-generated device summary: SBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly