--- title: "Telehealth EHR Integration for Wearables" description: "Wearable data in your EHR for hospitals and telehealth: remote patient monitoring readings in the patient record, a source on every value, in your own cloud." canonical_url: "https://openwearables.io/for/hospitals-telemedicine" --- # Wearable data in the EHR your clinicians already open. Hospitals and telemedicine Open Wearables for hospital groups and telemedicine platforms: readings from patients' own devices written into your record, with the evidence an auditor asks for, running in your own cloud account. [Book a demo](https://openwearables.io/book?tier=clinical) Already running on Open Wearables - Heart Monitor logo - Hundred logo - JustGains logo - Lifelong logo - MoveTogether logo - Suna logo - Yoboo logo The problem ## Clinicians want wearable data in the record. Today it lands everywhere else. Patients bring readings from their own devices to consultations as screenshots and exports. Getting those readings into the EHR, traceable and in a form an auditor accepts, is a project most hospitals have no team for. ### Readings outside the record Screenshots, exports and separate dashboards that clinicians have to switch to, and that never reach the chart. ### No trace behind a number Which device, which provider, which raw value. Without that, a reading cannot be trusted in a consultation or shown to an auditor. ### Every EHR connection is its own project Mapping, consent and access rules per site, all before the first value lands in the record. ### Patient data has to stay under your control Readings belong in your own cloud account and region, under your credentials, next to the record you already run. The solution ## Wearable data in your patients' app and in your clinical record One platform connects the devices your patients wear, feeds the app they already use, and writes the readings your clinicians need into the record. All of it is included. ### A patient app, ours or yours Patients connect their phone and wearables in the Connect App, joined with a link or a QR code, or inside your own app with our SDK for iOS, Android, Flutter and React Native. [Learn more](https://openwearables.io/platform/connect-app) ### One API across wearables Apple Health, Health Connect, Garmin, Oura, Withings and more arrive in one standard schema, with the source and the raw response kept behind every value. [Learn more](https://openwearables.io/platform/wearable-api) ### Into your EHR 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 view for clinicians Where the record cannot take writes yet, a clinician view runs beside it: trends, adherence and the readings since the last visit. ### Runs in your cloud, supported by us Your account, region and credentials, with upgrades and provider changes handled by the team behind Open Wearables under a clinical SLA. What it does ## From the patient's wearable to the chart, in three steps. 01 Connect ### Patients connect what they already wear In the Connect App or inside your own app, 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 the device and raw response kept. 03 Your record ### Written into the chart your clinicians open Readings and a weekly summary go into your EHR, with source and consent on every value. The outcome ## Clinicians open the chart and the data is already there. No second dashboard to open: the readings sit where the clinician already works. ### Readings in the patient's chart Sleep, heart rate and activity from the patient's own devices, filed next to notes, results and doses. A patient record with a visit note, a result and a dose change, and today's sleep and resting heart rate from Apple Health filed into it. ### Context before a consultation For a video call or a follow-up: what changed since the last visit, ready when the clinician opens the chart. 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. ### Patients monitored at home Hospital at home and post-discharge patients, with the device and sync time beside every value. A heart failure patient's readings, each with its device and sync time, beside fourteen days of weight rising 1.1 kg in three. Who it is for ## Organisations that run their own record. If patient data already lives in a system you control, this is how wearable data joins it. ### Hospital groups Clinicians asking for data between visits, and an EHR that should hold it next to everything else. ### Telemedicine platforms Remote consultations that are better with last week's readings in front of the doctor, inside your own platform. ### Clinic networks with their own record Several sites on one patient system, where a new data source has to fit the access rules you already run. ### Hospital at home services Patients monitored at home whose readings have to reach the ward's record, not a separate dashboard. ## 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 your patients' wearable data in your own EHR. Book a demo and we will walk you through it on a record like yours, from the patient's app to the chart your clinicians open. [Book a demo](https://openwearables.io/book?tier=clinical) FAQ ## Do you have more questions? ### 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. ### Does it work for remote patient monitoring? Yes. Patients connect the wearables they already own from home, and readings reach the record with the device and sync time beside every value: hospital at home, follow-up after discharge and chronic care. ### Can we connect it to our telehealth platform? Yes. Your platform adds wearable connections with our SDK, or patients use the Connect App, and the readings since the last visit are in the chart before the video consultation starts. ### 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. ### Our record cannot accept writes yet. Can we still start? Yes. A view runs next to the record and reads the patient context from it, and the data moves into the record once it can accept writes. ### Where does patient data live? In your own cloud account or the region you choose, under your credentials. When we work on your system, we do it under a data processing agreement you sign. ### How long does the first site take? Around three months from the first conversation to readings in the record, depending on what your EHR accepts. ### What does EHDS change for us? The European Health Data Space applies from 26 March 2027. From 26 March 2029, EHR systems handling patient summaries must meet its requirements, and the patient summary includes patient-provided data. It is a good reason to plan how wearable data enters your record.