Galaxy Watch Ultra2 & Watch9: Health Connect Data

1. Galaxy Watch Ultra2 and Galaxy Watch9 measure data and send it to Samsung Health.
2. From Samsung Health, the Samsung Health Data SDK offers a direct, read-only channel to FitMesh, independent of Health Connect.
3. Still from Samsung Health, data written to Health Connect reaches both FitMesh (a generic path, also used for other sources) and the Google Health app, via two separate links.
4. The Google Health API is a different system: a cloud infrastructure evolved from the Fitbit Web API, which doesn't automatically receive Galaxy Watch data and doesn't replace Health Connect.

What Samsung Announced

Samsung unveiled Galaxy Watch Ultra2 and Galaxy Watch9 on July 22, 2026, during Galaxy Unpacked, positioned as the new generation's "health companion on the wrist." According to Samsung, TM Roh (CEO, President and Head of the Device eXperience Division) said the two models "represent a massive leap forward in Samsung's health vision," continuously tracking vital signs from the wrist. Ultra2 focuses on extreme sports performance (Trail Run, diving to 100 meters with EN13319 certification), Watch9 on everyday comfort and battery life (Samsung states +20% capacity over the previous model for the 40 mm variant).

Official Specifications

Samsung explicitly states that "availability and features may vary depending on market, model and the smartphone paired" and that all specifications are "subject to change without notice": this table reflects the official 07/22/2026 press release, not an independent test on real hardware.

Health Features: Sensor, Samsung Health Score, or Data That Reaches FitMesh?

For each feature below we always distinguish: what the sensor measures, what Samsung Health displays, whether it's a proprietary Samsung score (not a standard data type) or raw data with a Health Connect equivalent, and whether FitMesh reads it, via which of the two paths.

• •Sleep Apnea (refined for this launch): the sensor detects breathing disruptions during sleep; an AI algorithm categorizes them into 3 levels, shown in Samsung Health. Samsung refers to "new FDA clearance," likely the same 2024 De Novo authorization already obtained for the base feature (the release doesn't specify whether this is a separate additional clearance). It's not a Health Connect data type. FitMesh reads only a boolean flag (detected/not detected), never the raw data, exclusively via the direct Samsung Health Data SDK channel. Requires a Galaxy phone on Android 12+, available only in select countries (not individually specified).
• •Vitals: the BioActive sensor measures heart rate, HRV, respiratory rate, skin temperature, and SpO2 during sleep; Samsung Health compares them against a personal baseline and alerts only on significant deviations. The individual raw metrics (not "Vitals" as a single score) have standard Health Connect equivalents. FitMesh reads them via Health Connect (heart rate, HRV, respiratory rate, SpO2) and via the direct Samsung channel (heart rate with priority, SpO2 and skin temperature as gap-fill); real skin temperature currently never arrives via Health Connect, only from the direct channel. Requires 7 nights of data, Android 11+, Samsung Health 7.0+.
• •Heart Health Score: a proprietary score combining body composition, sleep, stress, and activity into one value. Stays inside Samsung Health, no Health Connect equivalent, FitMesh doesn't read it. Requires a 24-hour initial setup, Samsung Health 7.0+; Samsung states it's not intended for the diagnosis of disease.
• •Daily Cardio Load: a proprietary score of accumulated cardiovascular strain, with estimated recovery times. Stays inside Samsung Health, FitMesh doesn't read it. Requires Galaxy Watch7 or above with One UI 9 Watch, Android 10+, at least 7 days of activity (28 recommended for accuracy).
• •Fitness Index: a proprietary score requiring at least one body-composition (BIA) measurement and one VO2 max measurement, plus two days of activity data. Stays inside Samsung Health. FitMesh doesn't read the score or the VO2 max feeding it: neither reaches FitMesh via either path.
• •Hearing: the watch's microphone monitors surrounding ambient noise and sends alerts and reports to Samsung Health (manual activation: Samsung Health > Hearing > Settings > Sound Monitoring). It's not a Health Connect data type, FitMesh doesn't read it.

Energy Score, AGEs Index, and Antioxidant Index are pre-existing Samsung Health features (announced in June 2026 for the whole Galaxy Watch lineup): the July 22 Ultra2/Watch9 launch release doesn't specifically re-announce them for these two models, so we don't present them as new to this launch. They remain proprietary scores regardless, not exportable, not read by FitMesh.

Two Distinct Paths, Not Just One

FitMesh doesn't receive Galaxy Watch data through a single channel that always goes via Health Connect. Once a data point reaches Samsung Health, there are two parallel, structurally distinct paths to FitMesh, with different permissions, different data surface, and even different merge priority when both report the same value.

• •Galaxy Watch -> Samsung Health -> Samsung Health Data SDK -> FitMesh: a direct channel, requiring Samsung partner approval (registered package name and SHA-256 signature), reading a selected subset of data types directly from the Samsung Health store, without going through Health Connect.
• •Galaxy Watch -> Samsung Health -> Health Connect -> FitMesh: the generic Android interoperability path, the same one FitMesh uses for any other compatible source (not just Samsung), independent of Samsung's approval.

For some metrics (heart rate, sleep) the direct Samsung channel takes priority when both paths report a value. For others (SpO2, workouts) Health Connect wins and Samsung only fills in missing data. Some metrics (blood pressure, sleep apnea, body composition, real skin temperature) arrive today ONLY from the direct Samsung channel, never from Health Connect. None of these rules are inferred: they're verified in FitMesh's merge code.

Samsung Health, Health Connect and Google Health Are Not the Same

• •Samsung Health is the app and store where Galaxy Watch data lands first: it's the starting point of both paths to FitMesh, not an API in itself.
• •The Samsung Health Data SDK lets approved partner apps (like FitMesh) read selected data types directly from the Samsung Health store, after registering a package name and signature with Samsung.
• •Health Connect is Android's on-device interoperability store, run by Google: any app can write to or read from it with user permission, regardless of device manufacturer.
• •The Google Health API is the evolution of the Fitbit Web API on a unified Google infrastructure: it is not the same thing as Health Connect, and the official documentation doesn't declare an explicit relationship between the two.
• •The Google Health API doesn't replace Health Connect: they're two distinct Google systems, with different purposes and access mechanisms (cloud OAuth API versus on-device store).
• •The Google Health API doesn't automatically receive Galaxy Watch data: the official documentation cites Fitbit, Pixel Watch, and generic third-party devices/apps, without naming Samsung as a source.
• •The consumer Google Health app doesn't connect directly to Galaxy Watches: per Google's own support page, syncing always requires Health Connect as an intermediary, plus explicit consent inside the Samsung Health app for data processing.
• •The new consumer Google Health app is therefore a distinct product from the Google Health API: the former is the end-user experience, the latter is the developer infrastructure. Further reading: Google Health vs. Google Fit, what changes.
• •FitMesh shouldn't be described as integrated with the Google Health API until a verified code path exists: no file in the repository calls it today.
• •In short: four distinct systems (Samsung Health, Samsung Health Data SDK, Health Connect, Google Health), not interchangeable synonyms, with different implications for which data FitMesh can actually read.

The Verified Matrix: From the Wrist to FitMesh

Two separate tables, not one. The first follows each metric or feature through four independent steps: what Galaxy Watch/Samsung Health shows, what's written to Health Connect, what FitMesh reads via the direct Samsung channel, what FitMesh reads via Health Connect. No column is inferred from the previous one: a yes in the first doesn't imply a yes in the second. The second table compares the four systems involved as platforms, not as metrics. States used: confirmed, not exported, not read by FitMesh, depends on version/region, not documented, not verified.

What FitMesh Can Read Today

FitMesh reads Galaxy Watch data through two parallel paths, not one with an exception. Via Health Connect: heart rate, HRV, sleep, SpO2, respiratory rate, workouts, and calories, once permissions are granted. Via the direct Samsung Health Data SDK channel (partner approval already obtained): heart rate and sleep with priority over the Health Connect value, plus SpO2, skin temperature, workouts, body composition, blood pressure, and sleep apnea (the latter only as a boolean flag, not raw data) available ONLY from this channel. FitMesh doesn't replicate any proprietary Samsung score (Heart Health Score, Daily Cardio Load, Fitness Index, Hearing, Energy Score, AGEs Index, Antioxidant Index): they don't exist as a data type in either path, so there's nothing to read.

Raw Data vs. Proprietary Score

A raw data point (heart rate, HRV, hours of sleep) is a directly measured value, with a standard unit, exportable as-is. A proprietary score (Fitness Index, Daily Cardio Load, Heart Health Score) is a derived calculation combining multiple raw data points with a non-public Samsung formula: two different apps can receive the same raw data but can never compute the same proprietary score, because the formula isn't publicly documented.

Compatibility and Android Requirements

Health Connect is Android-only: this FitMesh compatibility analysis covers exclusively the Android path. Samsung requires a phone on Android 13.0 or higher with more than 1.5 GB of memory and Google Mobile Services to activate Galaxy Watch Ultra2/Watch9: no Samsung-brand phone is required. Individual health features do have LOWER minimum requirements, inherited from the general Samsung Health platform (not specific to this launch): Sleep Apnea requires Android 12+, Vitals Android 11+, Daily Cardio Load and Fitness Index Android 10+; all require Samsung Health version 7.0 or higher and a Samsung account.

What You Can Verify Yourself

• •Open Samsung Health on your phone and check the app version in Settings: it must be 7.0 or higher for this launch's new features.
• •In Samsung Health, check whether your model and country show Vitals, Heart Health Score, Daily Cardio Load, Fitness Index, and Hearing: Samsung doesn't specify regional availability for each individual feature.
• •In FitMesh, open Settings and look for "Samsung Health": if available and connected, the direct channel is active (indicated by the string "Samsung Health connected, direct read active").
• •In Health Connect (a separate Android app, or inside Settings), check which apps have permission to write and read each data type: you can see whether Samsung Health actually writes the metrics you care about.
• •Compare the values you see in FitMesh against Samsung Health for the same day: if they differ, check which path has priority for that metric in Table A above.

Limits and Features Still to Verify

• •Samsung doesn't specify which Ultra2/Watch9 metrics are actually written to Health Connect: this remains "not documented" until verified empirically on real hardware.
• •Country-by-country availability of Sleep Apnea, Vitals, Heart Health Score, Daily Cardio Load, Fitness Index, and Hearing isn't individually specified by Samsung for Italy: the release refers generically to "select markets" or doesn't specify at all.
• •Whether and when FitMesh obtains a physical Ultra2/Watch9 test device to empirically verify (not just theoretically) Health Connect's real behavior on this model.

Sources, Methodology, and Verification Date

Methodology: the specs and health features cited in this article are verified directly against the text of Samsung Newsroom's 07/22/2026 press release (direct fetch, cross-checked with a second read of the raw HTML for numeric values like the processor name) and against the official Android/Google documentation listed in the sources. Claims about FitMesh's behavior are verified directly in the app's source code, not inferred from Samsung or Google documentation. Verification date: July 22, 2026.

History: first published on 07/22/2026, the day of Samsung's announcement. Any subsequent updates (regional feature availability, empirical verification on physical hardware) will be logged here with the date of the change.