DTRACCurrent state
Disabled by default:
health_connect.enabledisfalseinregistry.json, and the provider is absent from the allowlist. The implementation list below does not mean all these records are automatically collected by the baseline app.
The Android plugin reads records another app has shared with Health Connect. Records present only in the source app, but not shared to Health Connect, cannot be read through this path.
Implemented type paths
| Type | Observed code path |
|---|---|
steps | Read, event mapping, numeric ingestion |
sleep | Read, session ingestion, owner-scoped reconciliation |
heart_rate | Read/mapping, ingestion of the latest sample in each returned record |
exercise | Read/mapping, numeric exercise duration |
blood_glucose | Read, mapping, numeric ingestion |
blood_pressure | Systolic and diastolic numeric ingestion |
body_fat | Read, mapping, numeric ingestion |
weight | Type is declared, but its pull implementation is commented out |
Distinguish declared types from executable paths. In particular, weight is not documented as a completed collection feature.
Requirements and activation
Health Connect is integrated into Android 14 and later. Earlier versions may need the separate app. See the official Android setup guide for preparation and feature availability.
Activation requires aligning registry enabled, types, allowlist, build health-feature settings, and permission handling. Verify a real read and Room write after configuration changes. Documentation work does not change baseline collection settings.
Sleep records and time anchors
The app contains a Health Connect sleep-refresh path and a path that uses sleep-end records as evidence for a wake anchor. Background read access follows the executable sleep-anchor configuration and device capability. Missing records, missing permission, unavailable features, and read failures must not be treated as a valid sleep-end time.
Sharing scope is not integration scope
The presentation's '17 Samsung Health shared types' describes a source platform's sharing scope, not completion of 17 DTRAC integrations. Use the implementation table and study configuration to determine actual support.