Connected device data
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.

From signal to workflow
Device data becomes useful only when the care team can act on it.
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 areaThe value is the workflow around the data: consent, normalization, trend review, and escalation when a care program needs a human response.
Patients choose which health app, wearable, or manual entry source to connect from their My Health area.
TherapyPod maps source-specific readings into consistent metric types like heart rate, sleep, steps, glucose, and blood pressure.
Care teams can review patient-friendly highlights and trend patterns instead of raw device feeds.
Device context can support follow-up, patient education, and human review workflows when a clinic program requires it.
Instead of raw device feeds, clinics get patient context shaped for chronic care, maternal care, post-visit follow-up, and front-desk triage.
Steps, active minutes, calories, distance
Heart rate, HRV, SpO2, blood pressure
Sleep duration, quality, recovery patterns
Glucose, weight, manual readings, program-specific notes
Guardrails
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.