Samsung Health data, in your own stack.
Samsung Health writes to Health Connect on Android, so its data reaches Open Health Sync through the Health Connect upload, with no Samsung partnership needed.
- Source
- Galaxy phones, watches and rings
- How the data arrives
- On-device only: through Health Connect, which Samsung Health writes to.
What it collects.
Each record maps to the same model as every other source, with the provider, source and device it came from.
- Activity
- Sleep
- Heart rate
- Skin temperature
How it works.
- 01
Samsung Health writes to Health Connect
On the phone, the Samsung Health app shares its data with Health Connect.
- 02
Your app uploads it
Your app reads Health Connect and uploads it, as on the Health Connect page. Each record keeps Samsung Health as its source.
- 03
You read one model
The records land in the same model as every other source, over REST, MCP and FHIR R4.
Before you start.
- There's no Samsung cloud API to pull from.
- The Samsung Health Data SDK needs partner approval to distribute, and the older Samsung Health SDK for Android was deprecated on 2025-07-31.
- Records that arrive through Health Connect keep Samsung Health as their source.
Where to start.
Samsung Health has no connector of its own: set up the source its data goes through.
Questions.
Can I use Samsung Health with Open Health Sync today?
Yes, through Health Connect, which your app uploads. There's no Samsung Health connector of its own, and its records keep Samsung Health as their source.
Do I need anything from Samsung Health?
There's no Samsung cloud API to pull from.
Where does the data go?
Only to the server you run. Open Health Sync is self-hosted software, not a service: no account with us and no call home. Each user can be deleted with one call, raw files included.