--- title: "Remote Monitoring for Care Providers" description: "Remote patient monitoring on wearables for care providers: a patient app, a care view for your team and support, licensed per programme and run in your own cloud." canonical_url: "https://openwearables.io/for/care-providers" --- # Run a monitored programme without building the software. Care programmes Open Wearables for care programmes, clinics, senior care and prevention centres: a patient app, a care view for your team and support, running in your own cloud account from the first reading. [Book a demo](https://openwearables.io/book?tier=programme) Already running on Open Wearables - Heart Monitor logo - Hundred logo - JustGains logo - Lifelong logo - MoveTogether logo - Suna logo - Yoboo logo The problem ## Your patients already wear the devices. Using that data in a programme is the hard part. Care programmes, senior living operators and prevention centres tell us the same thing: the readings exist, but turning them into something a care team can trust and act on takes software they do not have. ### Everyone wears something different An Apple Watch, an Oura ring, a Withings scale, a glucose sensor: each with its own app, API and level of detail. ### A number you cannot trust A vendor changes its algorithm without notice, or a device misses a night. Before calling a patient, your team needs to know where a value came from. ### The right view for each team Caregivers on each campus or site see their own residents, with wellness and medical readings kept apart on one screen. ### A pilot that waits on a build Building the patient app, the backend and the team view in-house takes months before the first patient joins. The solution ## Everything around the data, so your team can run the programme 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. ### Connect App Patients join with a link or a QR code and connect their phone and wearables, with no account to create. If you already have an app, our SDK goes inside it instead. [Learn more](https://openwearables.io/platform/connect-app) ### Care view Trends, adherence, raw values and notes for each patient, with roles per site. It shows the data and leaves every decision to your team. ### Consent records Each patient sees who receives the data and chooses what to share. The consent is recorded next to their readings from the first day. ### Runs in your cloud Production and staging in your own cloud account, in the region you choose, under your credentials. The data, the keys and the code stay yours. ### Support Provider changes, upgrades and fixes handled by the team behind Open Wearables, with response windows agreed in your contract. What it does ## From a patient's wrist to your care team, in three steps. 01 Connect ### 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. 02 Your cloud ### Readings land in your own cloud account Every connected source arrives in one schema, in your region, under your credentials, with consent recorded alongside. 03 Your team ### Your team sees the week at a glance Days worn, trends and the last sync for each patient, on one screen per site. The outcome ## Continuous, remote monitoring of your patients' health. The questions a care team asks first, answered before anyone opens a spreadsheet. ### Chronic care between visits Heart failure, diabetes or COPD programmes: who is syncing, who has gone quiet, and a reminder on its way. A week of syncs across a heart failure programme, 36 of 42 syncing, two quiet patients to remind, one reminder sent. ### Follow-up after discharge Each patient's readings beside the weeks before, with the device each value came from. A heart failure patient's readings, each with its device and sync time, beside fourteen days of weight rising 1.1 kg in three. ### Senior care and prevention Residents or members followed across sites, with what changed since the last visit ready before it. 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. Who it is for ## Organisations that look after a group of people between visits. If you run the programme rather than build software for others, this page is for you. ### 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. ### Clinics Clinics that want to see how patients do between appointments, with the data kept in an account the clinic controls. ### Senior care operators Residential and home care providers following residents' sleep, activity and heart rate across sites, with roles per site. ### Longevity and prevention centres Programmes built on members' own wearables, where the history between visits is what the member pays for. ## Connect the devices your patients already own. Each connected source arrives in the same schema, so a patient who switches watch or adds a ring changes nothing on your side. [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) ## See it running for your programme. Tell us about your patients or residents and what you want to follow, and we will show you Open Wearables set up for it. [Book a demo](https://openwearables.io/book?tier=programme) FAQ ## Do you have more questions? ### 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. ### 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. ### Which devices can patients use? The consumer wearables they already own, through Apple Health, Health Connect and each provider's own connection. The [integrations page](https://openwearables.io/integrations) lists the current sources. ### Can residents without a smartphone take part? Most wearables sync through a phone today. For residents without one, we work out the setup with you during the first cohort, such as devices that sync on site. ### What happens when a device vendor changes its algorithm? Every reading keeps the device, the provider and the raw response it arrived in, so a change can be traced to its source instead of reading as a change in your patient. ### Can each site or campus have its own access? Yes. Roles are set per site, so each team sees the patients assigned to them, and patients see only their own data. ### 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.