Built into RPMConsole: wearable readings labelled as patient-reported, never clinical.
Engagement · Full PHI · Every specialtyThe point of this was never the sync — it was the label, and a label is a column, not an app. So it shipped inside RPMConsole: 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, so the nurse working the queue is never shown a step count under a heading that reads like a vital. What is NOT built is the sync itself: there is no HealthKit or Health Connect connector here — readings arrive through the Send a reading card on the patient’s portal link, where the patient picks one of the programme’s own measurements and says whether they measured it or their watch did, and a watch reaches the record the way any other self-report does. Integrators can post to the same door.
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.
Every app page carries this section. A listing with only benefits is an advertisement.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.
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.
All clinical data stays in the record.
WearSync is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.
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.