Contribute Try STAT+ Today

The Apple Watch 4 can now do something that was once available mainly in your doctor’s office or a hospital: take an electrocardiogram. This recording of your heart’s rhythm can detect rapid or skipped heartbeats. The watch can also check your heart’s rhythm in the background and notify you if an irregular rhythm appears to be atrial fibrillation.

That’s a useful task. A heart in atrial fibrillation beats faster than normal, and the upper and lower chambers don’t work together. Atrial fibrillation can go unnoticed. It can also cause fatigue, dizziness, heart palpitations, or chest pain. Noticed or not, it can increase the risk of having a stroke.

As a physician, I’m excited about this new frontier in digital health. But I’m also cautious about its implications. Diagnostic tests like this one are rarely perfect. They usually generate false positives: incorrectly diagnosing a condition in people who do not have it.


According to data that Apple submitted in its petition asking the Food and Drug Administration to give clearance to the heart monitoring app, the app accurately detects atrial fibrillation 99 percent of the time it gets a good reading.

That sounds amazing. But it leaves out an important little something: the likelihood of having atrial fibrillation is low among younger individuals and increases with age. I did some calculations to answer the question, “If my watch tells me I have atrial fibrillation, what are the odds it is correct?” The answer depends on the watch wearer’s age.


I first needed to know the baseline risk of having atrial fibrillation. According to the AnTicoagulation and Risk Factors in Atrial Fibrillation (ATRIA) Study, which included nearly 1.9 million Americans, the percentage increases with age: 0.1 percent of those younger than age 55 have atrial fibrillation, rising to 9.1 percent among those over age 85.

Next I needed to know the sensitivity (the probability of having atrial fibrillation if the watch detects it) and specificity (the probability of not having atrial fibrillation if the watch does not detect it) of the Apple Watch app. Apple helpfully supplies those numbers — 98 percent sensitivity and 99.6 specificity — in its user’s guide.

I applied Bayesian statistics to this information. This branch of statistics uses prior information, such as disease prevalence, to interpret the likelihood of an outcome, in this case having atrial fibrillation. The result of the calculation is the positive predictive value: the probability of having atrial fibrillation when it is detected by the watch.

In people younger than 55, Apple Watch’s positive predictive value is just 19.6 percent. That means in this group — which constitutes more than 90 percent of users of wearable devices like the Apple Watch — the app incorrectly diagnoses atrial fibrillation 79.4 percent of the time. (You can try the calculation yourself using this Bayesian calculator: enter 0.001 for prevalence, 0.98 for sensitivity, and 0.996 for specificity).

The electrocardiogram app becomes more reliable in older individuals: The positive predictive value is 76 percent among users between the ages of 60 and 64, 91 percent among those aged 70 to 74, and 96 percent for those older than 85.

Here’s the bottom line: For the vast majority of individuals under age 55 whose Apple Watches tell them they have atrial fibrillation, the odds are high that the watch is wrong. But it is more accurate for the aging population that is becoming a part of the wearable generation.

Does this mean younger folks should ignore a notification about atrial fibrillation?

No. Even younger individuals whose Apple Watch signals atrial fibrillation should contact their physicians to discuss any symptoms or medical conditions that heighten the risk for this disease. The Apple Health app lets users download a PDF of the watch’s electrocardiogram tracing to send to a physician. Efforts to integrate data from this app with electronic health records are currently underway.

Daniel Yazdi, M.D., is a second-year internal medicine resident at Brigham and Women’s Hospital in Boston. A version of this article was published by Medtech Boston.

  • I previously wrote about high heart rate readings which were inaccurate on my Fitbit because I have a pacemaker. I replaced it with an apple 3 watch and the heartbeat readings are accurate with no problems because of the pacemaker.

  • I believe I asked this before. If so, please excuse the duplicate. I have a fit bit watch and a pacemaker. The fit bit gives me a very high heartbeat reading that is not accurate because of the pacemaker and I believe the apple watch will do the same. Can you confirm.

  • I’m glad that you’re looking at the PPV of the Apple Watch’s AF detection algorithm–I’m also curious to know more about this and appreciate your efforts in this regard.

    I’d like to respectfully raise a concern about how this analysis calculated the PPV. The incidence numbers come from a subgroup of one study, while sensitivity and specificity come from another study. Traditionally, the Bayesian calculator is used when all the inputs come from the same study, or, at very least, from studies with very similar methods.

    However, these studies used substantially different methodologies to determine whether atrial fibrillation was present (ATRIA relied on physician-documented diagnoses and diagnoses listed in a database of resting EKG’s, while Apple Heart used ambulatory EKG patch devices).

    The PPV of 19% is surprising. I suggest that we interpret this PPV with skepticism. Yes, the math is correctly calculated, but the inputs into the PPV formula maybe should not be mixed together. I hope you will follow this up with more PPV values that come from homogeneous (and hopefully high quality) data as it becomes available, and I thank you for taking the time to analyze this topic.

  • I am 42 with an Apple Watch Series 3 – no ECG app, just the heart rate sensor. I’ve always been healthy and stay in good shape, running and lifting weights. I laughed the first time I got an A-Fib alert. Then I got another. And then 6 more. Definitely false positives, I thought but I made a doctor appointment anyway just to clear things up. One EKG test yesterday confirmed I actually do have A-Fib which otherwise would have gone undiagnosed for who knows how long. So maybe I’m an outlier because I’ve never had any other symptoms and am not of an age that is common for healthy people to have A-Fib. Hopefully it will eventually go away with treatment and/or lifestyle changes but it might not and at least now I know. You hear stories about healthy people dying from some undiagnosed condition all too often. I’m happy I know and that I can now do what needs to be done so that I’m around for my wife and 3 girls as long as possible.

    • Troy, my experience is virtually identical to yours. My Apple 3 watch sent an A-Fib alert followed by four more alerts. Unbeknownst to me, my heart rate was 190 bpm. When I took my blood pressure reading, it was 195/115. My wife grabbed the phone and called 911. Minutes later an ambulance arrived at my home and I was rushed to a local hospital and spent four days on a cardiac unit floor. My A-fib was out of control for over 24 hours. The good news is I lived to tell the story about how my Apple Watch saved my life. I am a thankful husband, father and grandfather. Thank you, Apple.

  • The key here is not the fidelity of the ECG sensor (it has a terrific sensitivity/specificity), but rather what happens when a very large population is screened for an illness. There are bound to be false positives, and when the prior likelihood of disease is low (those under 55) the false positives will outweigh the true positives making misdiagnosis common.

  • Cautiously optimistic about the future of medicine after reading this. Hope Apple fixes the algorithm!

    • I’m not sure it can be “fixed”. It may already be at the limit of this sensor. Bear in mind it uses dry electrodes, which are sensitive to electrode movement and contact pressure. There’s only so much you can do, given the fundamental design of the sensor.

    • I have found that if a person has a pacemaker, both the Fitbit and the Apple Watch give false (high) readings for the heartbeat. Have contacted both companies but there doesn’t seem to be a fix for this.

  • This article highlights what happens when engineers / techies drive clinical apps. 20% accuracy rate may be OK in beta software or other industries, but this level of error will result in sending MDs already drowning in data more useless or bad info, and cause patients undue anxiety.

    Is this really helpful to anyone because Apple is “cool” ?

  • I am 75 years old and have a history of two episodes of A.fib 10 years ago. Almost coincident with the release of the ECG app I started having symptoms again. Fortunately I work in the healthcare field and got to cardiogram machine right away. Since then I have been using the app. It has “diagnosed” AF multiple times since then. Even with that history, I am reluctant to overwhelm my cardiologist with frequent ECG/EKG PDF’s. What I have done is text the PDF’s to myself and save them till my visit with the doctor or ask him if he wants to see them between visits. I even e-mailed them to my home computer and printed them out – full page 8X11″ paper. The cardiologist was impressed and found it easy to confirm the diagnosis.

Comments are closed.