Wearable Sensors in Clinical Practice: What Consumer Devices Can and Cannot Tell a Doctor

Patients now arrive with screenshots from their watches. Heart rate graphs, sleep scores and rhythm notifications are common in the consulting room. Clinicians have to decide how much weight to give them.

The answer is neither “ignore it” nor “trust it”. It depends on what the sensor measures, how it measures it and what question is being asked.

How wearable sensors work

Most wrist devices rely on photoplethysmography (PPG), an optical method. A light shines into the skin, and a sensor detects changes in reflected light as blood volume pulses. From that signal the device estimates pulse rate and, in some cases, other values.

Other sensors add different information:

• Accelerometers detect movement and support step counts, activity and sleep estimates.
• Electrical sensors on some devices record a single-lead electrocardiogram when the wearer touches an electrode.
• Temperature and oxygen sensors estimate values that clinicians usually measure with dedicated equipment.

Where error comes from

Optical readings are sensitive to motion, fit, skin tone, tattoos and ambient light. A reading taken during a run is not comparable to one taken at rest. Manufacturers use filtering and algorithms to compensate, but the result is still an estimate.

Cleared features versus the whole device

A common misunderstanding is that a “FDA cleared watch” is a medical device in every respect. Regulators typically evaluate a specific function for a specific intended use. A rhythm notification feature can be cleared while the sleep score on the same device is a general wellness feature with no clinical claim.

The question is never whether the device is medical. The question is whether this feature has been evaluated for this purpose.

Clinicians and buyers can check this by looking at the manufacturer’s labeling and at the regulator’s public device databases, rather than relying on marketing language.

What clinicians find useful

Practitioners who work with wearable data often describe the same pattern. Single readings are rarely actionable, but longer patterns can prompt a conversation.

Trends over snapshots

A resting heart rate that drifts upward over several weeks, or an activity level that drops sharply after a procedure, can be informative. These changes are relative to the same person and the same device, which avoids many calibration issues.

Screening versus diagnosis

A notification about an irregular rhythm is a reason for follow-up, not a diagnosis. Confirmation usually needs a clinical-grade recording and an interpretation by a clinician. Wearable data works best as a prompt for that process.

Practical guidance for care teams

Teams that accept patient-generated data can reduce friction with a few steps:

1. Decide which data types the clinic will review, and say so in advance.
2. Ask patients to note the device model and how they wore it.
3. Record wearable data as patient-reported context, not as a verified measurement.
4. Avoid building clinical protocols on features without a clinical claim.

Privacy and data flow

Data from consumer devices usually sits with the manufacturer, under the manufacturer’s terms. It may not be covered by the same rules as data held by a hospital. Patients should know where their data goes before they share it with an app or a clinic portal, and clinics should know whether they are the owner of any data they import.

Where the field is heading

Wearables are becoming better at continuous, low-effort data collection, and researchers continue to study which signals have clinical value. Evidence is growing in some areas and thin in others. A measured approach helps: use the data where validation exists, treat the rest as context, and keep the clinical decision with the clinician.