Wearables and healthcare: why the first decade missed the point

Wearable health data is the most collected and least connected data in healthcare.

The hardware problem is solved. The Apple Watch can detect atrial fibrillation with enough accuracy to trigger a clinical referral. Continuous glucose monitors track blood sugar in real time. Heart rate variability, sleep architecture, respiratory rate — the sensors capture it all.

None of it reaches a clinician.

For most people, wearable health data lives in an app. It generates charts. It sends notifications. It stays on their phone. It never enters a medical record. It never becomes part of a care decision. A patient walks into a consult with years of continuous physiological data on their wrist, and the doctor starts from scratch.

The first decade of wearables was a hardware story. The next decade is an infrastructure story.

The missing layer is not better sensors — it's the clinical integration architecture that connects what a device measures to what a care team does. Data portability. Clinical interoperability. Consent frameworks that let patients share continuous data with their providers without surrendering control of it.

This gap isn't theoretical. In 2014, a wearable project for autism support faced this exact problem — the device worked, the sensors worked, but the infrastructure to make the data clinically useful did not exist. The architecture was right. The ecosystem wasn't ready.

Twelve years later, the ecosystem is catching up. The integration layer that makes device data part of a care pathway — not just a personal dashboard — is now being built into the same clinical platforms handling prescribing, dispensing, and patient records. One infrastructure, not two.

The first decade proved the hardware works. The second decade is about building the infrastructure to make it matter.