Comparison
RPM vs CCM.
CMS permits billing both RPM and CCM for the same patient in the same calendar month. Combined programs can reach $280–$380+ per patient per month while delivering better clinical outcomes through both device monitoring and care coordination.
Side by Side
Feature comparison.
Analysis
Key differences.
Time cannot overlap between programs
Clinical staff time counted toward RPM (reviewing device data, responding to alerts) cannot also count toward CCM (care coordination, medication management). Time must be tracked separately for each program with distinct documentation.
Both require independent documentation
Each program must have its own documentation trail. RPM documentation covers device data review, clinical interventions, and patient communication about readings. CCM documentation covers care plan updates, medication reconciliation, and provider coordination.
Combined revenue significantly increases per-patient value
Stacking RPM (~$160–220) and CCM (~$62–130) can generate $280–380+ per patient per month. For a panel of 200 dual-enrolled patients, this represents $56,000–76,000+ in estimated monthly revenue.
Clinical synergy improves outcomes
RPM provides real-time physiologic data that informs CCM care coordination decisions. For example, a weight spike detected by RPM can trigger a CCM care coordination call with the cardiologist, creating a feedback loop that improves clinical outcomes.
Guidance
When to use each.
Stack RPM + CCM when
The patient has 2+ chronic conditions AND benefits from daily device monitoring. Ideal candidates include patients with diabetes + hypertension (glucose + BP monitoring with care coordination), heart failure + CKD (weight monitoring with nephrology coordination), or COPD + heart failure (SpO2 monitoring with multi-specialist coordination).
Do not stack when
The patient has a single, well-controlled chronic condition that only needs periodic check-ins. Stacking for patients without genuine clinical need increases documentation burden without proportional clinical benefit and may attract audit scrutiny.
Ideal patient profiles
The best candidates for combined RPM + CCM are patients with multiple chronic conditions, multiple medications, multiple providers, and a history of ER visits or hospitalizations. These patients benefit most from both continuous monitoring and proactive care coordination.
FAQ
Common questions.
How much can you earn with combined RPM + CCM?
Estimated combined revenue ranges from $280–380+ per patient per month when all applicable CPT codes are billed for both programs. This includes RPM device supply (99454), RPM clinical review (99457/99458), and CCM care coordination (99490/99439).
Can RPM and CCM clinical time overlap?
No. CMS requires that time counted toward RPM billing be distinct from time counted toward CCM billing. If a care manager spends 20 minutes reviewing device data (RPM) and 20 minutes on care coordination calls (CCM), each 20-minute block must be documented separately.
Do you need separate patient consent for each program?
Yes. Patients must provide informed consent for each program independently. The consent should explain the program purpose, services provided, cost-sharing responsibilities, and their right to opt out at any time.
What is the ideal patient for RPM + CCM?
The ideal dual-enrollment patient has conditions like diabetes + hypertension or heart failure + CKD, takes multiple medications, sees multiple specialists, and has a history of ER visits or hospitalizations. These patients get the most clinical benefit from both device monitoring and care coordination.
Does the same staff manage both programs?
Yes, the same clinical staff can manage both RPM and CCM for a patient. However, the time spent on each program must be tracked and documented separately. Many practices use a single care management platform that allows staff to log time against RPM or CCM activities distinctly.
More Comparisons
Also compare.
CCM vs RPM
Compare Chronic Care Management (CCM) and Remote Patient Monitoring (RPM): billing codes, patient eligibility, reimbursement, and when to use each.
CGM vs Glucose Meter
Compare continuous glucose monitors (CGMs) and traditional glucose meters for remote patient monitoring: data frequency, cost, patient experience, and clinical use cases.
Facility EHR vs Practice EHR
Compare facility EHRs (PointClickCare, ALIS) with practice EHRs (athenahealth, Epic) for RPM integration: workflows, data flow, and implementation considerations.
RPM vs RTM
Compare Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM): CPT codes, eligible conditions, device requirements, and when to use each program.
BHI vs CCM
Compare Behavioral Health Integration (BHI) and Chronic Care Management (CCM): eligibility, billing codes, clinical workflows, and when to combine both programs.
Cellular vs Bluetooth
Compare cellular and Bluetooth blood pressure monitors for remote patient monitoring: data reliability, patient experience, connectivity, and clinical outcomes.
Sensorless (Radar) vs Wearable Devices
Compare radar-based sensorless monitoring with traditional wearable RPM devices: patient experience, data types, compliance, and ideal care settings.