Different Service Purposes
CCM covers ongoing, non-device-dependent care coordination for patients with multiple chronic conditions. RPM covers device-based physiologic data collection and review. They address different parts of a patient's care and are billed under different code families.
Potential Workflow Overlap
Both involve monthly clinical staff or practitioner time and care-team review — the overlap risk is in how that time gets counted and documented, not in whether the services can coexist at all.
Documentation Separation
Time Considerations
If a single interaction genuinely serves both a CCM care-coordination purpose and an RPM treatment-management purpose, only one of the two codes may count that specific time — it can't be billed toward both thresholds.
Same-Month Billing Considerations
Only one practitioner can bill CCM per patient per month, and only one practitioner can bill remote monitoring per patient per 30-day period — these are separate one-provider rules, each applying to its own service family.
Current Medicare Rules
Per the CMS Telehealth & Remote Monitoring MLN Booklet, you may bill remote physiologic monitoring and RTM (not both together) concurrently with the following care-management services for the same patient, if you don't count time and effort twice: chronic care management, transitional care management, behavioral health integration, principal care management, and chronic pain management.
Example Operational Workflow
Illustrative example only. A patient with hypertension and diabetes is enrolled in both CCM (for overall chronic-condition care coordination) and RPM (for daily blood pressure and glucose trend monitoring). The care coordinator's monthly CCM time covers care-plan review and specialist coordination; a separate treatment-management encounter — a real-time call reviewing the RPM data trends — is logged and billed under RPM's treatment-management code instead. The two time logs are kept distinct in documentation.