RingConn data, in your own stack.
RingConn publishes no developer API, but the RingConn app writes to Health Connect on Android and to Apple Health on iPhone, so its data reaches Open Health Sync through those uploads.
- Source
- Smart rings
- How the data arrives
- Through Health Connect (Android) or Apple Health (iPhone), which the RingConn app 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.
- Steps, active and resting energy
- Sleep with stages
- Resting and average heart rate
- SpO2
- Weight and height
How it works.
- 01
RingConn writes to Health Connect or Apple Health
On the phone, the RingConn app shares its data with Health Connect or Apple Health.
- 02
Your app uploads it
Your app reads Health Connect or Apple Health and uploads it, as on the Health Connect or Apple Health page. Each record keeps RingConn 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.
- Nothing to register with RingConn: the user turns on the RingConn app's Health Connect or Apple Health sync.
- RingConn doesn't share HRV with Health Connect.
- Records that arrive through Health Connect keep RingConn as their source.
Where to start.
RingConn has no connector of its own: set up the source its data goes through.
Questions.
Can I use RingConn with Open Health Sync today?
Yes, through Health Connect or Apple Health, which your app uploads. There's no RingConn connector of its own, and its records keep RingConn as their source.
Do I need anything from RingConn?
Nothing to register with RingConn: the user turns on the RingConn app's Health Connect or Apple Health sync.
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.