RPM Device Integration Playbook:
Tenovi, BodyTrace, Dexcom, iHealth, 100Plus & Rijuven Connected in One Workflow

Why Device Integration Is the Failure Point — Not the Device

Practices launching a remote physiologic monitoring program in 2026 typically buy the device first and assume the workflow follows. The reverse is true. The cellular blood pressure cuff, the connected scale, the continuous glucose monitor, the pulse oximeter, the spirometer — all six of these device families have matured. Transmission reliability is no longer the bottleneck.

The bottleneck is the integration layer that converts a device transmission into a billable record under CPT 99454, attributes that record to the right patient under the right ordering provider, captures clinician interaction time toward the CPT 99457 and 99458 per-calendar-month threshold, and writes the encounter to the EHR as an audit-defensible note — with all three artifacts (device-status log, attribution record, time log) preserved as structured data rather than free-text notes.

A typical 1,000-patient mixed-vendor RPM panel running on each manufacturer's own portal plus manual EHR documentation captures only 60 to 75 percent of billable 99454 device-supply months and 50 to 65 percent of billable 99457 / 99458 management time. The math compounds quickly across a year.

The Six Dominant RPM Device Platforms and What Each Surfaces

The integration challenge is not theoretical. Six platforms account for the vast majority of mixed-vendor practice deployments in 2026, and each one surfaces device data in a different shape, on a different cadence, with a different alert format and a different attribution scheme.

Tenovi

Hub-based cellular platform that supports a broad device catalog — blood pressure cuffs, weight scales, pulse oximeters, glucometers, peak flow meters, thermometers. The hub batches device readings and posts them to a single API. Strength: one integration covers many device types under one cellular SIM. Friction: hub provisioning errors are silent until the first 30-day billing cycle reveals zero transmissions.

BodyTrace

Cellular blood pressure cuffs and scales, transmission via embedded SIM (no hub, no Bluetooth pairing, no patient app). Strength: highest non-technical-patient adoption rate of the six platforms. Friction: device catalog is narrower — if the patient also needs SpO2 or peak flow, BodyTrace alone won't cover it.

Dexcom

Continuous glucose monitoring (G6, G7) with real-time interstitial glucose readings every five minutes. Strength: clinical depth no other platform matches for diabetes management. Friction: Dexcom Clarity (the provider portal) and the Dexcom data API are oriented around clinical interpretation, not the structured 99454 billing record — the practice has to derive the device-supply month and the 16-day-of-data attestation from the raw stream.

iHealth Unified Care

Cellular and Bluetooth devices across blood pressure, weight, glucose, pulse oximetry, thermometry. iHealth Unified Care offers an end-to-end RPM service tier (clinical staff included), but the device data and the embedded clinical workflow are tightly coupled. Friction: practices that want to retain clinical staffing in-house and only consume the device data are running against the grain of how the platform is sold.

100Plus

Cellular RPM platform with broad device coverage and an integrated clinical service offering. Strength: rapid deployment and the included virtual nurse layer. Friction: same as iHealth Unified Care — practices that want the device data fed into their own clinical-time workflow need an integration layer that extracts data from the platform without inheriting the bundled clinical workflow.

Rijuven

Multi-device RPM platform oriented around cardiology and chronic-condition monitoring with bundled device kits, mobile patient app, and a clinician portal. Strength: handles the cardiology stack well. Friction: as with the integrated platforms above, the clinical workflow assumption is built in — practices need an integration pattern that turns Rijuven device events into structured billing records without forcing the clinical team into the Rijuven UI.

The 2026 RPM Reimbursement Landscape Practices Are Integrating Against

Under the CY 2026 Medicare Physician Fee Schedule national average, the four RPM CPT codes pay as follows (national averages; each MAC and locality varies):

• CPT 99453 — Initial setup and patient education on the device, billed once per episode of care — approximately $19.36.
• CPT 99454 — Device supply with daily recordings, requires a minimum of 16 days of data within a 30-day period — approximately $43.02 per 30-day period.
• CPT 99457 — First 20 minutes of clinical staff or physician interactive communication time per calendar month — approximately $46.13.
• CPT 99458 — Each additional 20 minutes of clinical interactive communication time per calendar month — approximately $37.21.

Stacked monthly across a continuously managed patient with two 99458 increments captured per month, this generates roughly $1,468 of RPM revenue per patient per year — before any layered CCM, PCM, BHI, or APCM stacking.

The Three Artifacts That Make 99454 Audit-Defensible

The 99454 audit defense in 2026 requires three artifacts per 30-day billing period, per patient. None of them can be reconstructed from a free-text EHR note after the fact. All three need to be queryable structured data the moment a CMS Additional Documentation Request (ADR) lands.

1. The Device-Status Log

Proves the patient transmitted on at least 16 distinct calendar days within the 30-day period. The log needs to record device serial number, transmission timestamp, calendar day attribution, and reading payload. A vendor portal that shows "device active" without a queryable per-day transmission record will not survive an ADR cycle.

2. The Device-Attribution Record

Proves the readings came from a device that meets the FDA medical-device definition embedded in the 99454 code descriptor. Consumer wellness devices (smartwatches, retail fitness scales, off-brand BP cuffs) do not qualify. The integration layer needs to gate the 99454 claim line on the device class so a patient-procured non-qualifying device cannot accidentally generate a billable record.

3. The Patient-Attribution Record

Proves the readings came from the patient under the order — not a household member, not a co-resident with the same connected device. Most vendor platforms support this via account binding at activation; the integration layer needs to honor that binding and reject orphaned transmissions.

The 20-Minute Rule Across Multi-Vendor Panels

CPT 99457's 20-minute threshold is per patient per calendar month — not per device, not per vendor portal. This is where the most expensive practical mistake happens.

A patient on a Tenovi blood pressure cuff, a BodyTrace scale, and a Dexcom CGM has three vendor portals. If the practice staffs RN review through each portal independently, the same five minutes of clinician time on the same patient on the same day gets logged three times across three systems. That triple-counted time then either rolls up incorrectly into 99457 / 99458 (creating an audit clawback) or stays siloed and never crosses the 20-minute threshold (creating revenue leakage). Both failure modes are common.

The audit-defensible pattern is a single time-tracking record keyed to the patient per calendar month, with each touchpoint logged with start time, end time, modality (synchronous call, asynchronous message, chart review), and clinician identity. A deterministic rollup fires the 99457 claim line at exactly 20 cumulative minutes within a calendar month and the 99458 claim line at each additional 20-minute increment, capped at the CMS-allowed maximum (typically two 99458 units per month, but verify against your MAC's current LCD).

The Reference Architecture for One Workflow Across Six Vendors

A defensible cross-vendor RPM workflow built in 2026 has six layers. None of them require ripping out the EHR. None of them require ripping out the device vendor. The layers sit in between and turn six different vendor data shapes into one structured billing-and-clinical-time record per patient per month.

Layer 1 — Vendor Adapters

One adapter per vendor (Tenovi, BodyTrace, Dexcom, iHealth, 100Plus, Rijuven), each pulling data on the vendor's native cadence and normalizing into a single internal device-reading schema. The adapter layer absorbs vendor API churn so the rest of the stack stays stable.

Layer 2 — Patient and Device Master

One record per patient that maps the patient's MRN in the EHR to the device serial numbers active for that patient across all six vendors. This is the layer that prevents orphaned transmissions and supports the device-attribution audit artifact.

Layer 3 — Daily Aggregator and 16-Day Counter

A nightly job that walks each patient's transmissions for the rolling 30-day window, counts distinct calendar days with at least one valid reading, and surfaces patients who are at risk of missing the 16-day threshold — in time to intervene with an SMS reminder or a coaching call before the billing window closes.

Layer 4 — Clinical Time Tracker

A single per-patient per-month time log accessible from inside the clinician's existing workflow (EHR sidebar, Microsoft Teams plug-in, or simple browser overlay). Every touchpoint — synchronous call, asynchronous secure message, chart review, alert triage — logs start time, stop time, modality, and clinician identity. The cumulative total drives the 99457 and 99458 claim-line generation.

Layer 5 — EHR Write-Back

For each billing event (99453 setup, 99454 device-supply month, 99457 first 20 minutes, 99458 each additional 20 minutes), a structured note is written back to the EHR with the supporting data attached — not a free-text "RPM services rendered" note. The note is what survives an ADR cycle.

Layer 6 — Claim Line Generator

A monthly job that walks the eligible billing events per patient, applies the CMS-allowed unit caps, validates documentation completeness (device-status log present, time log present, encounter note present), and queues claim lines for the billing system. Anything that fails validation is queued for human review — not silently suppressed and not accidentally billed.

Where APCM (G0557 / G0558 / G0559) Changes the Math

CMS introduced the Advanced Primary Care Management (APCM) bundled codes effective January 2025: G0557 (Level 1, no time threshold, approximately $53.91), G0558 (Level 2, multiple chronic conditions, approximately $72.33), and G0559 (Level 3, multiple chronic conditions plus QMB-eligible, approximately $106.07). APCM does not require the 20-minute time threshold that 99490 CCM does, which means the documentation burden is materially lower per patient.

For practices running both APCM and RPM on the same patient panel, the integration layer needs to know which patients are billed under G0557 / G0558 / G0559 versus 99490 / 99439 in any given month, and route documentation accordingly. APCM stacking with RPM is allowed under the 2026 rules, but the documentation logic differs — and the two cannot be billed for the same patient under both APCM and CCM 99490 in the same month. The 20-minute rule playbook covers the time-tracking pattern when 99490 is the chosen code; APCM under G0557 sidesteps it but introduces a different attestation surface.

What a 6-to-10 Week Implementation Looks Like

For a practice currently running RPM on two or three vendor portals plus manual EHR documentation, the integration layer build typically lands in six to ten weeks:

• Weeks 1–2: Workflow audit. Pull 90 days of historical RPM activity. Quantify the gap between transmissions captured in vendor portals and 99454 / 99457 / 99458 actually billed. Identify the highest-leverage failure modes for this specific practice.
• Weeks 2–5: Build vendor adapters for the in-use platforms (Tenovi, BodyTrace, Dexcom, iHealth, 100Plus, Rijuven — whatever subset the practice runs). Stand up the patient/device master and the daily aggregator with the 16-day counter.
• Weeks 4–7: Deploy the clinical time tracker into the existing clinical workflow. Train clinical staff on the single-source-of-truth time-logging pattern. Run in parallel with the existing process for two billing cycles.
• Weeks 6–9: Stand up the EHR write-back with structured note templates per code family (99453, 99454, 99457, 99458, plus stacked 99490 / 99439 / G0557 as applicable). Validate against an actual ADR-style document pull to confirm completeness.
• Weeks 8–10: Cut over the claim-line generator. Retire the manual billing reconciliation spreadsheet. Run the first full automated billing cycle.

EHR stays the system of record. Vendor portals stay live for clinical workflows that depend on them. The integration layer sits in between and produces the structured billing artifacts and the audit-defensible documentation that neither the EHR nor the vendor portals were built to produce on their own.

Cross-Specialty Considerations: Cardiology, Pulmonology, Endocrinology, Primary Care

The reference architecture above is identical across specialties because the CPT code family is identical. What changes is the device mix, the layered code stack, and the clinical-alert thresholds the integration layer needs to honor.

Cardiology typically runs Tenovi or BodyTrace cellular cuffs, layered with implantable cardiac device monitoring under CPT 93297 / 93298 for pacemakers, ICDs, CRT-D, and loop recorders. The integration layer needs to bridge alert feeds from Medtronic CareLink, Abbott Merlin, and Boston Scientific Latitude into the same per-patient per-month time log so cardiac-device alert triage time counts toward the 99457 / 99458 threshold without double-counting against 93297 / 93298.

Pulmonology runs Tenovi or iHealth pulse oximeters and peak-flow meters, often layered with RTM under CPT 98975 (initial setup, $19.36), 98976 (respiratory device supply, $43.02), 98980 (treatment management 20 min, $46.13), and 98981 (additional 20 min, $37.21). RPM and RTM cannot both be billed for the same monitoring episode; the integration layer enforces the choice at the patient-month level.

Endocrinology is Dexcom-heavy by definition. The integration challenge is bridging Dexcom Clarity's clinical interpretation orientation with the structured 99454 device-supply record. The integration layer derives the 30-day device-supply attestation from the raw Dexcom stream and writes it back to the EHR as the structured 99454 documentation artifact.

Primary care typically runs the broadest device mix and the heaviest CCM stacking. RPM under 99457 / 99458 layers with CCM under 99490 ($66.30) plus 99439 ($47.40) for additional time, or with APCM under G0557 / G0558 / G0559. The integration layer enforces the per-patient per-month code-family lock that prevents the duplicate-billing failure mode.