EngagementLive · in the productSettings

WearSync

Wearable readings labelled as patient-reported, never clinical — inside Remote Monitoring.

Installs with RPMConsole, whose screen it works on

Get WearSync Open the appAvailable nowHow pricing works →

What it is

A view inside RPMConsole (Remote Monitoring) — installing it installs RPMConsole. The point was never the sync — it was the label: every monitoring reading carries how it was taken, and the four kinds are kept apart by the database rather than by a convention. A reading recorded as clinically measured must name a device the hospital registered. A reading arriving through the patient’s own link can only ever say “I measured this” or “my watch says”, cannot name a device at all, and if it is from a wearable must say which watch or app. That label is copied onto any alert the reading raises. What is NOT built is the sync itself: there is no HealthKit or Health Connect connector — readings arrive through the Send a reading card on the patient’s portal link.

Who uses it: Built for: Every specialty
Reads: The patient portal link, RPMConsole’s thresholds
Writes: Monitoring readings, with the class they were taken under
Never: There is no HealthKit, Health Connect or band-API connector in this product, and no background sync: nothing is pulled off a device, so nothing is pulled off it without consent either.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record.

How it works

The patient sends a reading from their portalSend a reading lets them pick the measurement, type what their meter or watch shows, and mark it I measured this or My watch or app says — the second needs which watch or app named before Send to my clinic will run.
It arrives labelled, never as a clinical measurementEvery reading carries how it was taken — measured — hospital device, home meter, patient reported or wearable — patient reported — and that label, not the number alone, travels onto any alert it raises.
Read the label in the queueThe badge on every reading and every alert row on Remote Monitoring names its class, so a step count and a hospital vital are never read as the same kind of fact.
Nothing syncs on its ownThere is no HealthKit or Health Connect connector behind this — Send a reading on the portal is the only door a wearable number comes through.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

There is no HealthKit, Health Connect or band-API connector in this product, and no background sync: nothing is pulled off a device, so nothing is pulled off it without consent either.

What exists is the labelling and the refusals around it — a patient-sent reading cannot claim one of the hospital’s devices, a wearable reading cannot be stored without naming its source, and none of it is written to the chart as a measured vital.

AI in WearSync

AskQuestions about what is on screen — “What needs attention in WearSync today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

WearSync — Remote Monitoring — Keep watch and phone readings labelled as the patient’s, not clinical — 01Remote Monitoring — Keep watch and phone readings labelled as the patient’s, not clinicalCaptured from the running demo clinic

01Remote Monitoring — Keep watch and phone readings labelled as the patient’s, not clinicalCaptured from the running demo clinic

1 of 1

Questions clinics ask

What does WearSync do?

Wearable readings labelled as patient-reported, never clinical — inside Remote Monitoring. A view inside RPMConsole (Remote Monitoring) — installing it installs RPMConsole. The point was never the sync — it was the label: every monitoring reading carries how it was taken, and the four kinds are kept apart by the database rather than by a convention. A reading recorded as clinically measured must name a device the hospital registered. A reading arriving through the patient’s own link can only ever say “I measured this” or “my watch says”, cannot name a device at all, and if it is from a wearable must say which watch or app. That label is copied onto any alert the reading raises. What is NOT built is the sync itself: there is no HealthKit or Health Connect connector — readings arrive through the Send a reading card on the patient’s portal link.

What data does WearSync read and write?

WearSync reads the patient portal link, RPMConsole’s thresholds and writes monitoring readings, with the class they were taken under. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does WearSync deliberately not do?

There is no HealthKit, Health Connect or band-API connector in this product, and no background sync: nothing is pulled off a device, so nothing is pulled off it without consent either. What exists is the labelling and the refusals around it — a patient-sent reading cannot claim one of the hospital’s devices, a wearable reading cannot be stored without naming its source, and none of it is written to the chart as a measured vital.

What happens to our data if we uninstall WearSync?

All clinical data stays in the record.

Is WearSync available today?

Yes — WearSync is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see WearSync running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Engagement

All 102 →