Will Apple devices' passive atrial fibrillation detection prevent strokes? Estimating the proportion of high-risk actionable patients with real-world user data.

OBJECTIVE: Utilizing integrated electronic health record (EHR) and consumer-grade wearable device data, we sought to provide real-world estimates for the proportion of wearers that would likely benefit from anticoagulation if an atrial fibrillation (AFib) diagnosis was made based on wearable device data. MATERIALS AND METHODS: This study utilized EHR and Apple Watch data from an observational cohort of 1802 patients at Cedars-Sinai Medical Center who linked devices to the EHR between April 25, 2015 and November 16, 2018. Using these data, we estimated the number of high-risk patients who would be actionable for anticoagulation based on (1) medical history, (2) Apple Watch wear patterns, and (3) AFib risk, as determined by an existing validated model. RESULTS: Based on the characteristics of this cohort, a mean of 0.25% (n = 4.58, 95% CI, 2.0-8.0) of patients would be candidates for new anticoagulation based on AFib identified by their Apple Watch. Using EHR data alone, we find that only approximately 36% of the 1802 patients (n = 665.93, 95% CI, 626.0-706.0) would have anticoagulation recommended even after a new AFib diagnosis. DISCUSSION AND CONCLUSION: These data suggest that there is limited benefit to detect and treat AFib with anticoagulation among this cohort, but that accessing clinical and demographic data from the EHR could help target devices to the patients with the highest potential for benefit. Future research may analyze this relationship at other sites and among other wearable users, including among those who have not linked devices to their EHR.

Patient-Initiated Data: Our Experience with Enabling Patients to Initiate Incorporation of Heart Rate Data into the Electronic Health Record.

BACKGROUND: Provider organizations increasingly allow incorporation of patient-generated data into electronic health records (EHRs). In 2015, we began allowing patients to upload data to our EHR without physician orders, which we henceforth call patient-initiated data (PAIDA). Syncing wearable heart rate monitors to our EHR allows for uploading of thousands of heart rates per patient per week, including many abnormally low and high rates. Physician informaticists expressed concern that physicians and their patients might be unaware of abnormal heart rates, including those caused by treatable pathology. OBJECTIVE: This study aimed to develop a protocol to address millions of unreviewed heart rates. METHODS: As a quality improvement initiative, we assembled a physician informaticist team to meet monthly for review of abnormally low and high heart rates. By incorporating other data already present in the EHR, lessons learned from reviewing records over time, and from contacting physicians, we iteratively refined our protocol. RESULTS: We developed (1) a heart rate visualization dashboard to identify concerning heart rates; (2) experience regarding which combinations of heart rates and EHR data were most clinically worrisome, as opposed to representing artifact; (3) a protocol whereby only concerning heart rates would trigger a cardiologist review revealing protected health information; and (4) a generalizable framework for addressing other PAIDA. CONCLUSION: We expect most PAIDA to eventually require systematic integration and oversight. Our governance framework can help guide future efforts, especially for cases with large amounts of data and where abnormal values may represent concerning but treatable pathology.