Apple is expanding the health warnings on the Apple Watch. With version 7.2 of watchOS, users can be warned if their fitness level is classified as low. The watch will then give advice on how to improve cardio fitness through more exercise and also provide tips on how to “talk to your doctor”, as Apple announced. According to the manufacturer, it is a “clinical assessment”.

Cardiorespiratory fitness is an important “variable for predicting general health “, stressed Apple with reference to the American Heart Association – low cardio fitness could lead to an increased risk of cardiovascular diseases.

Cardiofitness assessment with comparison and warning function for low values.

(Image: Apple)

VO2max for fitness assessment For the determination of cardio fitness, Apple uses the from the watch’s maximum oxygen capacity (VO2max) of the wearer. The watch estimates the VO2max value based on heart rate and movement data – common practice for sports watches and smartwatches. As of watchOS 7.2, lower data should now also be recorded by the watch estimating the maximum oxygen capacity in the background during movement during the day, even without performing a training session, as Apple explains. Previously, the Apple Watch only determined VO2max during workouts (running, hiking, brisk walks) – and was therefore only available for active users.

On the iPhone, the Health app from iOS 14. 3 also provides an assessment of whether the cardio fitness -Level is classified as high or low and compared to age group and gender as above or below average. For this, Apple uses the fitness database of the Mayo clinics. The Cardiofiness warnings are optional and must first be activated by the user.

Improved ECG app With watchOS 7.2, Apple is delivering version 2 of the EKG app in the first regions. It should also be able to check for atrial fibrillation arrhythmia at a heart rate of up to beats per minute (BPM) , with version 1 of the app this is only possible up to 120 BPM. Even at a heart rate of over 100 BPM, the EKG app may have shown “ambiguous” as a result so far, this should be with Version 2 does not happen.

(lbe)