RESOURCES | BLOG
April 1, 2026

7 Cardiac RPM Billing Compliance Requirements for 2026

Meet every 2026 cardiac RPM billing compliance requirement with Rhythm360. Automate CPT capture, audit trails, and CIED code pairings. Book a demo.

Last updated: October 9, 2026

Key Takeaways

  • 2026 CMS updates introduced CPT 99445 (2–15 days) and CPT 99470 (10–19 minutes), replacing all-or-nothing thresholds and creating new billable tiers for cardiac RPM.
  • A compliant platform must automatically map every transmission to the correct CPT code, enforce mutual-exclusivity rules, and prevent duplicate billing across practitioners in the same 30-day period.
  • Every claim requires an unbroken audit-evidence chain: documented consent, physician order, FDA-cleared device logs, transmission records, clinical review, time tracking, and code rationale, all retrievable on demand.
  • Cardiac-specific code pairings (93294–93298) operate on distinct 30- or 90-day cycles and require vendor-neutral data ingestion plus bidirectional EHR integration that generic RPM tools do not provide.
  • Rhythm360 automates CPT capture, threshold detection, and audit-trail creation end to end, helping cardiology practices increase revenue capture while staying audit-ready.

Get A Compliance Readiness Check

1. Map Every Code To Its Exact Day Or Minute Threshold

The 2026 RPM code set comprises six codes, each with a distinct threshold and documentation requirement. The table below lays out each code’s threshold and required documentation side by side, showing why a platform must map every transmission automatically rather than relying on manual staff review.

CPT Code Description Day / Minute Threshold Documentation Required
99453 Initial device setup and patient education One-time per episode of care Setup event log, patient education record, consent
99445 Device supply, 2–15 days of transmitted data (new 2026) 2–15 qualifying data days in a 30-day period Automated transmission log confirming day count, physician order, patient consent, ICD-10 codes, provider NPI
99454 Device supply, 16+ days of transmitted data 16 qualifying data days in a 30-day period Automated transmission log confirming ≥16 days, physician order, patient consent, ICD-10 codes
99470 Treatment management, first 10–19 minutes (new 2026) 10–19 minutes; one interactive communication required Time log, date and method of interactive communication, clinical issue discussed, provider identity
99457 Treatment management, first 20 minutes 20 minutes; one interactive communication required Time log, date and method of real-time interactive communication, clinical notes, provider identity
99458 Treatment management, each additional 20 minutes Each additional 20-minute increment beyond 99457 Cumulative time log, separation from other billable care-management work

A cardiac RPM billing compliance platform must automatically map each device transmission to the correct code and threshold. Because a patient’s day count can change mid-period, the platform also has to flag when someone crosses from the 99445 tier into the 99454 tier and then prevent both codes from being billed for the same patient in the same 30-day window. Manual tracking of these thresholds across a large CIED and physiologic monitoring population is operationally unsustainable and a primary source of audit exposure. For a deeper look at how these codes interact with cardiology-specific workflows, see CPT Code Billing Platform For Remote Monitoring Revenue.

Correct code selection is only half the compliance picture. Every code a platform assigns also needs documentation that can withstand an audit.

2. Build An Unbreakable Audit-Evidence Chain

At audit, missing documentation is treated the same as services not rendered. Compliance is a chain of documented events, each one logged and retrievable. Every link in that chain must be logged with timestamps, user identity, data source, review notes, and code rationale.

The required links in the chain are:

Rhythm360 logs each of these events automatically, creating a timestamped, user-attributed audit trail that is retrievable on demand rather than reconstructed after the fact. Cardiovascular RPM Compliance Software Tools 2026 provides additional context on how audit-evidence chain architecture differs across platform categories.

Rhythm360
Rhythm360

3. Enforce The One-Practitioner-Per-30-Days Rule

Who Can Bill For RPM Services In 2026? Billing practitioners must hold a National Provider Identifier and be eligible to bill Medicare, including physicians (MD/DO), nurse practitioners, physician assistants, clinical nurse specialists, and certified nurse midwives. Only one provider may bill any RPM device-supply code per patient per 30-day period, though clinical staff may deliver most day-to-day RPM services under general supervision.

Only one practitioner may bill RPM for a given patient in a 30-day period, even when two specialties monitor different parameters. In a cardiology practice where an electrophysiologist and a heart failure cardiologist both interact with the same patient, the platform must prevent duplicate billing across practitioners and flag when another provider has already submitted a claim for that period. The HHS Office Of Inspector General’s August 2025 data snapshot flagged overlapping claims from multiple providers for the same beneficiary as one of five patterns targeted for further review. A cardiac RPM billing compliance platform must enforce this rule at the point of claim generation.

4. Support The 2026 Codes Without Manual Workarounds

The 2026 Medicare Physician Fee Schedule final rule split the old 16-day data-collection threshold into two billable bands: 2–15 days under CPT 99445 and 16+ days under CPT 99454, with no existing RPM codes removed or reduced. Months that previously generated zero device-supply revenue because a patient transmitted on 8 or 12 days are now billable under 99445.

Similarly, CPT 99470 provides a code for 10–19 minutes of treatment management, capturing months where a full 20-minute encounter was not reached. 99470 cannot be billed with 99457 for the same month, so the platform must select the correct treatment-management code based on actual logged minutes.

Practices that attempt to manage these new code tiers through spreadsheets or manual staff review will generate billing errors in both directions, with missed revenue from under-billing and audit exposure from over-billing. A cardiac RPM billing compliance platform should support the 2026 code tiers with automated threshold detection and mutual-exclusivity enforcement built into the billing workflow. 7 Must-Have Capabilities In Cardiology RPM Billing Software outlines the operational requirements practices should evaluate when assessing platform readiness for the 2026 code set.

See The 2026 Code Tiers In Action

5. Handle CIED-Specific Code Pairings, Not Just Generic Vitals

A cardiac RPM billing compliance platform differs from generic RPM software because cardiac monitoring involves device-specific CPT code pairings that operate on separate billing cycles and carry distinct documentation requirements.

For pacemakers and ICDs, the relevant codes operate on a 90-day cycle:

  • 93294: Pacemaker remote monitoring, professional component
  • 93295: ICD remote monitoring, professional component
  • 93296: Pacemaker or ICD remote monitoring, technical component

For physiologic monitors and loop recorders, the relevant codes operate on a 30-day cycle and are device-specific rather than a professional or technical pair:

  • 93297: Implantable cardiovascular physiologic monitor (e.g., CardioMEMS), billable once per 30 days, global or with -26 or -TC modifier
  • 93298: Subcutaneous cardiac rhythm monitor or implantable loop recorder (ILR or ICM), billable once per 30 days, global or with -26 or -TC modifier

Generic RPM platforms track blood pressure, weight, and glucose. They lack the device-specific pairing logic, billing-cycle tracking, and modifier rules that determine whether a claim is billed global, professional-only, or technical-only. Billing 93297 against a loop recorder, or 93298 against a CardioMEMS device, produces a device-type mismatch denial. Failing to bill the technical component at all leaves revenue on the table.

Rhythm360 automatically tracks these device-specific pairings, enforces the correct billing cycle for each device category, and prevents both device-type mismatch denials and unbilled technical components. Those pairings only work, however, when the platform can ingest data from every device a practice implants, regardless of manufacturer.

6. Use Vendor-Neutral Ingestion And EHR Integration

A cardiac RPM billing compliance platform must ingest data from all major CIED manufacturers, including Medtronic, Boston Scientific, Abbott, and Biotronik, as well as physiologic monitors such as CardioMEMS. Practices that implant devices from more than one manufacturer cannot maintain a compliant audit trail if staff must log into separate, non-interoperable OEM portals to retrieve transmission data.

Data normalization must occur through API, HL7, XML, and computer-vision PDF parsing. That normalization is what makes transmission logs machine-readable, timestamped, and linkable to the correct billing period regardless of source format. Bi-directional EHR integration with systems including Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health ensures that documentation written in the platform appears in the patient record the practice owns, which supports audit-ready consent and clinical review documentation.

Rhythm360 provides this vendor-neutral, multi-format data ingestion and bi-directional EHR integration. Its AI-powered alert triage and optional certified cardiac technician oversight help practices reduce critical alert response times by up to 80%. The same automation supports the revenue capture improvement noted earlier by reducing missed codes and avoidable denials.

The table below shows how Rhythm360’s platform capabilities map to the compliance requirements covered in this article, from device support to code-pairing logic.

Attribute RhythmScience (Company) Rhythm360 (Platform)
Product Type Specialized healthcare technology company focused on cardiovascular care and chronic disease management Vendor-neutral, HIPAA-compliant cloud platform aggregating CIED and RPM data
Device Manufacturer Support Designed for vendor neutrality across all major OEMs Medtronic, Boston Scientific, Abbott, Biotronik, and CardioMEMS, with data ingested via API, HL7, XML, and computer-vision PDF parsing
EHR Integration Bi-directional integration strategy Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health via HL7
Onboarding Timeline Streamlined implementation process EHR integration and onboarding in days to weeks
Pricing Model SaaS-based, value-adjusted Scales with clinic size and platform usage
CIED-Specific Code Pairings 90-day and 30-day cycle tracking Automated tracking of 93294, 93295, 93296 (90-day) and 93297, 93298 (30-day) with modifier logic
2026 RPM Code Support Native support for new code tiers Support for the 2026 code tiers with mutual-exclusivity enforcement

Check Your EHR Integration Options

7. Automate CPT Capture And Documentation End To End

Manual CPT code capture is the single largest source of revenue leakage in cardiac RPM programs. Staff must review transmission logs, count qualifying days, calculate management minutes, and select codes without automated guardrails. Errors then accumulate in both directions: codes are missed when thresholds are met, and codes are billed when documentation does not support them.

A cardiac RPM billing compliance platform must automate the full CPT capture workflow, from transmission log ingestion through threshold detection, code selection, documentation generation, and claim preparation, so that each claim is supported by the audit-evidence chain described above. CMS medical-record guidance under 42 CFR 424.516(f) requires applicable providers to maintain required documentation for 7 years from the date of service and to make it available when requested by CMS or a Medicare contractor. That documentation must be structured, retrievable, and linked to the specific claim it supports.

Rhythm360’s automated CPT code capture and documentation help practices recover previously lost revenue. The platform’s end-to-end automation means that a practice managing hundreds of CIED and physiologic monitoring patients does not need to scale administrative headcount proportionally to scale billing compliance.

Frequently Asked Questions

What Are The RPM Billing Guidelines For 2026?

The 2026 RPM billing framework comprises six CPT codes with distinct thresholds. CPT 99453 covers initial device setup and patient education and is billed once per episode of care. As covered in Section 4, the 2026 framework splits device supply into 99445 for 2–15 days and 99454 for 16 or more days and adds 99470 for 10–19 minutes of treatment management alongside 99457 and 99458. All claims require documented patient consent, a physician order, an FDA-cleared automatically transmitting device, transmission logs supporting the day count, and time logs supporting the management minutes billed. Only one practitioner may bill any RPM code for a given patient in a 30-day period.

Who Can Bill For RPM Services?

As outlined in Section 3, eligible practitioners are those with a valid NPI who are enrolled in Medicare. Clinical staff such as nurses and medical assistants may furnish day-to-day RPM services under the billing practitioner’s general supervision, meaning the practitioner directs the service and remains available for clinical judgment but need not be physically present during each patient interaction. The key operational constraint remains the one-practitioner-per-30-days rule, so practices must designate billing ownership and use a platform that prevents duplicate claims for the same patient and period.

What Is One Disadvantage Of Cardiac RPM Billing Compliance Platforms?

The primary disadvantages of cardiac RPM billing compliance platforms are upfront cost and implementation effort. Integrating a new platform with existing EHR systems, onboarding clinical and administrative staff, and migrating patient data from legacy OEM portals requires time and organizational commitment. For smaller practices, the per-patient economics must be modeled carefully against the platform’s subscription cost before enrollment scales. Rhythm360 addresses both concerns directly: its SaaS pricing scales with clinic size and platform usage rather than requiring a large fixed license fee, and its implementation process, including EHR integration, typically takes days to weeks rather than months. The revenue recovery from automated CPT capture and reduced denials generally offsets platform costs as the enrolled patient panel grows.

Is RPM Billing Legitimate?

Remote patient monitoring is a covered Medicare service with defined CPT codes, documented eligibility criteria, and published CMS billing guidelines. CMS has expanded the RPM codes eligible for reimbursement in each of the past several years, most recently in the CY 2026 Medicare Physician Fee Schedule Final Rule, where it adopted new codes CPT 99445 and CPT 99470 that were created by the AMA CPT Editorial Panel in September 2024. RPM billing is legitimate when claims are supported by the required documentation: patient consent, a physician order, an FDA-cleared automatically transmitting device, transmission logs confirming the applicable day threshold, and time logs confirming the applicable management minutes with a documented real-time interactive communication. Claims that lack any of these elements are subject to denial or recoupment because the documentation standard is strict and auditors treat missing records as services not rendered. A cardiac RPM billing compliance platform like Rhythm360 keeps claims defensible by maintaining the complete audit-evidence chain automatically, so that every submitted claim can be substantiated on demand.

Conclusion: Make The Audit-Evidence Chain Unbreakable

The 2026 RPM code changes, CPT 99445 for 2–15 days of data and CPT 99470 for 10–19 minutes of management, expand the revenue opportunity for cardiology practices while also raising the documentation precision required to capture it. Every new code tier, every mutual-exclusivity rule, and every one-practitioner-per-30-days constraint adds a link to the compliance chain. Each link must be logged, timestamped, and retrievable under audit.

Practices that attempt to manage this complexity through manual workflows or generic RPM software face a choice between leaving revenue uncaptured and accumulating audit exposure. A cardiac RPM billing compliance platform that cannot produce a traceable, timestamped record from patient consent to claim submission leaves both revenue and audit protection at risk.

Rhythm360 is the vendor-neutral, AI-powered cardiac RPM billing compliance platform built to make that chain unbreakable across CIED device pairings, physiologic monitoring codes, the full 2026 RPM code set, and the EHR systems cardiology practices already use.

Build Your Audit-Evidence Chain

Read Next

Related posts