5 RTM Implementation Mistakes That Kill Revenue

Practices that add Remote Therapeutic Monitoring to their billing mix often end up disappointed with the results — not because RTM doesn’t generate revenue, but because the program was implemented in a way that left most of the revenue on the table. RTM billing failures tend to cluster around five specific mistakes. They are predictable, common, and entirely fixable. If your RTM program is underperforming, one or more of these is almost certainly the reason.

Mistake 1: Not Getting Patient Consent Upfront

RTM requires documented patient consent before monitoring begins. This is not a bureaucratic formality — it is a billing eligibility requirement. Claims submitted for RTM services provided to patients who did not provide informed consent before the monitoring period began are not properly billable, and in an audit, the absence of consent documentation is one of the first things reviewers look for.

The mistake typically happens in two ways. First, practices that implement RTM quickly start enrolling patients and transmitting data before they have a consent process in place. Second, practices get verbal consent but don’t document it in a form that creates an auditable record.

The fix is straightforward: create a written RTM consent form that explains what will be monitored, how the data will be used, the patient’s right to withdraw from the program, and any costs associated with monitoring. Obtain a signed copy before or at the first monitoring enrollment visit and make it part of the medical record. Do not start the monitoring clock until consent is documented.

Mistake 2: Failing to Hit the 20-Minute Monthly Interaction Threshold

CPT 98980 requires at least 20 minutes of practitioner or clinical staff time per month spent on RTM treatment management services. This is the code that generates most of the monthly RTM management revenue, and practices frequently fail to bill it correctly because they either don’t track the time spent at all, or they discover at the end of the month that they can’t document 20 minutes for a specific patient.

The underlying clinical failure is often that the RTM program is not actually generating meaningful patient interaction. If staff are reviewing data but not documenting their review time, or if patients are transmitting data that nobody is actively reviewing, the 20-minute threshold is not being met through actual clinical activity.

The fix has two components. First, build time tracking into the RTM workflow from day one. Every time a staff member reviews data, responds to a patient message, or makes a clinical decision based on monitoring data, that time should be logged immediately. Second, assign specific staff members to specific patient panels for RTM monitoring so that the responsibility is clear and the time adds up predictably. A staff member who knows she is responsible for 30 RTM patients will structure her workflow to ensure those patients get meaningful attention each month.

Mistake 3: Missing the 16-Day Data Collection Minimum

CPT 98977 and 98978 (device supply codes) require that the patient transmit data on at least 16 of the 30 days in the billing period. This is a patient behavior requirement, not a practice requirement — and practices that do not actively monitor patient data transmission frequently bill device supply codes for patients who have not met the threshold.

This is the most common RTM audit finding. The practice assumes that because a patient is enrolled and the monitoring is active, data is being transmitted. In reality, patients miss days, forget to log, or disengage from the monitoring tool for stretches of time without the practice knowing. Claims for 98977 submitted without confirming the 16-day threshold are improperly billed and may require repayment with interest in an audit.

The fix is a real-time compliance dashboard. Every RTM patient should have a visible count of data transmission days in the current billing period. When a patient reaches day 20 of the month and has only transmitted on 8 days, staff need a workflow trigger to reach out and re-engage the patient — not to manufacture compliance, but to support it. Many patients who fall behind on monitoring respond to a simple check-in message and return to consistent logging. The patient who would have hit 10 days without intervention hits 18 days with it.

Mistake 4: Not Billing All Available Codes in the Series

RTM is a code series, and the full revenue per patient depends on billing all eligible codes each month. Many practices that run RTM programs bill 98977 and 98980 and stop there, consistently missing 98975 (in the enrollment month), 98981 (for additional 20-minute increments beyond the first), and sometimes the appropriate device supply code for their specialty.

The most expensive single miss is 98975. It is billable only once per patient, in the enrollment month, and represents the setup and patient education services. Practices that start billing RTM mid-program — often because they implemented RTM informally before setting up proper billing — typically never bill 98975 for their initial cohort, leaving that revenue permanently uncaptured.

The fix is a billing checklist that runs at the start of each patient’s first RTM billing month and at the start of each subsequent month. The checklist confirms: Is this the enrollment month? Bill 98975. Is 16-day data threshold met? Bill 98977 or 98978. Is 20 minutes of treatment management documented? Bill 98980. Is more than 20 minutes documented? Bill 98981 for each additional increment. Systematic use of the checklist eliminates the revenue leakage from missed codes.

Mistake 5: Poor Patient Enrollment Rates

The most fundamental RTM revenue problem is not billing errors — it is a small enrolled patient panel. A practice with 200 eligible patients that has enrolled 15 in RTM is not running an RTM program. It is running an RTM pilot that generates a fraction of the revenue the practice should be capturing.

Low enrollment rates almost always trace to one of three causes: the enrollment conversation happens inconsistently (some providers discuss RTM with patients, others don’t), the technology friction is high enough that patients decline to engage, or the practice has not made enrollment an operational priority with a target and accountability.

The fix requires treating RTM enrollment as an operational metric, not a clinical side project. Set an enrollment target — a reasonable goal is 30% to 50% of eligible patients in the first year — and track it monthly. Build the enrollment conversation into the standard visit workflow for eligible patients. Make the technology as simple as possible: if patients can enroll with a phone scan and start logging in under two minutes, enrollment rates go up. If enrollment requires a 15-minute orientation with a pamphlet and a separate login, they go down.

RTM is not a passive revenue stream. It requires active program management. The practices that run it well — with consent processes, time tracking, compliance monitoring, full code billing, and disciplined enrollment — generate consistent, significant revenue from it. The ones that implement it casually generate enough to see the potential, not enough to justify the effort. The difference is entirely in execution.

The Organizational Setup Required Before Billing

Many practices rush to start billing RTM before they have the organizational infrastructure in place to support it. This produces a period of billing that later requires correction — reprocessing claims, retroactively updating documentation, and sometimes issuing refunds for codes that were billed without proper support. The setup work before the first claim is submitted is not overhead — it is the foundation that makes all subsequent billing defensible.

The minimum organizational setup for an RTM program includes: a written RTM consent form that has been reviewed for accuracy and compliance; a defined monitoring program for each eligible diagnosis category with a documented monitoring plan template; an assigned staff member or team responsible for monitoring data review and time tracking; a defined billing workflow with clear triggers for each code in the series; and a method for tracking 16-day compliance per patient in real time.

Practices that try to build these elements retroactively — after billing has started — consistently find that some of the initial claims are not properly supported and face a choice between proactive correction and audit risk. The practices with the cleanest RTM billing histories are those that spent two to four weeks on program design before enrolling the first patient.

The Documentation Template Problem

RTM programs that rely on free-text documentation for data review notes produce inconsistent records that are difficult to audit and time-consuming to review. When clinical staff write RTM review notes in free text, the notes vary dramatically in content, specificity, and defensibility. Some notes are comprehensive clinical narratives. Others are minimal notations that do not demonstrate meaningful data review.

Structured documentation templates for RTM review notes solve this problem by ensuring that every note covers the required elements: what data was reviewed, for what period, what it showed clinically, and what action was taken or not taken based on that data. Templates do not need to be long or complicated. A well-designed RTM review note template might have five fields that take 2 to 3 minutes to complete and consistently produce a defensible, clinically meaningful record.

The time investment in designing documentation templates before the program launches is repaid many times over in the consistency and quality of the records they produce. A practice with 60 RTM patients and a good template generates 60 consistent, auditable review notes per month. The same practice without a template generates 60 records of wildly varying quality, some of which will not support the associated billing in an audit.

Monitoring Patient Dropout and Re-Engagement

Patient dropout from RTM programs is a revenue leak that practices frequently miss because it is gradual rather than sudden. A patient does not announce that they are no longer participating in RTM — they simply stop logging data as consistently as they did initially. The practice that is not actively monitoring per-patient data transmission will not notice the dropout until the end of the month, when the 16-day threshold has already been missed and the device supply code cannot be billed.

Re-engagement is far more effective than replacement. A patient who was engaged and drifted has already made a commitment to the program and is generally recoverable with a simple outreach: a check-in call, a message noting that the practice noticed they haven’t logged in a while and asking if they need support. Most patients who drift from RTM compliance respond positively to this kind of personal outreach and return to consistent logging. The patient who would have ended the month at 9 days logged often reaches 16 days logged after a mid-month re-engagement call.

Tracking re-engagement rate — the percentage of patients who were trending below the 16-day threshold and recovered to compliance after outreach — is a useful operational metric for RTM programs. A re-engagement rate above 60 percent means the outreach process is working. Below 40 percent suggests either the outreach is happening too late (when there are too few days remaining to reach the threshold) or the monitoring technology is creating friction that outreach alone cannot resolve.