AZMedAppzSign inSet up a practice

WearSync

◦ in design

Patient wearables into the record — labelled, consented, thresholded.

Engagement · Full PHI · Every specialty

What WearSync does

Steps, heart rate, sleep, SpO2 and weight from HealthKit, Health Connect and band APIs, stored as patient-device-grade observations — visibly distinct from clinical-grade — with per-datatype consent and thresholds that flag the doctor’s inbox, not the patient’s anxiety.

What it reads

wearable APIsconsents

What it writes

observationsthreshold flags
Same patient record as every other app — nothing is copied into a silo. Data class: Full PHI.

What it does not do

It does not mix wearable readings with clinical measurements in trends without labelling both, and it syncs nothing without per-datatype consent.

Every app page carries this section. A listing with only benefits is an advertisement.

Questions clinics ask

What data does WearSync read and write?

WearSync reads wearable APIs, consents and writes observations, threshold flags. 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?

It does not mix wearable readings with clinical measurements in trends without labelling both, and it syncs nothing without per-datatype consent.

What happens to our data if we uninstall WearSync?

All clinical data stays in the record.

Is WearSync available today?

WearSync is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.

More engagement apps