Wearables & Health Data
Most of what happens to a client happens between visits. When a client connects a wearable — an Apple Watch, Oura ring, Whoop strap, Garmin, or a continuous glucose monitor — their daily sleep, heart-rate, activity, and recovery data flows into Ready Practice automatically. You see the trend on their profile, Atlas can reason about it, and their app shows them the same picture you're looking at.
Connecting a device is always the client's decision, made from their app. You never connect a device on their behalf, and a client can disconnect at any time.
How a client connects a device
Ask your client to open their app, go to their health or profile section, and choose to connect a device. They'll pick their brand, sign in to that brand's account, and approve the connection. From then on their data syncs on its own — there's nothing to press again.
Historical data usually backfills within a few minutes, and new days arrive automatically. A client with several devices can connect more than one; each contributes the metrics it measures.
Some devices report through the phone's own health app rather than connecting directly. For those, the client grants permission once in their phone's health settings, and the data flows the same way.
What you see on your side
Once a client is connected, their profile shows their metric trends — sleep duration and quality, resting and variable heart rate, steps and activity, and any glucose data — alongside their labs, notes, and program. That's the point of having it in one place: you can look at a recovery dip and their training load in the same view rather than asking them to describe their week.
The trend matters more than any single day. A client's HRV dropping for four days running is a conversation; one low night usually isn't.
Ask Atlas "how has this client been sleeping this month?" or "has anything changed in their recovery since we started the new program?" and it answers from these same metrics, in plain language.
How sleep is counted
Sleep is the metric clients check against their own device most often, so it's worth knowing exactly what the number means. The figure on a client's profile is time asleep, not time in bed — a client who lay down at eleven and got up at nine, but was actually asleep for seven hours, shows seven hours. Where their device reports its own asleep total, that is the figure used; where it reports only an in-bed window and a sleep-efficiency percentage, the two are combined.
A day's sleep includes every session that belongs to that night, so a nap counts toward the same day as the sleep that follows it. An evening nap on Tuesday is counted with Tuesday night's sleep and appears under Wednesday, which is how the client's own device reports it. A night that begins before midnight is credited to the morning it ends on, for the same reason.
This means the number you see should match what the client sees in their Oura, Whoop, or Apple Health app. If it doesn't, that's worth raising rather than explaining away.
When data looks wrong or missing
Wearable data depends on the client's device and their connection to that brand's service, so gaps happen for ordinary reasons: the device wasn't worn, the phone hadn't synced, or the brand's account was signed out. If a client's data stops arriving, have them open their app and confirm the device still shows as connected — reconnecting takes a few seconds and backfills what was missed.
A client's health data is theirs. It appears to your team only while they're an active client of your clinic with the connection in place, and disconnecting stops future syncing immediately.
Next steps
- To act on what the data shows: build or adjust a program in Clinical Protocols.
- To see the labs side of the picture: see Labs.