Wearable API for Remote Patient Monitoring

Remote monitoring programmes increasingly rely on devices the patient already owns rather than issued hardware. That means a mix of Withings cuffs and scales, Fitbit and Garmin watches, Dexcom sensors and Apple Health on the phone — and a clinical team that needs one view.

WearLink normalises the physiological families that matter clinically — heart rate, blood pressure, blood glucose, respiratory rate, body temperature, body composition — into one schema with canonical units, and records every privileged access in an append-only audit log you can export.

It is important to be clear about what WearLink is not: it is not a medical device, it holds no SOC 2 or HIPAA attestation today, and consumer wearables are not validated for diagnosis. The security page states exactly what controls exist so your compliance review can be done on facts.

What usually goes wrong

How WearLink handles it

• Canonical clinical units — mg/dL for glucose with mmol/L preserved, mmHg for blood pressure, degrees Celsius for temperature, breaths per minute for respiratory rate.
• Append-only audit log with NDJSON export — Every privileged action is recorded and exportable in one request for questionnaires and internal review.
• Revisions delivered as events — When a provider restates a record, WearLink re-emits the corrected object so downstream views never hold a silently stale value.
• End-user export and deletion — Per-user data export and hard deletion endpoints support subject-access and erasure requests.