Sunday, February 24, 2019

ECG on Apple Watch Series 4



You may be aware that there is a new ECG app on the Apple Watch Series 4. An Apple Support page provides instructions on how to use the app and interpret the results. Since I'm a doctor and a geek, I'll try to provide a little more context about the Apple Watch ECG capabilities in layman's terms.

The Apple Watch ECG tracing (a portion of mine is pictured above) is a subset of what is formally known as a "12-lead ECG" that might be used in doctor's offices and hospitals. A full 12-lead ECG might look something like this:


It's called a 12-lead ECG because there are 12 combinations of the leads that are placed on a patient's body, with each lead representing the electrical signals between 2 points on the body. Those 12 leads are I, II, III, aVR, aVL, aVF, V1, V2, V3, V4, V5, and V6. The placement of those 12 leads on a patient's body and the understanding of the differences between those leads are beyond the scope of this blog, but suffice it to say that in certain scenarios, it is important to look at ECG tracings from multiple leads to tell what is going on.

A 12-lead ECG can reveal many different kinds of findings, such as:
  • Arrhythmias: atrial fibrillation, atrial flutter, ventricular tachycardia, ventricular fibrillation, Wolf-Parkinson-White syndrome, sick sinus syndrome (tachy-brady syndrome), atrioventricular nodal reentrant tachycardia, multifocal atrial tachycardia, wandering atrial pacemaker, 1st/2nd/3rd-degree atrioventricular block, premature atrial contractions, premature ventricular contractions, long QT syndrome, asystole, and many others
  • Ischemia (insufficient supply of oxygen to heart muscles): unstable angina and acute myocardial infarction (heart attack)
  • Structural abnormalities: cardiac aneurysms, dextrocardia, congenital heart defects, hypertrophic obstructive cardiomyopathy, atrial septal defects, and others
  • Miscellaneous: hyperkalemia, hypokalemia, hypercalcemia, hypocalcemia, digoxin effect, pericarditis, and many others
The Apple Watch Series 4 (and presumably beyond) can identify normal sinus rhythm (i.e., a normal rhythm that is found in healthy hearts) and atrial fibrillation (an abnormal heart rhythm in which there is no predictable periodicity to the heartbeats and the notable absence of a certain kind of electrical signal known as a P wave on the ECG), but it cannot currently identify any other problems such as the partial list above.

After demonstrating success with the detection of atrial fibrillation, I think it would be fairly straightforward for Apple to identify several other kinds of arrhythmias (from the partial list above) on a Series 4 Apple Watch simply by updating the software, and I predict that we will see this capability sometime soon. However, it makes a lot of sense to start with identifying atrial fibrillation because it is one of the most common cardiac arrhythmias, has potentially serious consequences if left undetected and untreated, and is fairly straightforward to computerize its detection on ECG.

That being said, there are some conditions such as detecting heart attacks that are unlikely to be performed on an Apple Watch because a heart attack results in ECG changes in some leads but not others, depending on its location. That is why we use all 12 leads to look for signs of ischemia in all regions of the heart. The Apple watch ECG tracing is more or less equivalent to lead I on a 12-lead ECG. It is essentially a 1-lead ECG or a "telemetry strip" reading.

I hope this sheds some light on the Apple Watch ECG app's current capabilities and limitations. Tim Cook recently stated, "if you zoom out into the future, and you look back, and you ask the question, 'What was Apple's greatest contribution to mankind,' it will be about health." With Apple's introduction of HealthKit (June 2014), the Health app (June 2014), ResearchKit (March 2015), CareKit (March 2016), and now the ECG app (December 2018), I think Apple is in an excellent position to do just that.

Saturday, February 23, 2019

Updates on macOS Mojave App Store

I have a MacBook Pro and iMac, both running macOS Mojave 10.14.3. Several days ago my MacBook Pro told me that I had an update waiting to be installed.



I dutifully updated my NordVPN application, and because I have the same application running on my iMac, I turned on the iMac, launched the App Store, and planned to update the app there too. However, the NordVPN update was nowhere to be found.



I could not find an option to check for updates or to refresh the App Store, so I waited several minutes to no avail.  I tried quitting and re-launching the App Store, but still no success. It wasn't until the next day that the App Store on my iMac gave me the option to update my NordVPN application.

So this made me wonder if there is some sort of queueing protocol where not all users are given the option to update applications at the same time, perhaps to avoid server bandwidth issues? Anyone else see similar behavior on 2 separate Macs?

Friday, February 22, 2019

I'm All In


I've purchased a variety of Apple products over the years: Apple //e, Mac Classic II, 17-inch G4 iMac, 24-inch Mid-2007 iMac, and 27-inch Late-2012 iMac. Our family also owns two iPads, two iPhones, and an Apple TV. I've also used MacBook Pros for work and was recently gifted a set of AirPods. A couple of years ago, I bought an Apple Watch for my wife but had not used one myself until a couple weeks ago when we won an Apple Watch Series 4 in a raffle—woo hoo, come to Digital Daddy!

Clearly I am fully invested in the Apple ecosystem. In any case, I'll be blogging in the near future about some observations related to the Apple Watch so stay tuned!

Excuses Excuses


As described in my previous post, I recently bought a GoPro HERO7 Black. It records video at 4K (3840 x 2160). It's technically not my first device that is capable of capturing 4K video. My GoPro HERO3+ Black records video at 4K 15fps, but I found the 15fps frame rate to be unacceptable in most situations, so I mostly used 2.7K 30 fps and 1080p 60fps. However, my GoPro HERO7 Black records video at 4K 60fps (woo hoo) which means that I'll be recording a lot more 4K video.

Much to my dismay, Final Cut Pro X told me that my Late 2012 27-inch iMac (2.9 GHz Intel Core i5 processor) isn't quite powerful enough to edit 4K video (or larger). I proceeded to edit a 4K project anyway, and sure enough the skimming and previewing of 4K video is quite choppy and results in a significantly degraded editing experience. However, upon export, the 4K video plays smoothly in VLC Media Player, QuickTime Player, and of course YouTube.

The bottom line is that now I have an excuse to buy a new 27-inch Retina 5K iMac. ðŸ¤“