Connected device data

Turn patient-permitted device signals into clinic-ready context.

TherapyPod's connected-device layer turns the sources patients choose to share into trend summaries, follow-up cues, and program context for their care team.

Request a device workflow demoView AI device insights
Connected device workflow dashboard

From signal to workflow

Device data becomes useful only when the care team can act on it.

Source types patients can connect

The patient portal already models health apps, wearables, clinical devices, and manual entry as data sources. Availability can vary by clinic program and patient account.

Patient connection area
Apple Health
Google Fit
Fitbit
Oura Ring
Garmin Connect
Samsung Health
Withings
Dexcom CGM
Manual Entry

How device data becomes useful

The value is the workflow around the data: consent, normalization, trend review, and escalation when a care program needs a human response.

01

Connect with consent

Patients choose which health app, wearable, or manual entry source to connect from their My Health area.

02

Normalize the signal

TherapyPod maps source-specific readings into consistent metric types like heart rate, sleep, steps, glucose, and blood pressure.

03

Summarize trends

Care teams can review patient-friendly highlights and trend patterns instead of raw device feeds.

04

Route what needs attention

Device context can support follow-up, patient education, and human review workflows when a clinic program requires it.

Metric context for real care programs

Instead of raw device feeds, clinics get patient context shaped for chronic care, maternal care, post-visit follow-up, and front-desk triage.

Daily activity

Steps, active minutes, calories, distance

Heart signals

Heart rate, HRV, SpO2, blood pressure

Sleep and recovery

Sleep duration, quality, recovery patterns

Chronic care context

Glucose, weight, manual readings, program-specific notes

Guardrails

Device data needs clinical boundaries.

TherapyPod does not sell hardware from this page or imply that a device reading is a diagnosis.

Patient data access is permission-based, and patients can disconnect sources from their account.

Device context is used to support care workflows, trend review, and escalation logic, not replace clinicians.

For clinic teams

Discuss which device workflows fit your care model.

Request demo

For insight exploration

Review the device-attribute intelligence layer.

Explore insights

For enrolled patients

Manage connected health sources from My Health.

Sign in