What wearable remote patient monitoring actually is
Wearable remote patient monitoring is the practice of gathering a patient's vital signs, activity, and recovery trends from a personal device — typically a smartwatch, ring, chest strap, or connected cuff — instead of asking them to come in for every reading. The data is collected between visits, summarized for a clinician, and surfaced as an early signal rather than a single point-in-time measurement. Used well, wearable remote patient monitoring turns chronic-condition management into a continuous, asynchronous conversation rather than a quarterly one.
The 'patient-owned' part is what changed the calculus. Five years ago CPM meant shipping a vendor-locked cellular device to the patient and hoping they wore it. Today the watch the patient already wears, the ring they sleep in, and the cuff they use at home can all contribute — and the provider program no longer has to warehouse hardware, replace dead batteries on a fleet of hubs, or absorb a return rate when the patient gives up. VivoCore was built around that shift from day one: receive, normalize, and interpret whatever the patient already happens to be wearing.
The CMS billing codes that pay for wearable RPM
CMS reimburses wearable remote patient monitoring across four CPT codes that, billed together, pay most of the program cost for an enrolled patient. None of them require an in-person visit; all four require at least 16 days of readings in a 30-day window and a documented clinical reason for monitoring.
CPT 99453 covers the one-time set-up and patient education — the time a clinician spends walking the patient through the device, syncing it to the dashboard, and confirming the baseline. CPT 99454 is the per-month device-supply and data-transmission fee: it pays for the connected device itself and for the daily transmission of readings to the practice. CPT 99457 is the first 20 minutes per calendar month of clinical staff time reviewing the data, communicating the findings back to the patient, and recording the decisions made. CPT 99458 bills each additional 20 minutes — it appends to 99457, never replaces it.
The catch is that 99457 and 99458 require a "live, interactive" conversation each month — typically a phone call, video visit, or secure message thread — with the patient. A program that simply collects vitals without touching base fails the audit even if the patient is monitored perfectly. VivoCore's rules layer enforces both the 16-day threshold and the live-touch requirement automatically: a patient's month only closes once both gates are green, so the practice never bills for non-qualifying work.
What "supported devices" actually means
VivoCore is hardware-agnostic on purpose. The same rules engine that decides 'this reading is anomalous given the user's adaptive baseline' runs whether the reading came from an Apple Watch on a 67-year-old's wrist, an Oura ring on a 31-year-old's finger, a Polar H10 chest strap on a cardiac-rehab patient, or — when continuous blood pressure or SpO₂ is needed — an FDA-cleared cuff or pulse-oximeter provided by the program.
The list of supported connectors today is Apple Health (iPhone + Apple Watch + iPad), Google Fit, Oura, Garmin, Fitbit, and WHOOP. Wearables contribute different vital streams: Apple Watch and Garmin stream HR plus HRV plus sleep; Oura contributes HRV and body temperature trend; WHOOP focuses on recovery and strain; Fitbit and Google Fit surface steps plus activity. The rule on the program side is one device per vital stream is enough — a patient doesn't need a watch, a ring, and a strap to qualify for 99454.
What VPCore does not support — and this is a design choice, not a gap — are consumer devices whose only contribution is weight or sleep without any longitudinal vitals. A bathroom scale that uploads once a week should not be the centerpiece of an RPM program, and a sleep-only tracker without HRV cannot power an adaptive baseline. Programs that try to bill 99454 on those streams will undercut their audit-defensibility for the entire per-patient-per-month fee.
VivoCore's alert-to-appointment workflow
The point of collecting all that data is to act on it. VivoCore's daily summary is the patient's prompt to escalate, and the alert-to-appointment workflow is what happens after they say "yes".
The flow has five steps. First, the adaptive baseline — a per-patient, per-stream moving window that the system updates every day — detects a meaningful deviation. HRV drops 30% below the user's own trailing mean, or resting heart rate climbs 12 bpm for two days, or SpO₂ dips into a band the user has not been in before. Second, the anomaly is surfaced in that day's summary: the user sees the deviation, the prior week's trend for context, and one of three severity tiers. Third, the user is asked whether to escalate. VivoCore never auto-pages a doctor, a caregiver, or 911 — the user owns the decision. Fourth, if they escalate, the linked caregiver or primary care practice is notified through the channels they configured at signup (email, SMS, push). Fifth, the practice can use the built-in appointment-picker — fed by the same scheduling contract as the daily-summary auto-booking — to put a slot on the calendar before the end of the next clinic day.
Practices that adopt VivoCore's baseline-first workflow report fewer no-shows and a higher rate of same-week interventions, in part because the appointment that gets booked has a clinical anchor — the alert that triggered the book. The book-from-alert path is the rare place in RPM where the workflow is both auditable and humane: the patient is not handed a script, the practitioner is not handed a spreadsheet, and the slot on the calendar has a reason attached to it.
Where this is going in 2026
CMS finalized a small but meaningful adjustment to the 2026 physician fee schedule that increases the four RPM codes by roughly two to four percent and clarifies that 99457 and 99458 can be billed for time spent on asynchronous patient messaging within a continuous relationship — not just synchronous phone calls. That change matches the way RPM programs actually run in 2026, and it removes the "but we only messaged them" defensibility friction that has scared practices off the codes for the past two years.
VivoCore's rules layer is built to keep a program on the right side of that change. Every month a patient is enrolled, four auditable conditions — on ingested days, on set-up completeness, on the 20-minute touch, and on the additional-time justification — are tracked in the background, and any month that does not clear them is excluded from the claim automatically. Practices never bill for time they did not do, and they never miss a code they did.
If you have been waiting to take your RPM program live, the next quarter is a good time. Talk to a VivoCore operations partner about which tier (Starter, Growth, or Enterprise) fits the volume and technology footprint of your practice, and ask for a short read of the first three months of the program's compliance posture before you agree to anything. Wearable remote patient monitoring is finally a CMS-billable workflow that pays for itself when the rules are applied — and that is what the rest of the platform exists to do.