---
title: "Wearable Data for Clinics and Care Teams"
description: "Ready-made solutions for wearable health data: monitor patients, update health records, run studies and power your app, running in your own cloud."
canonical_url: "https://openwearables.io/medica"
---

# Ready-made solutions for wearable health data

[Join our Discord community](https://discord.gg/qrcfFnNE6H)

Monitor patients, update health records, run studies and power your app with data from the wearables people already own.

[Book a call](https://openwearables.io/medica#book) [Get started](https://openwearables.io/docs/quickstart)

Built by

[2.6k](https://github.com/the-momentum/open-wearables)

- Open source
- Self-hosted
- MIT license

How it works

## From the wearable to your team, in your own cloud

Open Wearables is open-source infrastructure for wearable data. Connect the devices your patients already own, keep the original data, and build scores and insights on top, all inside your own cloud account.

### Patients connect what they already wear

Invited with a link or a QR code, they pick Apple Health, Health Connect or their wearable account and confirm who receives the data.

### Readings land in your own cloud account

Every connected source arrives in one format, in your region, under your credentials, with consent recorded alongside.

### Scores and summaries on top

Health scores and summaries of each patient's trends, computed inside your deployment.

### Where your team already works

Your app, your health records, a care view for your team or a research dataset, with the source on every value.

Who is it for

## Make wearable data part of how you work

Each one runs on Open Wearables in your own cloud, set up and shaped around how your team works.

### Remote patient monitoring

Patients join with a QR code. Your care team sees who is wearing their device and who dropped off.

A care team's week: which patients are syncing and which have gone quiet.

### Clinical research

Every value traceable to its device and raw payload, in your own database.

A reviewer asks where a participant's resting heart rate came from; the answer shows the value, its device and the raw payload as it arrived.

### Telemedicine

Readings land in the health records your clinicians already open, with source and consent on each value.

A patient's record with wearable readings beside visits, results and medication.

### Care programmes and virtual wards

Hospital at home, post-discharge follow-up and chronic care programmes that need readings from home without a device logistics project.

A heart failure patient's readings, each with its device and sync time, beside fourteen days of weight rising 1.1 kg in three.

### Longevity and prevention centres

Programmes built on members' own wearables, where the history between visits is what the member pays for.

A brief before a 10:30 follow-up: sleep down 35 minutes a night and resting heart rate up 4 bpm since the last visit.

### Digital health applications

Connect your users' wearables through one API and mobile SDKs, under your brand.

An app under your brand suggests an electrolyte mix after three long sessions, and says why.

Use cases

## What your team can do with it

Open Wearables collects readings from the devices your patients wear. We deploy it in your account and set up the rest with you, so the programme starts without a software project in front of it.

### See who dropped off

Your care team sees who is wearing their device and who dropped off, with trends, adherence, raw values and notes for each patient. It shows the data and leaves every decision to your team.

### Readings in the record

Readings written into the patient record your clinicians already open, with the device, source and consent on every value, mapped to the system you run, and a weekly summary per patient.

### A summary of each patient

Summaries of each patient's trends for the care team, inside the scope you define.

### Patients join with a QR code

Patients scan a QR code or open a link, then connect their phone and wearables in our Connect App, with no account to create. If you already have a patient app, the same connection can sit inside it.

### Data that stays yours

Your account, region and credentials, with upgrades and provider changes handled by the team behind Open Wearables under a clinical SLA.

What patients see

## A reason to keep wearing it.

Patients see their own readings explained in plain language, so they keep wearing their device between visits.

### A morning summary

Last night against their own recent nights, in plain language.

### A nudge when a device goes quiet

When a watch stops syncing, the patient gets a reminder before your care team has to call.

### Progress since the last visit

What changed since their last appointment, in their own numbers.

### Answers about their own readings

A question about a reading gets an answer measured against their own usual range.

Built on Open Wearables

- Heart Monitor logo
- Hundred logo
- JustGains logo
- Lifelong logo
- MoveTogether logo
- ROXFIT logo
- Smarter Diagnostics logo
- Suna logo
- Yoboo logo

## Let's talk

Book a call with our team.

- 30 minutes, online On Google Meet, at a time that suits you.
- A live demo The care view, health records and AI insights, shown running.
- Your use case How it could fit your patients, your record and your cloud.

> “Open Wearables was our second commit. Five days later, we had real Apple Watch data in Lifelong. It let us start building the family experience instead of rebuilding wearable ingestion.”

Razi Syed Founder, Lifelong

## Connect the devices your patients already own.

Every device arrives in the same format, so a patient who switches watch or adds a ring changes nothing for your team.

[Browse integrations](https://openwearables.io/integrations)

- [Garmin integration](https://openwearables.io/integrations/garmin)
- [Whoop integration](https://openwearables.io/integrations/whoop)
- [Oura integration](https://openwearables.io/integrations/oura)
- [Polar integration](https://openwearables.io/integrations/polar)
- [Suunto integration](https://openwearables.io/integrations/suunto)
- [Withings integration](https://openwearables.io/integrations/withings)
- [Strava integration](https://openwearables.io/integrations/strava)
- [Ultrahuman integration](https://openwearables.io/integrations/ultrahuman)
- [SensorBio integration](https://openwearables.io/integrations/sensorbio)
- [Google Health API integration](https://openwearables.io/integrations/google-health)
- [Fitbit integration](https://openwearables.io/integrations/fitbit)
- [Apple Health integration](https://openwearables.io/integrations/apple-health)
- [Google Health Connect integration](https://openwearables.io/integrations/google-health-connect)
- [Samsung Health integration](https://openwearables.io/integrations/samsung-health)

FAQ

## Do you have more questions?

### How does the call work?

Thirty minutes on Google Meet with the team behind Open Wearables: a short intro, a live demo and a look at how it could fit your use case.

### Do we need our own developers?

No. We deploy Open Wearables in your cloud account and set up the patient app and the care view with you. If you have developers, they can build on the same API.

### How do you integrate wearable data into an EHR?

Open Wearables collects readings from the patient's devices into your own cloud account, maps them to FHIR resources (Observation, Device, Provenance and Consent) and writes them into your record, as part of the rollout. Where the record cannot accept writes yet, a clinician view runs beside it.

### Which wearables can patients use?

The devices they already own, such as Apple Watch, Garmin, Oura, Withings and Samsung, through Apple Health, Health Connect and each provider's own connection. The [integrations page](https://openwearables.io/integrations) lists the current sources.

### Where does patient data live?

In your own cloud account, in the region you choose. When we work on your deployment, we do it under a data processing agreement you sign.

### How long until we are live?

About a month from the start to the first patients sending data. Your first cohort then runs for three to six months before the programme scales.
