RPM Program Implementation: A 90-Day Cardiology Playbook

Key Takeaways

• Remote physiological monitoring (RPM) in cardiology differs from primary care because it involves managing CIEDs from multiple manufacturers, billing across two distinct CPT code families, and handling high alert volumes that require structured triage.
• A poorly structured RPM program risks missed critical cardiac events, alert fatigue, revenue leakage from unbilled CPT codes, and staff burnout from fragmented workflows.
• Successful implementation requires seven sequential phases over 90 days, each with named owners, deliverables, and KPIs to prevent common failure points like workflow fragmentation and unclear clinical responsibility.
• Key prerequisites before launch include an executive sponsor, clinical champion, baseline patient data, EHR integration readiness, multi-OEM device inventory, and working knowledge of both CIED and general RPM CPT codes.
• Rhythm360 provides vendor-neutral CIED and RPM data consolidation, AI-powered alert triage, and bi-directional EHR integration to help cardiology practices scale remote monitoring programs efficiently.

Talk With Rhythm360 About Cardiology RPM

Why This Process Matters

The clinical, operational, compliance, and financial stakes of a poorly structured RPM program are concrete. Missed critical events such as new-onset atrial fibrillation, ventricular tachycardia, device malfunction, or early battery depletion can result in stroke, syncope, or hospitalization. Alert fatigue erodes the clinical focus needed to catch those events. Revenue leakage from unbilled or denied CPT codes undermines the financial case for the program. Staff burnout from manual, fragmented workflows makes it harder to retain specialized cardiac device technicians.

The team involved in a cardiology RPM program spans practice administrators, electrophysiologists, cardiologists, PAs, NPs, RNs, CCTs, and billing staff. Each role carries distinct responsibilities, and when ownership is undefined, every step becomes a bottleneck.

Failed RPM pilots typically trace back to fragmented workflows such as data overload, unclear clinical responsibility, and poor integration into existing care pathways rather than device failure, though patient and device usability issues can also contribute. Andrew Beaser, MD, Associate Professor of Medicine at the University of Chicago Medicine (UCM), described pre-implementation workflows as "a major challenge and incredibly difficult." Gaurav A. Upadhyay, MD, FACC, FHRS, Professor of Medicine and Director of the Pacing & Defibrillation Device Clinic at UCM, noted: "Staffing was always an issue for our center, because our device clinic like many other medical centers had struggled with technician turnover and timely weekend coverage." A phased implementation plan addresses these structural problems directly.

See Rhythm360 in a Live Walkthrough

Prerequisites and Readiness: What Must Be in Place Before Day 1

Before the 90-day clock starts, confirm the following:

• Executive sponsor with budget authority and organizational commitment
• Clinical champion typically an electrophysiologist or cardiologist who owns clinical protocol decisions
• Baseline patient population data, including device types, manufacturers, and chronic condition mix
• EHR access and integration readiness EHR integration typically takes a few days to a few weeks
• Device inventory across all OEM manufacturers (Medtronic, Boston Scientific, Abbott, Biotronik)
• Staffing roles identified, even if not yet fully hired
• HIPAA compliance review completed for any new platform or data flow
• Working knowledge of RPM CPT codes, including the distinction between CIED monitoring codes and general RPM codes

Practices managing devices from multiple OEMs face an additional readiness step: data consolidation. A 2024 real-world study found that centers are not widely adopting alert-based monitoring strategies, in part because managing multiple proprietary vendor systems makes standardizing workflow models difficult. Teams that resolve that fragmentation before go-live create a stable foundation instead of treating consolidation as a later optimization.

How to Implement a Remote Physiological Monitoring Program in 7 Phases

The seven phases below move a cardiology RPM program from charter to pilot go-live in 90 days. Each phase includes an objective, required actions, key dependencies, and a named deliverable.

Phase 1: Define the Clinical Use Case and Target Population

Start with one condition. Heart failure, hypertension, and atrial fibrillation (AFib) all have strong clinical evidence behind cardiology RPM programs, and post-discharge monitoring is a related use case for reducing readmissions. Attempting to launch all three at once fragments attention and delays go-live, so the pilot should focus on a single condition first.

Define eligibility criteria such as NYHA Class II–III HF with a recent hospitalization or CIED patients within 90 days of implant. Define exclusion criteria such as patients without smartphone access or with cognitive barriers to device use. Estimate expected enrollment volume for the pilot cohort so staffing and device supply match demand.

The deliverable for Phase 1 is a one-page program charter that documents the clinical use case, target population, enrollment target, and executive sponsor sign-off.

Phase 2: Build the Multidisciplinary Team with Named Ownership

Every workflow step in an RPM program needs a named owner. Ambiguity about who reviews a transmission, who contacts the patient, and who signs the report creates the most common operational failure points.

Assign the following roles explicitly:

• Executive sponsor: budget, escalation authority, cross-departmental coordination
• Clinical champion: protocol decisions, alert threshold configuration, physician sign-off
• Program coordinator: day-to-day operations, enrollment tracking, patient communication
• Device technician (CCT): transmission review, report generation, alert triage
• Billing lead: CPT code capture, denial management, documentation audit
• IT/EHR analyst: integration setup, data flow validation, access provisioning

Build a RACI-style matrix (Responsible, Accountable, Consulted, Informed) for each workflow step such as patient enrollment, transmission review, alert escalation, report sign-off, and billing submission. RPM programs should build the escalation model before adding staff, documenting who owns each alert category, expected review windows, patient-contact procedures, escalation thresholds, after-hours rules, documentation requirements, and backup coverage.

The deliverable for Phase 2 is a staffing and ownership matrix.

Phase 3: How To Select RPM Devices and Vendors

Vendor selection criteria for a cardiology RPM program differ from primary-care RPM. The evaluation scorecard should include:

• FDA clearance status for all monitored device types
• Automatic transmission capability without patient-initiated action
• Vendor-neutral data aggregation across all OEM manufacturers
• Bi-directional EHR integration with the practice's existing system
• AI-powered alert triage to reduce non-actionable transmission volume
• Mobile access for on-call clinicians
• Data transmissibility reliability and redundancy

Rhythm360 consolidates CIED and RPM data across Medtronic, Boston Scientific, Abbott, and Biotronik. It adds AI-powered alert triage, maintains greater than 99.9% data transmissibility through redundant data feeds and AI-powered extrapolation, and integrates bi-directionally with Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health.

The deliverable for Phase 3 is a vendor evaluation scorecard.

Phase 4: How To Build an RPM Billing and Compliance Workflow

Cardiology RPM billing operates across two distinct CPT code families, and that split affects daily operations. CIED codes bill on 90-day cycles, while general RPM codes bill monthly, so a single patient population can require two separate billing workflows.

Device Type CPT Code(s) Billing Cycle Notes Pacemakers 93294 (professional) Up to 90 days Billed once per monitoring period; pairs with 93296 for technical ICDs 93295 (professional) Up to 90 days Billed once per monitoring period; pairs with 93296 for technical Pacemakers & ICDs (technical) 93296 (technical) Up to 90 days Technical component for pacemaker and ICD remote interrogation Implantable cardiovascular physiologic monitors (e.g., CardioMEMS) 93297 Up to 30 days Device-specific; billable once per 30 days; can be billed global, -26, or -TC Subcutaneous cardiac rhythm monitors / implantable loop recorders 93298 Up to 30 days Device-specific; billable once per 30 days; can be billed global, -26, or -TC General RPM — setup 99453 One-time per patient per device Patient education and device setup General RPM — device supply 99454 30-day rolling cycle Requires data transmission on at least 16 of 30 days General RPM — treatment management 99457 Per calendar month First 20 minutes; requires at least one real-time interactive communication

Two compliance rules govern general RPM billing and function as operational requirements. Per the CMS Physician Fee Schedule: CPT 99454 requires a patient to transmit data on at least 16 separate calendar days during a 30-day billing period. If the patient falls short of that threshold, the claim cannot be billed. CPT 99457 requires a minimum of 20 minutes of non-face-to-face treatment management time per calendar month, including at least one real-time, synchronous, two-way audio interaction with the patient or caregiver.

Rhythm360 automates device-specific CPT pairing, reduces device-type mismatch denials, and captures unbilled technical components. Gaurav A. Upadhyay, MD, at UCM, observed: "We have improved billing and accountability for our patients after the integration."

The deliverable for Phase 4 is a billing and compliance SOP.

Explore Billing Automation With Rhythm360

Phase 5: Clinical Escalation and Alert-Triage Protocol

Alert triage design needs to precede enrollment so the queue remains manageable from day one. Define three alert tiers with explicit response times and escalation paths:

• Critical: ventricular fibrillation, lead malfunction, ERI/RRT; response within hours; direct physician notification
• Urgent: new-onset AFib, significant weight gain in HF patients; response within one business day; NP/PA or physician review
• Routine: scheduled transmissions with no flagged findings; review within three business days; CCT documentation

A peer-reviewed study of 384,796 CIED transmissions found that 57% were dismissed as nonactionable, 31% were routine billable transmissions, and only 13% were critical alerts requiring genuine clinical attention. Clinical staff therefore spend most review time on transmissions that do not change patient care. AI-powered triage reduces that non-actionable volume before it reaches the clinician. UCM reviewed more than 73,000 reports annually through Rhythm360, with stable dismissal rates, demonstrating scalable monitoring in a high-volume environment.

Rhythm360's AI-powered alert triage filters non-actionable transmissions and prioritizes clinically significant events, with optional 24/7/365 CCT oversight supporting timely intervention. This approach supports up to an 80% reduction in critical alert response times.

The deliverable for Phase 5 is a written escalation protocol with named owners, response time commitments, and after-hours coverage rules.

Phase 6: Patient Onboarding, Consent, and Engagement

Patient onboarding functions as a repeatable workflow with clear steps and owners. Each step must be documented and assigned:

• Eligibility verification against the program charter criteria
• Written consent obtained before services begin; retroactive consent is not permitted under Medicare
• Device shipment or in-clinic setup with connectivity testing
• Patient education on transmission frequency, alert thresholds, and how to respond to outreach
• Documentation of device FDA-clearance status in the patient record
• Follow-up protocol for disconnected or non-transmitting devices

Rhythm360's integrated Twilio-powered messaging framework automates patient reminders, logs all communications with a full audit trail, and flags disconnected devices for coordinator follow-up. These capabilities reduce manual tracking burdens and support consistent adherence.

The deliverable for Phase 6 is a patient onboarding checklist.

Phase 7: Run a 90-Day Pilot with KPIs

The pilot cohort, typically 25 to 50 patients, runs for 90 days before any decision to scale. Define KPIs across three dimensions before go-live.

Clinical KPIs:

• Alert response time by tier (critical, urgent, routine)
• Critical event detection rate
• Time from alert to clinical intervention

Operational KPIs:

• Enrollment rate against target
• Device transmission compliance rate (percentage of patients meeting the 16-of-30-day threshold)
• Staff time per patient per month

Financial KPIs:

• Billing capture rate by CPT code
• Denial rate and denial reason distribution
• Revenue per patient per month

Set a formal go/no-go review at day 90. Programs that skip this checkpoint tend to scale problems rather than scale success. The deliverable for Phase 7 is a KPI dashboard template populated with pilot data.

Workflow Considerations Throughout

Even with all seven phases complete, certain failure points recur across cardiology RPM implementations regardless of phase, and they are easier to prevent than to correct.

• Multi-OEM portal fragmentation: Logging into separate Medtronic, Boston Scientific, Abbott, and Biotronik portals for every patient review is unsustainable at scale. Consolidate before enrollment begins.
• Manual data transcription errors: Manual entry from OEM portals into the EHR introduces errors and consumes staff time that should be spent on clinical review.
• Device-type-to-CPT mismatch denials: Billing 93298 for a defibrillator patient or applying 93297 to a loop recorder generates preventable denials. Automated CPT pairing eliminates most of these errors.
• Alert overload: RPM alert overload should first be addressed by identifying why the queue is growing; common causes include thresholds generating too many low-value alerts, duplicate notifications, unclear queue ownership, and fragmented systems. Teams should diagnose these causes before adding staff.
• EHR integration delays: Integration setup that is deferred to after go-live forces manual workarounds that often become permanent. Treat integration as a Phase 1 dependency.
• Patient non-adherence: Patients who transmit on fewer than 16 days in a 30-day period make 99454 unbillable for that cycle. Automated reminders and proactive outreach for disconnected devices function as core operational requirements.

Operational and Clinical Validation: How to Know It Is Working

Program validation at day 90 relies on measurable indicators rather than subjective assessment. Timeliness of alert response, measured against the tier-specific response time commitments defined in Phase 5, is the primary clinical indicator. Completeness of documentation, measured by the percentage of transmissions with a signed report and a documented clinical decision, is the primary compliance indicator.

Staff efficiency is measured by time per transmission review. Research tracking staff time across U.S. and European device clinics found that reviewing a single remote transmission requires between 9.4 and 13.5 minutes of staff time for therapeutic devices. Programs that exceed that benchmark without AI-assisted triage are either understaffed or over-alerting.

Patient adherence is measured by the percentage of enrolled patients meeting the 16-of-30-day transmission threshold for 99454. Billing readiness is measured by clean-claim rate, defined as the percentage of submitted claims that are paid on first submission without denial or correction.

Rhythm360's administrative dashboard provides real-time visibility into patient compliance, critical alerts, and captured and potential revenue based on CPT code requirements, giving practice administrators a single view of program health without manual reporting. Andrew Beaser, MD, at UCM, explained: "We are able to address these issues earlier; rather than waiting for a 3-month visit, we can call patients in for evaluation."

Variations and Edge Cases

Implementation differs meaningfully by practice size, care setting, patient population, device mix, and staffing model.

Practice size: A solo electrophysiologist launching a CIED monitoring program for 50 patients has different staffing and technology requirements than an integrated health system managing 2,000 patients across multiple sites. Rhythm360 scales via SaaS-based pricing based on clinic size and platform usage, which makes the same platform viable across both contexts.

Care setting: Hospital-based device clinics split CPT 93296 billing across two claim forms; the hospital reports the technical charge on a UB-04, while the reading physician reports the professional component on a CMS-1500. In an office setting, the physician's practice owns the monitoring platform and performs both data acquisition and clinical interpretation. It therefore bills the professional code (93294 or 93295) and the technical code (93296) as two separate line items on a CMS-1500, because no single global code bundles both components.

Patient population: CIED patients require the 90-day billing cycle for pacemakers and ICDs and the 30-day cycle for loop recorders and physiologic monitors. HF and HTN patients require the general RPM code family (99453, 99454, 99457). Programs that mix both populations must maintain separate billing workflows for each.

Device mix: Multi-OEM practices face the portal fragmentation problem described throughout this guide. Single-OEM practices face a different risk: over-reliance on one manufacturer's portal creates vulnerability if that portal experiences downtime or data gaps.

Staffing model: In-house CCT teams provide institutional knowledge and direct clinical integration but are vulnerable to turnover. Outsourced CCT oversight, such as Rhythm360's optional 24/7/365 certified cardiac technician coverage, provides coverage continuity without the recruitment and retention burden.

Advanced Optimization: Scaling Beyond the Pilot

A successful 90-day pilot creates the foundation for scaling, and scaling works best when standardization comes first. The first step after a go/no-go approval is workflow standardization: document every process that worked during the pilot as a written SOP before expanding enrollment.

Triage algorithm refinement follows. Alert thresholds that were set conservatively for the pilot cohort may generate excessive volume at scale. The 2023 HRS/EHRA/APHRS/LAHRS international consensus statement reports that customized alert programming can reduce alert frequency to approximately one per patient-year while making remaining alerts more actionable. Refining thresholds based on pilot data reduces alert volume while maintaining clinical safety.

Service line expansion is the next growth lever. Practices that launch with CIED monitoring can add HF and HTN RPM as a second service line once CIED operations are stable. Rhythm360 supports distinct but integrated service lines for Rhythm-CIED and HF/HTN, allowing practices to manage both populations from a single platform without duplicating administrative infrastructure.

Reporting drives cross-team coordination at scale. Programs that cannot report alert response times, billing capture rates, and enrollment trends by service line cannot identify where to invest next. Rhythm360's administrative dashboard provides that visibility in real time.

See How Rhythm360 Scales Beyond the Pilot

Frequently Asked Questions

What Is Remote Physiological Monitoring?

Remote physiological monitoring (RPM) is the clinical use of FDA-approved connected devices to capture patient physiologic data such as heart rhythm, blood pressure, weight, or pulmonary artery pressure outside a traditional clinical setting. That data is transmitted to a cloud platform where clinicians review, triage, and document findings, and bill for those services under established CPT codes. In cardiology, RPM encompasses both general chronic disease monitoring for conditions like heart failure and hypertension and the remote interrogation of cardiac implantable electronic devices such as pacemakers, ICDs, loop recorders, and implantable hemodynamic monitors. The two categories use different CPT code families, different billing cycles, and different documentation requirements.

Who Pays for Remote Patient Monitoring?

Medicare has reimbursed remote patient monitoring services since 2019, and Medicare Advantage plans are required to follow national coverage determinations (NCDs) and local coverage determinations (LCDs). In the absence of an NCD or LCD, CMS guidelines allow a Medicare Advantage Organization to make coverage determinations using an objective, evidence-based process, and prior authorization requirements vary by plan. Commercial payers vary significantly; some cover RPM broadly, others restrict covered diagnoses or require prior authorization, and some do not cover RPM at all. Medicaid coverage varies by state. For CIED remote monitoring, Medicare covers the 93294–93298 code family, with the treating physician responsible for determining appropriate monitoring frequency under National Coverage Determination 20.8.1. Practices should verify coverage and any prior authorization requirements with each payer before enrolling patients.

What Are the Top Remote Patient Monitoring Companies?

Cardiology practices benefit most from platforms that match their specific operational requirements rather than generic rankings. The evaluation criteria that matter most include vendor-neutral data aggregation across all OEM manufacturers, AI-powered alert triage, bi-directional EHR integration, automated CPT code capture for both CIED and general RPM code families, data transmissibility reliability, and scalable pricing. Rhythm360 is purpose-built for cardiology, offering vendor-neutral CIED and RPM data consolidation, AI-powered alert triage, greater than 99.9% data transmissibility, and bi-directional EHR integration with Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health.

How Long Does RPM Program Implementation Take?

A 90-day timeline from program charter to pilot go-live is realistic for a cardiology RPM program when leaders treat the launch as an implementation project with dependencies, owners, and decision gates. Many teams structure this as three 30-day sprints covering governance and contracting, workflow design, and pilot. EHR integration typically takes a few days to a few weeks depending on the EHR system and the complexity of the data flows required. The phases that most commonly extend the timeline are staffing, billing SOP development for practices new to the CIED CPT code family, and patient consent and onboarding workflow design. Practices that complete the readiness checklist before Day 1 consistently reach go-live faster than those that treat these as Phase 1 tasks.

What CPT Codes Apply to Remote Cardiac Device Monitoring?

Cardiology RPM billing spans two distinct CPT code families that mirror the table in Phase 4. For CIEDs, pacemaker remote interrogation uses 93294 (professional) and 93296 (technical) on a 90-day cycle, and ICD remote interrogation uses 93295 (professional) and 93296 (technical) on the same 90-day cycle. Implantable cardiovascular physiologic monitors such as CardioMEMS use 93297, and subcutaneous cardiac rhythm monitors and implantable loop recorders use 93298, both on 30-day cycles with professional (-26) and technical (-TC) components. For general RPM in HF and HTN, the applicable codes are 99453 for one-time setup, 99454 for device supply with the 16-of-30-day requirement, and 99457 for the first 20 minutes of monthly treatment management with at least one real-time interactive communication. Prior authorization failures are the single most common source of claim denials in cardiology billing, accounting for an estimated 20–23% of cardiology claim denials.

How Do You Prevent Alert Fatigue in an RPM Program?

Alert fatigue prevention functions as a core design input. Structural causes in cardiology RPM include alert thresholds set too broadly, non-actionable transmissions routed to the same queue as critical alerts, and the absence of AI-assisted first-read triage. Effective programs configure alert thresholds to the individual patient's clinical profile rather than relying on manufacturer defaults. They implement a tiered triage framework that routes critical, urgent, and routine transmissions to different workflows with different response time expectations. They also deploy AI-powered triage to filter non-actionable transmissions before they reach the clinical review queue. Rhythm360's AI-powered alert triage system filters non-actionable noise and prioritizes clinically significant events, with optional 24/7/365 CCT oversight. Programs that treat alert fatigue as a staffing and technology design decision sustain clinical engagement and reduce turnover among device clinic staff.

Discuss Alert-Triage Design With Rhythm360

Conclusion: Your 90-Day Checkpoints

A cardiology RPM program that reaches day 90 with all seven deliverables in place program charter, staffing and ownership matrix, vendor evaluation scorecard, billing and compliance SOP, written escalation protocol, patient onboarding checklist, and KPI dashboard can scale. A program that reaches day 90 without them relies on individual heroics and remains vulnerable to staff turnover or enrollment growth.

The checkpoints are sequential for a reason. The clinical use case defines the patient population. The patient population determines device mix and vendor requirements. Device mix and vendor selection drive billing workflows, staffing needs, and alert-triage design. When each phase builds on the last, practices create a cardiology RPM program that protects patients, supports clinicians, and sustains revenue over time.

Read Next

• How to Set Up a Remote Heart Failure Monitoring Program
• Cardiac RPM Analytics Platform for Cardiology Practices
• 7-Step 90-Day HF RPM Implementation Checklist
• Remote Patient Monitoring Benefits for Cardiology in 2026
• EHR Integration For RPM: A 2026 Cardiology Practice Guide