Cardiac RTM: Heart Failure and Hypertension Monitoring

The Clinical Case for RTM in Cardiology

Cardiology is uniquely positioned to benefit from remote therapeutic monitoring (RTM) because the two most prevalent conditions in a cardiology practice — heart failure (HF) and hypertension — are defined by physiologic changes that occur between office visits. A cardiologist seeing a CHF patient every 90 days has a 90-day blind spot. RTM converts that blind spot into a continuous data stream that enables earlier intervention and, critically, generates monthly Medicare revenue for the monitoring activity.

The clinical rationale for HF monitoring is well-established: daily weight gain of 2-3 lbs over 24-48 hours is one of the earliest and most reliable indicators of fluid retention and imminent decompensation. The standard clinical guideline (per ACC/AHA Heart Failure Guidelines) is to instruct HF patients to weigh daily and call if weight increases by more than 2 lbs overnight or 5 lbs over one week. RTM operationalizes this guideline through automated data transmission and alert thresholds, replacing the "call us if" instruction — which patients consistently fail to follow — with proactive clinical surveillance.

For hypertension, home blood pressure monitoring has strong evidence basis for improving blood pressure control compared to office-only measurement. Home readings eliminate white-coat effect, capture nocturnal hypertension (a pattern associated with higher cardiovascular risk that office readings miss), and provide the multiple-reading average that is more clinically meaningful for treatment decisions than a single office measurement. RTM turns the standard recommendation to "check your BP at home" into a documented, billable clinical service.

Symptomatic monitoring — dyspnea, leg edema, palpitations, chest discomfort — adds a third data layer for HF patients. Validated symptom questionnaires (modified NYHA functional class assessment, Kansas City Cardiomyopathy Questionnaire short form) administered via RTM platform daily or weekly allow early detection of functional deterioration before it progresses to an ED visit or hospitalization.

RTM Code Set for Cardiology: CPT 98975-98981

Understanding the RTM billing architecture is essential for compliance and maximum capture. CMS created the RTM code set in 2022, and cardiology practices have a strong clinical and administrative basis for billing these codes for HF and hypertension patients.

CPT 98975 — Remote therapeutic monitoring device supply with scheduled real-time interaction with the clinical staff. Billed once per episode of care (not monthly) when the patient is set up on the RTM platform. Reimburses approximately $19 nationally. Documentation requirement: physician order for RTM, device or platform provided to patient, patient education on use.

CPT 98977 — Remote therapeutic monitoring of musculoskeletal system (20 days of data collection per 30-day period). For cardiology RTM programs focused on symptom and adherence monitoring (rather than physiologic device data), 98977 covers non-physiologic data including pain, function, and medication adherence. Reimburses approximately $48/month. Note: cardiac physiologic data (BP readings, weight) technically falls under RPM codes 99454/99453; RTM codes 98975-98981 are designed for non-physiologic data. Practices billing RTM for weight and BP should consult their compliance team on appropriate code selection — some practices use RTM for symptom monitoring and RPM for physiologic data for the same patient.

CPT 98980 — Treatment management services, first 20 minutes of physician/QHP time per calendar month. Covers the provider's time reviewing RTM data, making clinical decisions, and contacting the patient. Reimburses approximately $50/month.

CPT 98981 — Treatment management services, each additional 20 minutes. Reimburses approximately $41/month.

For practices using remote patient monitoring (RPM) codes for physiologic data alongside RTM for symptom data: CPT 99453 (device setup), 99454 (device supply, 16 days/month), 99457 (first 20 min RPM management), and 99458 (additional 20 min) are the appropriate RPM codes. These can be billed simultaneously with RTM codes for the same patient when both physiologic and non-physiologic monitoring are occurring, with careful time documentation to prevent overlap.

Heart Failure RTM: Alert Thresholds and Clinical Protocols

The clinical value of a heart failure RTM program is determined by its alert threshold design and the clinical response protocol attached to those alerts. A program that generates alerts without a defined clinical response protocol is a liability, not an asset — it creates a documentation record that the practice received a warning and did not act.

Standard HF RTM alert thresholds:

- Weight gain alert: ≥2 lbs in 24 hours or ≥5 lbs in 7 days → triggers MA review and patient callback within 4 business hours - Critical weight alert: ≥5 lbs in 24 hours → triggers immediate physician or NP notification and same-day phone contact - Dyspnea escalation: patient reports new or worsening shortness of breath (NYHA class change, difficulty walking one block) → physician review and contact within same day - Edema report: new lower extremity edema, pitting → MA callback and physician notification - BP threshold: SBP >180 or SBP <90 → immediate provider notification - Weight missing (adherence alert): no weight recorded for 3+ consecutive days → MA outreach to assess barriers

For each alert level, document the clinical response pathway in your practice's RTM protocol: who receives the alert (MA, RN, NP, physician), the expected response time, the documentation standard, and the escalation path if the patient cannot be reached.

A 3-lb overnight gain alert responded to with a furosemide dose adjustment and 48-hour monitoring can prevent a hospitalization that costs Medicare $15,000-$28,000 and causes significant patient harm. This prevention value is the clinical business case for investing in a rigorous HF RTM program — the billing revenue ($50-91/month per patient) is secondary to the clinical mission, but it makes the program financially sustainable.

Document every alert response as an RTM clinical event note: date, alert type, patient contact attempted, clinical action taken, time spent. This documentation serves double duty as the RTM billing record and the clinical care record.

Hypertension RTM: Home BP Logging and Medication Titration

Hypertension management is the highest-volume application for cardiac RTM because essential hypertension (I10) is the single most prevalent diagnosis in cardiology practices, and a significant portion of these patients have suboptimal control despite treatment. The Seventh Report of the Joint National Committee (JNC 7) established a BP goal of <140/90 mmHg for most patients; the ACC/AHA 2017 Hypertension Guidelines tightened this to <130/80 mmHg for most adults with cardiovascular risk factors. Achieving these targets in real-world practice requires between-visit data that home BP monitoring provides.

Medication titration via RTM: when a provider reviews 14 days of home BP data showing SBP averaging 148/92 on current regimen, they can initiate a medication adjustment — increasing amlodipine from 5 mg to 10 mg, adding a second agent — via a secure message or telehealth visit rather than waiting for the next scheduled appointment. This reduces the mean time to blood pressure goal achievement by an estimated 30-45 days compared to appointment-only titration.

Document medication titration decisions made based on RTM data in the RTM clinical event note, including the specific data reviewed, the clinical rationale, and the medication change ordered. This note is the billing documentation for CPT 98980 (first 20 minutes of physician RTM management) for that month.

Revenue Math: 80 Cardiac Patients on RTM

Building the revenue model for a cardiology practice with 80 patients enrolled in a combined HF + HTN RTM program using 2025 Medicare national non-facility rates:

Monthly RTM subtotal: $9,045 / Annual: $108,540

For practices also billing RPM codes for physiologic data (weight for HF, BP for HTN): - CPT 99454 (device supply, 16+ days): $48.00 × 80 = $3,840/month - CPT 99457 (first 20 min RPM management): $50.00 × 80 = $4,000/month

RPM additional monthly: $7,840 / Annual: $94,080

Combined RTM + RPM annual revenue: $202,620 for 80 patients.

Program costs: RTM/RPM platform licensing at $10-14/patient/month = $9,600-$13,440/year for 80 patients; cardiac monitoring MA or RN (0.3 FTE at $55,000 salary) = $16,500/year. Net annual contribution after costs: $172,680-$176,520.

Break-even at: 24 patients covering the monitoring staff cost. Practices with existing cardiology nursing staff can absorb RTM data review into existing roles, reducing the incremental cost further.

Important billing note: practices must verify with their MAC and compliance team whether RPM and RTM codes can be billed simultaneously for the same patient in the same month — some MACs have issued guidance on this. The conservative approach bills RTM for symptom monitoring and RPM for physiologic monitoring with clear documentation that the services are distinct.

Patient Selection and Enrollment for Maximum Clinical and Financial Impact

Enrolling the right patients in a cardiac RTM program maximizes both clinical benefit and billing compliance. The highest-value cardiac RTM patients meet clinical and administrative criteria that distinguish them from patients for whom the program adds minimal value.

Enrollment process: obtain physician order, secure patient consent (verbal or written per practice protocol), provide device or app setup with MA-led education session, confirm first data transmission within 24 hours of enrollment to verify technical success before counting the enrollment as active.

Target an enrollment rate of 60-70% of eligible patients at your first review of your panel. Practices that attempt 100% enrollment simultaneously overwhelm the onboarding process and the monitoring infrastructure. A phased enrollment — 20 patients per month — allows operational tuning before scaling.

Integrating RTM Into Cardiology Practice Workflow

RTM data is only clinically useful if it is reviewed with sufficient regularity and acted upon promptly. The workflow design for cardiac RTM must specify who reviews data, at what frequency, what actions are taken for which alerts, and how the activity is documented for billing.

Daily RTM dashboard review is the operational standard for HF monitoring programs. A designated cardiac nurse or MA reviews the RTM dashboard each morning for the previous 24 hours of data. The dashboard should surface only actionable alerts — weight gains above threshold, BP readings above threshold, symptom escalations. Raw data for patients within normal range should not require daily provider review; the platform's alerting logic handles this.

Monthly billing reconciliation: before the end of each month, the RTM coordinator confirms for each enrolled patient: (a) 16+ days of data received, (b) at least one provider review documented, (c) provider review time threshold met (20+ min for 98980). Patients not meeting criteria are not billed for that month — document the reason (patient non-compliance, hospitalization, technical failure) in the chart.

Integration with office visit workflow: when a cardiac RTM patient comes in for a scheduled office visit, the provider should review their RTM trend data as part of visit preparation — not discover it for the first time in the room. The 30-day BP trend, weight trend, and symptom frequency data should appear in the visit pre-summary alongside recent labs and last visit note.

RTM Documentation That Withstands Payer Audit

RTM billing for cardiology is a relatively recent phenomenon, and MAC post-payment audits of RTM claims are increasing as the codes mature. Documentation that withstands audit is specific, clinician-generated, and directly tied to the data reviewed.

Audit-proof RTM documentation for cardiology must contain:

1. Physician order for RTM monitoring, specifying condition being monitored (CHF, HTN), monitoring parameters (weight, BP, symptoms), alert thresholds, and reporting frequency. This order must predate the first month of billing.

2. Device supply evidence: confirmation that the patient received the monitoring device (automated BP cuff, cellular scale, symptom app) and was educated on its use. Date of supply, device type, and patient acknowledgment.

3. Monthly data receipt: the RTM platform should generate a monthly report showing the number of days data was received (must be 16+ for 98977/99454). This report is the primary evidence for the monitoring threshold requirement.

4. Provider review note (98980/98981): each month, a physician, NP, or PA must document a review of RTM data with: specific data elements reviewed (e.g., "reviewed 28-day weight trend: 3 episodes of 2+ lb overnight gain, responding to furosemide dose adjustment on [date]"), clinical assessment of data, action taken or decision to continue current plan, and time spent in minutes. Generic notes like "reviewed RTM data, no concerns" will not survive audit.

5. Patient consent: signed or verbally documented consent for RTM enrollment, with the date preceding the first billing month.

Institute a quarterly chart pull audit of 10 randomly selected RTM patients. For each, verify all five documentation elements are present and complete. Address gaps before they appear in a payer audit. The difference between a compliant RTM program and an audit liability is almost always documentation specificity, not the underlying clinical activity.