Can RPM stack with CCM or APCM?
Yes — that's the intended design, and it's where per-patient economics get compelling. Time must be independently documented, which our ledger enforces automatically.
SanseraCCM360™ · Remote Physiologic Monitoring
Vitals watched every day. Problems caught before the ER visit.
Remote Physiologic Monitoring puts connected devices — blood pressure cuffs, glucometers, scales, pulse oximeters — in your patients' homes and pays your practice monthly to monitor what they transmit. The clinical case is proven. The operational case fails on two things: patients who stop taking readings, and staff drowning in alerts. Sansera's AI fixes both.
The Program
What Remote Physiologic Monitoring actually requires
RPM pays for physiologic data — blood pressure, glucose, weight, oxygen saturation — that is automatically collected and transmitted by a connected medical device. Manual patient entry doesn't qualify (that's RTM's territory). It's ordered by a physician or QHP for an established patient, and it stacks on top of CCM, PCM, or APCM with independently documented time.
The RPM code ladder
| Code | What it pays for | Requirement | ~2025 rate* |
|---|---|---|---|
| 99453 | Setup & patient education | Once per device episode | ~$19 |
| 99454 | Device supply & transmission | 16+ days of readings per 30 days | ~$43/mo |
| 99457 | Treatment management | 20 min + a live interactive contact | ~$48/mo |
| 99458 | Add-on to 99457 | each +20 min | ~$39 |
*National non-facility averages; localized in-platform.
The two rules that sink RPM programs: the 16-day rule (fewer than 16 reading-days in the 30-day period means the device month doesn't bill) and the interactive-communication requirement on 99457 (the 20 minutes must include real, live contact — not just chart review).
How Sansera Runs It
Monitoring that patients stick with — and staff can keep up with
Order to first reading in under a week.
Provider orders in the EHR; we handle device selection, shipment, and AI voice onboarding in the patient's language — a real walkthrough, not a pamphlet — and verify the first successful transmission.
Personalized baselines, not dumb thresholds.
Per-patient time-series models learn what's normal for this patient and alert on clinically meaningful deviation. A deterministic floor guarantees critical values always escalate immediately. Result: your nurses see the readings that matter, not three hundred that don't.
The 16-day rule, defended in advance.
Our adherence model predicts by day 10 which patients will miss the threshold — then the engagement agent nudges, troubleshoots the device, and schedules a call before the month fails. Programs run this way keep 80%+ of device-months billable.
Management time that documents itself.
Monitoring reviews, patient calls, and adjustments flow into the same automatic time ledger as every other program — with the interactive-contact evidence for 99457 captured from the telephony log, not from memory.
A monthly brief your clinicians actually read.
The AI drafts a per-patient trend summary — what changed, what matters, what to consider — attached to the management workflow for clinician review. Drafted for humans, never auto-filed.
The Math
What RPM adds to the stack
$300K–$400K/year
Ongoing RPM typically runs ~$100–140 per patient per month (device supply + management + partial add-on) — on top of the patient's base care-management program. Three hundred RPM patients at 80% capture is roughly $300K–$400K/year of stacked revenue, with the clinical upside of catching decompensation at home instead of in the ED.
FAQ
Remote Physiologic Monitoring questions
Can we bill RPM and RTM for the same patient?
Not by the same practitioner in the same month. Different practitioners — say, your PCP on RPM and a physical therapist on RTM — can run both with independent devices, data, and time. The platform validates practitioner separation before either claim releases.
What if a patient takes two readings a day?
The 16-day rule counts days with readings, not reading counts. Our tracker computes it from raw device timestamps — the standard an auditor will use.
Do patients need Wi-Fi or a smartphone?
No. We prioritize cellular-connected devices precisely because safety-net populations can't be assumed to have home broadband.
SanseraCCM360™
One platform. Five programs. One right answer per patient.
CCM, PCM, and APCM are mutually exclusive — every patient, every month, there's one compliant program that pays best, and it changes as the patient changes. RPM and RTM stack on top with rules of their own. The Smart Billing Engine evaluates all of it monthly: eligibility, expected revenue, delivery requirements, and every compliance gate — deterministic rules, never AI guesswork, with an evidence bundle behind every claim.
Start with a working session, not a sales pitch.
Thirty minutes. Bring your panel size and payer mix; we'll show you what your care-management program is actually worth, and what it takes to capture it without hiring anyone.
HIPAA
SOC 2 Type II audit in progress
NIST AI RMF
Full audit trail on every AI action
Human override on every autonomous decision