Wearable trends in context. Browse wearables
Wearables

Your device knows. Nothing else does.

Bring the export in once, and the trend stops living in its own app.

File import works today across every device below. Signed-app phone sync is built and stays gated until store and real-device verification is complete.

  • Sleep
  • HRV
  • Resting heart rate
  • Training load
  • Readiness
After the import72READYSleep debt, seven days1.2 hTraining load, this week412HRV, seven-day line58 ms

What can come in

Six ways in,three of them live

Most health products count every provider they have heard of. This is the shorter, duller, true list: what you can actually do today, and what is built but waiting.

  • Wearable export files

    Live

    A CSV, JSON or zip you download from the device app yourself. This is the broad path, it works today, and it covers every device on this page.

  • Apple Health export

    Live

    The zip the Health app hands you, carrying whatever your watch, phone and connected apps have written into it.

  • FHIR and C-CDA files

    Live

    Records from a portal or a provider, read by their own parser and held to the same review step as everything else.

  • HealthKit sync

    activation gated

    Built for the signed iOS app, and gated until store and real-device verification is complete. It is not live, and this page will not say it is.

  • Health Connect sync

    activation gated

    Built for the signed Android app, gated on the same terms. Same code, same review step, waiting on the same verification.

  • Cloud device sync

    future adapter

    A paid aggregator sits behind one normalized boundary for later. It is a future adapter, not a current dependency, and nothing today runs through it.

A device catalog is not a count of live connections, and Ojava will not present it as one. File import is the broad live path today. Every gated row above is real code waiting on a real verification step, and it says so on the label rather than in a footnote.

Eight devices

Pick the onealready on your wrist

Each page says what that device records, what the export actually contains, and what happens to it once Ojava has read it.

  • Oura Ring

    Sleep, HRV, temperature, readiness

    Prepare sleep, recovery, temperature, and HRV exports for context alongside labs and symptoms.

  • Fitbit

    Steps, sleep, heart rate, workouts

    Use manual activity, sleep, heart-rate, and habit exports as patient-owned context for visit prep.

  • Peloton

    Workouts, output, load

    Stage workout trends, perceived exertion notes, and capacity context as wellness history.

  • Garmin

    HRV status, VO2max, training load

    Read HRV status, resting heart rate, sleep, VO2max, and training load as trends against your records.

  • Apple Watch

    Heart rate, rings, sleep, VO2max

    Use heart rate, HRV, activity, sleep, and VO2max exports as wellness context alongside your chart.

  • WHOOP

    Recovery, strain, HRV, sleep

    Turn recovery, strain, HRV, and sleep performance into readiness context for a clinician conversation.

  • Eight Sleep

    Stages, HRV, bed temperature

    Read sleep stages, HRV, resting heart rate, and temperature trends as recovery context.

  • Ultrahuman

    HRV, sleep, temperature, movement

    Read HRV, resting heart rate, sleep, temperature, and metabolic context as wellness trends.

Once it lands

Readings becomenumbers you can use

Nothing joins your record until you accept it. After that the arithmetic is fixed: the same inputs give the same answer every time, and the coach reads those finished values rather than inventing its own.

What one week producesExample
Sleep debt, seven days1.2 h
Readiness, this morning72 of 100
Training load, against a four-week average of 386412

Example screen, with illustrative values.

  • The night

    Stages, duration, consistency, HRV and resting heart rate become sleep debt and a readiness number, computed in code from your own accepted readings rather than a population average.

  • The week

    Sessions roll into a weekly training load, read against your own four-week average with rest days counted in, so a heavy week reads as heavy for you.

  • The rest of the record

    Those finished numbers sit beside the meals you logged, the panels you accepted and the documents you brought in, which is the only place a trend can actually explain itself.

Wellness context, and it stays there.

Consumer wearables are wellness devices, and Ojava treats them as wellness devices. Readings become trend context and material for a conversation with your own clinician.

  • Not continuous monitoring, and not a medical device.
  • No diagnosis, no prescription, no dose, no lab order.
  • No clinical alert, and no replacement for your clinician.
Bring it in

One export,then it is quiet

Drop the file in, accept what the reader found, and your nights and sessions sit beside your food, your labs and your records from then on.

  • You accept it first

    Every reading waits in review. Nothing joins your record until you say so, and a wrong value can be fixed by hand.

  • Two devices, one night

    Overlapping readings are collapsed before anything is stored, so a night is never counted twice in a baseline.

  • Yours to take back

    Export or delete what you brought in whenever you decide it should leave. No ad targeting, and no model training on your health records.

Ojava is a General Wellness product. It organizes and explains your own data and helps you prepare for a visit. It does not diagnose, prescribe, dose, order labs, or replace your clinician.