Device readings, with the patient’s permission.
A patient connects their wearable or home device once. Their readings reach your clinic in a consistent form, source by source, in the console or through the enterprise API.
- The patient connects. Nothing is read until the patient grants it, and they can withdraw it.
- One shape per reading. Each reading keeps the device it came from.
- One API. The same signed enterprise API as every other order.
From a connection to a reading.
A device connection is the patient’s decision. TrueRoute records it, reads only what it allows, and stops when it is withdrawn.
- 1
Invite
Your clinic invites the patient to connect a device.
- 2
Permission
The patient signs in to their device account and grants access. The permission is recorded.
- 3
Readings
Readings arrive in one consistent form, each labelled with its source.
- 4
Your software
Your team sees them in the console, or your platform reads them through the API.
Said plainly.
Does TrueRoute sell or ship devices?
No. Patients connect devices they already own.
Can a patient stop sharing?
Yes. A patient can withdraw access at any time, and TrueRoute stops reading from that device.
Is device data a diagnosis?
No. Readings are information for your clinicians, who decide what they mean.
Bring device data into your care.
Tell us which devices your patients use and where you want the readings, and we will help set up the right access.