| RPM | CCM | |
|---|---|---|
| Purpose | Device-based physiologic data collection and review | Non-device care coordination for multiple chronic conditions |
| Patient population | Acute or chronic condition requiring monitoring, established patient | 2+ chronic conditions, 12+ months, significant risk |
| Technology/device requirement | FDA-defined connected medical device required | Certified EHR, no monitoring device required |
| Time requirements | 99457 (20 min) + 99458 add-on; separate device-supply day requirement | 99490/99439 or 99487/99489 time thresholds |
| Data collection | Electronic, device-transmitted physiologic data | No device data; care-plan and coordination documentation |
| Billing structure | One-time setup + recurring device supply + treatment management | Recurring time-based codes only |
| Can services coexist? | Yes, if time/effort isn't double-counted | Yes, if time/effort isn't double-counted |
Purpose
RPM focuses on collecting and reviewing a patient's physiologic data from a connected device. CCM focuses on ongoing, non-device-dependent care coordination for patients with multiple chronic conditions.
Patient Population
RPM currently covers acute or chronic conditions requiring monitoring, for an established patient. CCM requires two or more chronic conditions expected to last at least 12 months with significant risk of decline.
Technology/Device Requirement
RPM requires an FDA-defined connected medical device that electronically collects and transmits data. CCM has no device requirement — it requires certified EHR use for structured health information, but not a connected monitoring device.
Care-Management Activities
RPM's activities center on device setup, data collection, and reviewing that data for treatment management. CCM's activities center on care planning, coordination across providers, and managing transitions of care.
Time Requirements
Both have time-based treatment/care-management codes (RPM: 99457/99458; CCM: 99490/99439 or 99487/99489), but RPM's device-supply code is based on a data-collection window (days), while CCM has no equivalent device-day requirement.
Data Collection
RPM requires electronic, device-transmitted physiologic data. CCM doesn't require ongoing device data at all — its documentation centers on the care plan and coordination activities.
Patient Communication
RPM's treatment-management billing requires at least one real-time interactive communication per month. CCM similarly expects care-team accessibility, but its billing doesn't hinge on a specific communication event the way RPM's does.
Billing Structure
Both use monthly, largely time-based codes, but RPM adds a distinct one-time setup code and a recurring device-supply code that CCM has no equivalent for.
Documentation
RPM documentation centers on device data, the collection window, and interactive communication. CCM documentation centers on the care plan, coordination activities, and monthly qualifying time.
Typical Workflow
RPM workflow: patient identified → device setup → ongoing data collection → clinical review → treatment management. CCM workflow: eligibility and consent → initiating visit → care plan → ongoing monthly coordination.
Can Services Coexist?
Yes — current CMS guidance allows billing RPM and CCM concurrently for the same patient, as long as time and effort spent on one isn't also counted toward the other. See our CCM and RPM Together guide for a fuller breakdown.
Use Cases
RPM fits patients whose condition benefits from ongoing physiologic data (e.g., blood pressure, weight, oxygen saturation trends). CCM fits patients whose primary need is coordinated care planning across multiple chronic conditions. Many patients are reasonable candidates for both, run as separate, properly-documented programs.