Exploring HealthTech innovation through expert knowledge and industry insights.





Your wearable aggregator now needs your own Garmin API key: what it means for your product and how to pick your next step.

%25201.png)
Open Wearables 0.10.0 brings a rebuilt dashboard, 42 nutrition data types, sync-aware webhooks and more accurate calorie data.


The Garmin Connect Developer Program reopened with new tiers and stricter third-party rules. What health product teams should check next.


Nine questions that scope an EHR integration in one discovery call, from who authenticates to clinical notes, BAAs and scale.


Which clinical notes a clinical data integration pulls from the EHR and when de-identifying them becomes a separate build.


A quick-reference comparison of the four EHR integration paths and which one fits your product's authentication model.


How to merge wearable data from several devices into one reliable record per metric, with overlap rules per data type that survive reprocessing.

.png)
Data ownership for wearable health products: who owns raw data and derived scores, and how to keep both when you switch vendors.

%201.png)
Open Wearables 0.9.0 splits Google into two providers, renames energy to active_energy, and fixes inflated Google Health API energy data.
