CPT Code Compliance for Remote Monitoring: 2026 Playbook

Key Takeaways

• Cardiology and EP practices face heightened payer audits in 2026 as Medicare paid $536 million for RPM in 2024 and the HHS OIG classified remote monitoring as a high-risk compliance area.
• The 2026 CPT code set introduces 99445 and 99470, creating new billing pathways that require shorter data-day and time thresholds while maintaining strict documentation standards.
• Compliant RPM billing demands documented patient consent, FDA-compliant devices, interactive communication logs, medical necessity, and adherence to the single-billing-provider rule.
• CIED-specific codes follow 90-day or 30-day cycles; device-type mismatches and unbilled technical components are leading causes of denials that integrated platforms can prevent.
• Rhythm360 consolidates CIED and HF/HTN data from all major manufacturers into auditable documentation that supports CPT code compliance and reduces audit exposure.

See how Rhythm360 automates compliant CPT capture

Executive Overview: The 2026 Remote Monitoring Code Set

Remote patient monitoring (RPM) refers to the collection and transmission of physiologic data, such as blood pressure, weight, glucose, and heart rate, from a patient's home to the care team using an FDA-defined connected device. Remote physiologic monitoring and remote therapeutic monitoring (RTM) are distinct services: RPM monitors physiologic data, while RTM monitors non-physiologic therapeutic data such as medication adherence. The 2026 code structure matters because the CY 2026 Physician Fee Schedule final rule (CMS-1832-F), effective January 1, 2026, added two new RPM codes, 99445 and 99470, that operationalize shorter data-day and time thresholds, creating new billing pathways and new compliance obligations simultaneously. The table below maps each core RPM code to its 2026 requirement so practices can see where the new thresholds diverge from the established ones.

Any changes proposed for 2027 remain proposed only and are not yet in effect. Practices should verify current payer-specific policies before submitting claims, as Medicare, Medicare Advantage, Medicaid, and commercial plans may not process RPM identically.

Schedule a demo to see compliant CPT code capture in action

The Remote Monitoring Billing Ecosystem: From Fragmented Portals to Integrated Compliance

The remote monitoring billing ecosystem involves providers, device manufacturers, EHRs, billing teams, and patients, each generating data that staff must capture, reconcile, and document before a claim is submitted. Practices managing CIEDs from multiple manufacturers face a distinct compliance burden because staff must log into separate, non-interoperable manufacturer portals to retrieve device data. That fragmentation creates documentation gaps that translate directly into audit exposure.

The shift toward integrated platforms addresses this fragmentation by consolidating billable events and generating auditable documentation at the point of care rather than reconstructing it at billing time. An audit-ready practice produces defensible documentation as a byproduct of its workflow, not in a scramble after an auditor arrives.

Rhythm360 is a vendor-neutral, HIPAA-compliant platform that consolidates CIED and HF/HTN data from all major device manufacturers, including Medtronic, Boston Scientific, Abbott, and Biotronik, into a single source of truth. That consolidation makes auditable documentation possible because the platform automates data ingestion, report generation, and billing documentation, and integrates bi-directionally with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7. Other platforms in the cardiac remote monitoring space include Murj, Implicity, Rhythm Management Group, and Octagos. Whatever solution a practice evaluates, it should enforce device-specific cycle tracking, documentation completeness, and no-double-counting rules at the point of care.

Those rules only hold up if the underlying documentation does. The next section explains what a compliant RPM record must contain.

Documentation Requirements for Remote Patient Monitoring (RPM)

Compliant RPM billing requires that every claim be supported by documentation addressing each of the following elements before submission. At audit, missing documentation is treated the same as services not rendered.

1. Established Patient Relationship and Consent. RPM generally requires an established patient relationship, meaning the patient must already be under the care of the billing practitioner or practice before RPM services are billed. Patient consent may be verbal, but staff must document it in the medical record along with justification for the use of RPM services. Reviewers look for the date consent was obtained, what the patient was told, the patient's responsibility to use the device, potential cost-sharing, and confirmation that the patient agreed to the service.
2. Device Supply and Transmission Requirements. The FCSO RPM documentation checklist requires documentation showing the remote monitoring device is both FDA compliant and HIPAA compliant, that data were automatically transmitted rather than manually uploaded, and that the required data-day threshold was met for the specific code billed. Manual logs alone are weak support for RPM billing, so billing teams should rely on device or platform logs showing actual data transmission.
3. Interactive Communication and Time Documentation. CMS defined interactive communication for RPM codes as involving at a minimum real-time synchronous, two-way audio interaction that is capable of being enhanced with video or other kinds of data transmission between the patient or caregiver and clinical staff, a physician, or another qualified healthcare professional. Recovery Audit Contractors reviewing 99457 and 99458 claims look for time logs that document when the interactive conversation happened and what was discussed, not just a running minute total.
4. Medical Necessity Documentation. The record should clearly support why the patient needs remote monitoring, such as uncontrolled hypertension with a recent medication adjustment that requires blood pressure monitoring to evaluate treatment response.
5. Single Billing Provider Rule. Only one provider may bill for the RPM device supply per 30-day period. Documentation must confirm that only one practitioner is billing RPM for the patient during the reporting period to prevent duplicate claims.

Cardiac and CIED-Specific Compliance: High-Value Codes with High Audit Risk

Cardiac device remote monitoring codes follow device-specific billing cycles that differ from the general RPM code stack. Device-type mismatch and unbilled technical components are among the most common denial causes in this category.

Pacemakers and ICDs follow a 90-day billing cycle:

• 93294 is the pacemaker professional code
• 93295 is the ICD professional code
• 93296 is the pacemaker/ICD technical code

Physiologic monitors and loop recorders follow a 30-day billing cycle:

• 93297 is the device-specific code for an implantable cardiovascular physiologic monitor, such as CardioMEMS
• 93298 is the device-specific code for a subcutaneous cardiac rhythm monitor or implantable loop recorder

Because 93297 and 93298 are device-specific codes rather than a professional and technical pair, each is billable once per 30 days. Practices can bill each code three ways: global, with the -26 professional component modifier, or with the -TC technical component modifier. Applying either code to the wrong device type creates a device-type mismatch denial. Failing to bill the technical component when the practice performs that service creates an unbilled technical component denial.

Rhythm360 automatically tracks device-specific CPT pairings and both billing cycles. That tracking prevents device-type mismatch denials and catches unbilled technical components before the claim goes out. For HF/HTN programs, the general RPM codes 99453, 99454, and 99457 apply to heart failure and hypertension patients using connected physiologic monitoring devices, and the same documentation requirements described above govern those claims.

See how Rhythm360 tracks device-specific CPT cycles automatically

Concurrent Billing Rules for RPM, CCM, and TCM

CMS permits RPM to be billed concurrently with Chronic Care Management (CCM) and Transitional Care Management (TCM) when all requirements for each service are independently met. Concurrent billing of RPM alongside CCM or TCM is one of the most under-covered and highest-risk areas in remote monitoring billing. The rule targets double-counting: the same time or effort cannot be counted toward more than one billed service.

The decision framework for concurrent billing rests on three principles:

1. Independent Eligibility. A patient's enrollment in RPM or CCM does not automatically mean a billable service exists each month, so if the documentation does not satisfy the requirements of the code being considered, the code should not be reported.
2. No Shared Time. The recommended internal rule is "One Minute → One Time-Based Service." Documentation should separately itemize time by date, duration, staff member, and activity, clearly separating time counted toward RPM from time counted toward CCM or TCM.
3. Attribution at the Time of Service. Work should be labeled at the time it occurs, for example recording "8/4 CCM care coordination 8 min" and "8/9 RPM treatment management 12 min," rather than asking billing staff to reconstruct service attribution at the end of the month.

The same minute of clinical staff time cannot count toward two care management programs, so for an interaction involving both RPM and CCM, practices must document distinct qualifying activities and allocate actual time without duplication. Rhythm360's automated CPT code capture and auditable documentation help practices attribute billable events correctly and maintain the separation required to defend concurrent claims at audit.

Common Audit-Failure Patterns and How to Avoid Them

The following patterns are the most common reasons remote monitoring claims fail review. Each represents a documentation or workflow failure that Rhythm360's automated report generation and billing documentation are designed to prevent.

• Missing or Incomplete Consent Documentation. Missing or vague consent documentation is consistently cited as a top reason RPM claims fail audit review, regardless of whether the clinical service itself was appropriate. Compliant documentation should include the date consent was obtained, what the patient was informed of, and confirmation the patient agreed to the service.
• Undocumented Interactive Communication. Documenting chart review without a real live conversation can fail 99457-style requirements, and text messaging alone does not satisfy the interactive communication requirement. Compliant documentation should include the date, duration, and content of the real-time two-way audio interaction.
• Time Not Tracked or Not Attributable. A defensible RPM record should allow the practice or a reviewer to trace billed time back to specific dates, staff, and activities, because a single unsupported monthly total may not provide enough detail to substantiate the billed service.
• Device-Type Mismatch. Reviewers compare the billed code against the actual device. Compliant documentation should confirm the device type and that the correct code was selected, particularly for the cardiac-specific codes 93294–93298.
• Unbilled Technical Components. Reviewers look for whether the technical component was appropriately billed for CIED codes. Compliant documentation should confirm whether the service was billed global, with -26, or with -TC.
• Duplicate Billing Across Overlapping Service Periods. Concurrent billing overlap between RPM and another care management program for the same time period is a recurring cause of RPM recoupment. Compliant documentation should clearly separate time attributed to RPM from time attributed to CCM or TCM.
• Missing Medical Necessity Documentation. Lack of medical necessity documentation is one of the most common RPM billing mistakes leading to denials and audits, and claims are denied when RPM is billed without a documented link between monitoring and the patient's diagnosis or treatment plan.

Most of those failures trace back to code selection. Two of the most common mix-ups involve RTM and a handful of legacy codes that look like RPM but are unrelated.

RPM vs. RTM and Codes Commonly Confused with Remote Monitoring

RPM and RTM should not be billed together for the same patient during the same billing period, because RPM monitors physiologic data, such as blood pressure, oxygen saturation, blood glucose, weight, and heart rate, while RTM monitors therapeutic or non-physiologic data such as musculoskeletal status, medication adherence, and treatment response. Medicare coverage and payment rules for RTM differ from RPM, so practices should verify payer-specific policies before billing either service.

Two codes are frequently confused with the RPM framework:

• CPT 99091 is a physician or qualified health care professional code for the collection and interpretation of physiologic data stored or transmitted digitally. It is a legacy RPM-adjacent code and functions as a distinct service rather than an interchangeable part of the 2026 RPM framework.
• CPT 99396 and 99397 are preventive evaluation and management visit codes unrelated to remote monitoring and should not be conflated with RPM billing.

Readiness and Implementation Considerations for Compliant Remote Monitoring Programs

Practices assessing organizational readiness for a compliant remote monitoring program should evaluate the following areas as a connected sequence rather than isolated tasks.

• Stakeholder Alignment. Clinical, billing, and compliance teams need to agree on documentation requirements and workflow ownership before the first claim is submitted, because without that agreement each team documents to a different standard and the record fragments.
• Workflow Maturity. With ownership settled, assess whether current processes for data retrieval, documentation, and claim submission can actually produce that record. Structuring RPM workflow as a defined sequence, Enrollment → Consent → Setup → Data → Review → Communication → Escalation → Documentation → Billing Review, with each step having a designated owner, ensures the practice can answer who was responsible, what happened, and where it is documented.
• Data Quality and Integration. Evaluate whether device data flows automatically into the EHR and whether documentation is captured at the point of care rather than reconstructed at billing time, because real-time capture reduces gaps.
• Consent and Audit Processes. Confirm consent workflows are documented and audit trails are retrievable for every patient in the program so staff can respond quickly to payer requests.
• Staff Training. Ensure clinical and billing staff understand what each code requires and how to document it, including the device-specific cycle distinctions for CIED codes, so documentation supports every billed claim.

A phased rollout that begins with a defined patient cohort, validates documentation workflows, and then expands incrementally reduces compliance risk during program growth. Rhythm360's streamlined implementation, including EHR integration, typically takes only a few days to a few weeks and integrates bi-directionally with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7.

Once the program is running, readiness turns into maintenance. The metrics below show how practices keep compliance from drifting.

Measurement and Ongoing Optimization

Practices that treat compliance as an ongoing operational discipline rather than a one-time setup track metrics across four categories.

• Clinical Metrics. Alert response times and patient compliance with device use. Rhythm360 reduces critical alert response times by up to 80%.
• Operational Metrics. Staff time spent on documentation and completeness of records across the patient panel.
• Financial Metrics. Captured versus missed billable events and clean claim rates. A healthy RPM billing operation should consistently hit a clean claim rate above 95% and a denial rate below 5%. Rhythm360's automated CPT code capture helps practices capture up to 300% more revenue.
• Compliance Metrics. Denial rates, audit findings, and recoupment exposure. A denied RPM claim appears to be a minor problem, but rework costs, pattern risk, and audit exposure make a high denial rate far more expensive than it appears.

Ongoing review of workflows, staffing, and system use, rather than annual audits, is the operational posture that produces defensible documentation consistently.

Schedule a demo to optimize your remote monitoring compliance

Frequently Asked Questions

Which Documentation Gaps Cause the Most RPM Denials?

The core requirements appear in the Documentation Requirements section above. The gaps that most often sink a claim are missing or vague consent, lack of documented interactive communication for time-based codes, and time that is not clearly attributed to specific dates, staff, and activities.

What Is CPT Code 99091 Used For?

CPT 99091 is the legacy RPM-adjacent code described above. The FAQ-relevant point is that it requires at least 30 minutes of physician or qualified health care professional time per 30 days and should not be treated as substitutable for the 99453–99470 stack.

Does Medicare Pay for Remote Therapeutic Monitoring?

Medicare coverage and payment rules for remote therapeutic monitoring differ from remote physiologic monitoring. RTM monitors non-physiologic therapeutic data such as medication adherence or treatment response, while RPM monitors physiologic data such as blood pressure, weight, or glucose. RPM and RTM cannot be billed together for the same patient during the same billing period. Practices should verify payer-specific policies before billing either service, as Medicare, Medicare Advantage, Medicaid, and commercial plans may not process RTM identically.

What Are the New CPT Codes for Remote Monitoring in 2026?

The two new codes are 99445 and 99470, detailed in the Executive Overview above. The practical point is that both require at least one real-time interactive communication, and 99445 is mutually exclusive with 99454 for the same 30-day period, while 99470 is mutually exclusive with 99457 and 99458 for the same calendar month.

How Do RPM and CCM Concurrent Billing Rules Work?

RPM and CCM may be billed concurrently when each service independently meets its requirements and the same time or effort is not counted toward both. Documentation must clearly separate time attributed to RPM from time attributed to CCM, itemized by date, duration, staff member, and activity. The same employee may provide both RPM and CCM services in the same month, provided all applicable personnel and supervision requirements are met and separately reported work remains separately identifiable in the record.

What Drives Compliance Risk for Cardiac Device Codes 93294–93298?

The cycle and code assignments appear in the CIED compliance section above. For audit defense, the key points are that 93297 and 93298 are device-specific codes rather than a professional and technical pair, and applying either to the wrong device type or omitting the technical component when performed are common denial causes.

Conclusion: Compliance as a Core Operational Capability

CPT code compliance for remote monitoring is a core operational capability for cardiology and electrophysiology practices in 2026. Practices that enforce documentation, device-specific cycle tracking, and no-double-counting rules at the point of care are positioned to survive payer review, while practices that reconstruct compliance after the fact face higher recoupment risk. The audit-defense posture that protects revenue comes from the workflow itself, assembled claim by claim rather than in response to an audit notice.

When evaluating remote monitoring platforms, practices should assess whether the system enforces device-specific CPT pairings and billing cycles, captures auditable documentation at the point of care, supports concurrent billing attribution, and integrates with existing EHR infrastructure. Rhythm360 is built to meet each of those requirements for CIED and HF/HTN programs.

Schedule a demo of Rhythm360 today