Last updated: July 14, 2026
Confirm these operational prerequisites before you run the eight-step workflow. Solid infrastructure prevents denials later.
With these prerequisites in place, your team can run the eight-step verification workflow with fewer gaps and faster turnaround.
This workflow applies to all RPM enrollments in a cardiology or electrophysiology practice. Complete every step before provisioning a device or submitting a claim.
| Step | Action | Key Requirement | Common Pitfall |
|---|---|---|---|
| 1 | Confirm active insurance coverage | Verify that the patient's plan is active on the intended enrollment date and that RPM services are a covered benefit under that plan | Billing the wrong payer or a lapsed plan is the leading eligibility denial driver, so re-verify 24–48 hours before enrollment, not only at scheduling. |
| 2 | Verify established patient relationship | Medicare requires an established patient relationship before RPM services begin. Document the qualifying visit date in the chart. | New patients without a prior visit cannot be enrolled. Enrolling without this documentation is a top audit trigger. |
| 3 | Obtain and document patient consent | Consent must cover agreement to participate, single-provider acknowledgment, cost-sharing disclosure (typically 20% coinsurance), and the right to revoke at any time. Written consent with patient signature provides stronger audit protection than verbal consent. | Incomplete consent language, such as missing cost-sharing disclosure or the single-provider rule, makes consent non-compliant. Verbal consent is acceptable under 2026 CMS rules but must be documented in the medical record. |
| 4 | Confirm medical necessity for CIED or HF monitoring | Medical necessity documentation must connect the patient's acute or chronic condition to the need for remote monitoring rather than stating only the diagnosis. A valid physician order specifying the qualifying condition is required. | Generic enrollment language applied across patients is a 2026 audit trigger. Individualized clinical rationale is required for each enrollment. |
| 5 | Check device transmission capability | Confirm the assigned device is FDA-cleared and capable of automated electronic data transmission. For heart failure patients, qualifying devices include cellular or Bluetooth-connected weight scales, blood pressure monitors, and pulse oximeters that automatically transmit physiologic data. | Overlooked device connectivity issues, such as a disconnected HF scale or a CIED with a failed remote transmission session, silently erode billable days. Rhythm360's >99.9% data transmissibility, achieved via redundant data feeds and AI-powered extrapolation, flags connectivity failures before they affect the billing period. |
| 6 | Validate the 16-day data transmission requirement | A calendar day counts toward the 16-day threshold for CPT 99454 only if at least one measurement is taken and transmitted on that day; multiple readings on the same day count as one day. For 2026, CPT 99445 covers 2–15 transmitted days and CPT 99454 covers 16–30 transmitted days per 30-day period; the two codes are mutually exclusive. | The 16-day transmission threshold is the most commonly violated RPM compliance requirement and the most frequent cause of CPT 99454 claim denials and audit recoupment. Automated alerts should flag patients falling short on day 10, giving staff time to intervene with coaching or technical assistance. |
| 7 | Screen for concurrent billing conflicts | Confirm that no other practitioner has billed CPT 99453 or 99454 for the same patient in the preceding 30-day window. Only one practitioner may bill RPM services for a given patient in any 30-day period. | CCM and RPM can be billed concurrently, but time must not be double-counted. See the troubleshooting table below for specific conflict scenarios. |
| 8 | Generate auditable documentation | Required documentation includes dated patient consent with cost-sharing summary, a medical necessity statement tied to a specific condition and care plan, proof of an established patient relationship, device type and provisioning record, and an interactive communication record. | Vague time entries such as "reviewed RPM data, 20 minutes" are increasingly flagged in audits. Every entry must include date, duration, activity description, and staff identifier. |
See how Rhythm360 handles steps 5–8 automatically, eliminating manual transmission tracking and generating audit-ready documentation in real time.
Medicare fee-for-service covers RPM for any acute or chronic condition when baseline requirements are met, with no condition-specific exclusions. Effective January 1, 2026, CPT 99445 covers low-volume data transmission (2–15 days) and CPT 99454 covers standard volume (16+ days) per 30-day period. Medicare generally does not require prior authorization for RPM services.
Commercial payer policies diverge significantly from Medicare in 2026, particularly in covered conditions, prior-authorization rules, and reimbursable CPT codes. The table below highlights these differences by major payer.
| Payer | Covered Conditions (2026) | Prior Authorization | 2026 Code Notes |
|---|---|---|---|
| Medicare FFS | Any acute or chronic condition | Not required | 99445 (2–15 days) and 99454 (16+ days) both active; 99453 still requires 16-day usage in first period |
| UnitedHealthcare Commercial | Heart failure and hypertensive disorders of pregnancy only as of January 1, 2026 | Often required for device supply codes | RPM for diabetes, COPD, or hypertension outside of pregnancy treated as not medically necessary. |
| Aetna (Commercial and MA) | Heart failure, hypertension, and diabetes only as of March 1, 2026 | Required for most RPM enrollments | Explicitly excludes CPT 99445 and 99470; limits reimbursement to 99453, 99454, 99457, and 99458 |
| Cigna | Heart failure among medically necessary indications when plan-specific criteria are met | Plan-specific; verify per contract | Coverage for remote blood-pressure monitoring tightening to high-risk cases. |
For Medicare Advantage patients, providers should not apply Aetna's three-condition limitation or code exclusions and should appeal any condition-based denials using the CMS coverage standard and MA equivalent-coverage rules. As of January 1, 2026, RHCs and FQHCs must stop using the bundled G0511 code for RPM and instead report individual CPT codes.
Cardiology practices often manage patients enrolled in both Chronic Care Management (CCM) and RPM programs. The following table addresses the most frequent concurrent billing conflicts.
| Conflict Scenario | Rule | Resolution |
|---|---|---|
| Same time counted for both CCM (99490) and RPM (99457) in one month | Time that counts toward 99457 includes reviewing transmitted readings, adjusting the treatment plan, live phone or video communication, and coordinating with other clinicians; non-clinical administrative work does not count | Maintain separate time logs for CCM and RPM activities. Document each entry with date, duration, activity description, and staff identifier. |
| Two practitioners billing RPM for the same patient in the same 30-day period | Only one practitioner may bill RPM services for a given patient in any 30-day period | Run a pre-enrollment check to confirm no active RPM billing exists for the patient. Rhythm360 flags this conflict automatically at enrollment. |
| CPT 99454 billed when patient transmitted data on only 15 days | Readings on only 15 days prevent billing 99454; 2–15 days qualifies for CPT 99445 in 2026 | Use platform-level transmission day counters to select the correct code before claim submission. Never manually override the day count. |
| RPM management code billed without documented interactive communication | Treatment-management codes require documented management time and at least one interactive communication with the patient or caregiver during the month | Log the date, mode (phone or video), and clinical substance of every patient interaction. Asynchronous messages do not qualify. |
A structured eligibility workflow produces measurable improvements across three key performance indicators.
Rhythm360 clients have achieved up to a 300% increase in revenue generation through more accurate CPT code capture and improved staff efficiency, along with an 80% reduction in response times for critical patient alerts.
See your practice's validation metrics in real time—Rhythm360 tracks denial rates, verification speed, and enrollment completion automatically.
The eight-step workflow scales across practice configurations, but execution priorities shift by size and complexity.
Solo practices and small electrophysiology clinics usually manage a single CIED device line and a limited RPM panel. The highest-risk steps for these practices are step 3, which covers consent documentation completeness, and step 6, which covers 16-day transmission tracking. Manual processes fail most often in these two areas. A lightweight automated platform that flags transmission shortfalls and generates consent-compliant enrollment records addresses most denial risk without dedicated RCM staff.
Large health systems and integrated cardiology groups managing thousands of CIED patients across multiple OEM device lines face compounding complexity. Payer mix variation, multi-provider billing conflicts in step 7, and cross-team handoff failures in step 8 become more frequent. RPM utilization has become increasingly concentrated in cardiovascular conditions, with circulatory system diagnoses rising from 49.0% of visits in 2020 to 59.8% in 2024, so large cardiology programs carry proportionally higher RPM billing volume and audit exposure. Rhythm360's population-level dashboard and role-based workflow routing support this scale by consolidating data from all major device manufacturers, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into a single source of truth.
Manual eligibility workflows introduce latency and human error at every step. Automation focuses on the highest-frequency failure points: transmission day counting, consent record retrieval, and concurrent billing conflict detection.
Rhythm360 is a vendor-neutral, HIPAA-compliant platform that ingests and normalizes data from all major CIED manufacturers and RPM device types. This vendor-neutral design removes the fragmentation that occurs when staff must log into separate OEM portals for each device line. The platform's automated CPT capture engine directly addresses the transmission-day counting challenges in step 6 by tracking days per patient in real time and selecting the correct device supply code, 99445 or 99454, based on actual transmitted days instead of manual counts. To close the documentation gap in step 8, it generates audit-ready documentation bundles that include consent records, device logs, time entries, and interactive communication records. Bi-directional EHR integration then writes eligibility findings and billing artifacts back to the patient chart without manual transcription, which reduces re-entry errors.
The platform's high data transmissibility rate, detailed in step 5 above, ensures that device connectivity failures are detected and resolved before they erode billable days. This reliability supports the real-time tracking that the workflow requires. The secure, HIPAA-compliant mobile application allows clinicians and device technicians to review transmissions, confirm eligibility status, and sign reports from anywhere, which supports the cross-team handoffs that step 8 depends on. Other platforms in the cardiac monitoring space exist, but Rhythm360's integrated eligibility tracking, automated CPT documentation, and multi-condition RPM support align specifically with cardiology billing compliance needs.
Consent must be obtained and documented before RPM services begin, before the device is provisioned, and before any CPT code is billed. Written consent with patient signature provides the strongest audit protection, though verbal consent is acceptable under 2026 CMS rules when documented in the medical record. Consent is required only once per episode of care but should be re-affirmed annually or whenever there is a material change to devices, data flows, or cost structure. The consent record must include all four elements detailed in step 3 of the workflow above: participation agreement, single-provider acknowledgment, cost-sharing disclosure, and revocation rights.
CIED remote monitoring, which covers pacemakers, ICDs, implantable loop recorders, and CRT devices, is billed under a separate set of cardiac device monitoring codes, CPT 93279–93299, not under the RPM codes 99453 and 99454. RPM codes apply to physiologic monitoring devices such as connected weight scales, blood pressure cuffs, and pulse oximeters used for conditions like heart failure and hypertension. Ambulatory cardiac monitoring devices such as the Zio patch fall under CPT codes 93224–93272. A cardiology practice may bill both CIED monitoring codes and RPM codes for the same patient when the patient has both an implanted device and a qualifying chronic condition requiring physiologic monitoring, as long as each service meets its own documentation and medical necessity requirements independently.
As noted in the payer comparison above, commercial payers impose prior authorization requirements that Medicare does not. The practical effect is that commercial RPM enrollments require a prior authorization request, supporting clinical documentation, and payer approval before device provisioning, which can add days to weeks to the enrollment timeline. Practices should build prior authorization workflows into step 1 of the eligibility checklist for all commercial patients, not as a downstream billing step. For Medicare Advantage patients, some plans impose prior authorization requirements that traditional Medicare does not, so staff should verify MA plan-specific requirements separately from the underlying CMS coverage rules. Aetna's 2026 policy, for example, limits covered conditions to heart failure, hypertension, and diabetes and excludes CPT 99445 and 99470 entirely, requirements that do not apply to traditional Medicare and that may conflict with CMS MA equivalent-coverage rules for MA members.
Rhythm360's implementation process, including EHR integration setup, typically takes from a few days to a few weeks depending on practice size and the complexity of existing EHR and device manufacturer connections. The platform supports bi-directional integration with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7, and connects to all major CIED manufacturers, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, without requiring practices to maintain separate OEM portal logins. The SaaS-based pricing model scales based on clinic size and platform usage, so practices can launch with a focused CIED or HF/HTN RPM program and expand as patient volume grows.
Walk through Rhythm360's onboarding process and see the eligibility workflow in action for your practice.
Verified RPM eligibility requires eight completed checkpoints before a device is provisioned or a claim is submitted. These checkpoints include active coverage confirmed, established patient relationship documented, compliant consent recorded, individualized medical necessity established, device transmission capability validated, 16-day data rule tracked in real time, concurrent billing conflicts screened, and auditable documentation generated. Practices that execute all eight steps consistently reduce initial denial rates, protect against audit recoupment, and capture the full revenue potential of their CIED and heart failure monitoring programs. Rhythm360 automates the highest-risk steps in this workflow, including transmission day tracking, CPT code selection, consent record retrieval, and EHR documentation, so cardiology teams can focus on patient care instead of billing remediation.
Put the eight-step workflow into action—see how Rhythm360 verifies eligibility, reduces denials, and scales compliant monitoring for your cardiology practice.
