Sleep and wearables

You already own the thing that knows how you slept. It's on your finger or your wrist, it has been counting your nights for months, and none of it has ever made it into the conversation about your thyroid.

Short answer: Osmi connects Oura, WHOOP, and Apple Health, and reads your sleep, heart rate, and exercise from whichever one you use. Those numbers land on the same dated record as your labs, your symptoms, and your cycle, so you can see what tracks with what. Your sleep card shows the hours you were actually asleep against your own usual, counted from your own nights. Osmi never grades a night and never tells you what your sleep means about your thyroid. If you don't wear anything, nothing here is closed to you. Osmi works from your check-ins on its own.

What Osmi does with your ring or your watch

Three names, and they're peers. Oura, WHOOP, and Apple Health each connect to Osmi directly, and you pick the one you already use. Nothing routes through the others.

From whichever you connect, Osmi reads three things: your sleep, your heart rate, and your exercise. That's the list. It isn't the longest list in the app store and it isn't meant to be. Those are the signals that come in without you doing anything, and a signal you don't have to type is the only kind that survives a bad week.

That's the whole logic of connecting a device. Everything else in Osmi asks you for a minute. This asks you for nothing after the first tap. Connect Oura, WHOOP, or Apple Health, and your sleep, heart rate, and exercise land on the same record as your labs and your symptoms.

What Osmi does not do with those numbers matters just as much. It doesn't score them. It doesn't decide your night was good or bad. It doesn't tell you a short night means something about your thyroid, and it never will, because that sentence isn't Osmi's to write.

What you see: your sleep card

Open Osmi in the morning and your sleep card is sitting on your Home screen, above your last panel.

It's built in four parts, in this order. First, what it is: the hours you were actually asleep, from your watch. Not sleep quality. Not a stage breakdown. Not a readiness number. Hours asleep.

Then what can affect it, folded away until you want it.

Then your data. Your usual, worked out from your own nights, sitting as a line across a chart of your last fourteen. Last night sits at the end of the row, with its own figure beside it.

Then one sentence that reads the chart back to you. Six of your last fourteen nights came in under six hours. Read that again and notice what it is. It's a count. It isn't a warning, it isn't a target you missed, and there's no number of hours Osmi thinks you should be getting. Your usual is yours, the count is of your own nights, and the anchor never comes from us.

That distinction sounds small on a product page. It's the entire difference between a record you can take to an appointment and an app that spent six months telling you that you're doing badly.

No ring, no watch, nothing missing

The honest answer to "do I need one" is no.

Osmi works from your daily check-in and your scans on its own. A wearable makes your daily read sharper, because sleep and heart rate are things you shouldn't have to type. That's the entire claim. It saves you typing. It doesn't detect anything. Wearing a ring doesn't switch on some other version of the app, and not wearing one doesn't put you on a lesser one.

It's worth saying why, because the reasoning is the product. No ring measures brain fog. No lab measures cold hands. The things you notice are first-class data in Osmi, dated and counted the same way a synced number is, and most of what the app does runs with no device and no bloodwork at all. A woman who types four answers a day and photographs a lab report twice a year has a real record. That was the design from the start.

And if you connect a device later, nothing you typed gets overwritten. An import fills in the gaps around your own entries. It doesn't correct you.

Where your sleep sits in the rest of your record

One number on its own is a number. The reason to bring your sleep into Osmi is everything it ends up sitting next to.

Your labs move two to four times a year. How you feel moves every day. Osmi holds both on one dated record. That join is the thing Osmi is for, and it's a join your provider portal and your ring's own app don't make. On your cycle screen, a day reads as what you recorded: cold hands, low energy, six hours twenty of sleep. On your appointment sheet, your sleep leaves the app as a single row, a thirty day median, on the same sheet as your TSH, your antibodies, and how many days out of thirty you were cold. The sheet says what it is at the bottom: not a diagnosis, your own numbers, in the order you will need them.

There's a reason sleep earns a place on that sheet. The American Thyroid Association's patient booklet lists more fatigue, trouble awakening in the morning, need for more sleep, and a tendency to fall asleep during the day among the common features of hypothyroidism. The same booklet is just as clear about the limit: hypothyroidism cannot be diagnosed based on symptoms alone, and most hypothyroid symptoms are common complaints. The NIDDK says the same thing from the other side, that many of these symptoms, especially fatigue and weight gain, are common and do not necessarily mean you have a thyroid problem.

So sleep is on the list, and the list settles nothing by itself. Which is exactly why a dated run of your own nights is worth more in the room than any single one of them. If you want the longer version of that question, we wrote it up in is there an app that connects my sleep data to my thyroid symptoms, and the rest of the record is covered in the thyroid symptom tracker.

Your wearable data is in Osmi to build your reads, and nothing else. It's never sold and never used for ads, and you can export or delete all of it whenever you want. The full version of that is in our privacy policy.