RTM Documentation: What Payers Actually Need

Remote Therapeutic Monitoring claims get denied for two reasons: coverage gaps and documentation failures. Coverage gaps are straightforward — the payer doesn’t cover RTM for that patient or service category, and the fix is pre-authorization or payer selection. Documentation failures are different. They happen when RTM services are legitimately covered and clinically appropriate, but the medical record doesn’t tell the right story to support the claim. Documentation failures are entirely preventable with the right workflow, and they are the more common RTM billing problem by a significant margin. Understanding what each RTM code requires in the medical record is the starting point for building a documentation system that doesn’t leak revenue.

Why RTM Claims Get Denied

RTM denials cluster around four documentation gaps. First, missing or incomplete patient consent. The payer has no evidence that the patient agreed to the monitoring program before services began. Second, insufficient data collection evidence. The claim cannot demonstrate that the patient transmitted data on at least 16 days in the billing period. Third, missing treatment management documentation. There is no record showing that clinical staff spent 20 minutes or more on RTM services in the billing period. Fourth, inadequate clinical review notes. Data was collected but there is no evidence anyone reviewed it meaningfully.

Each of these gaps represents a different point in the RTM workflow where documentation either happens systematically or falls through the cracks. Practices that experience high RTM denial rates almost always have at least two of these gaps simultaneously, because the same process weakness that allows one gap to persist tends to create others.

Code-by-Code Documentation Requirements

CPT 98975 (initial setup and patient education) requires documentation of the patient enrollment, including the RTM consent, the diagnosis being monitored, the monitoring plan that was established, and the patient education that was provided about the use of the monitoring device or software. This code is billable once per patient and the documentation should be in the record as a permanent baseline.

CPT 98976, 98977, and 98978 (device supply for respiratory, musculoskeletal, and behavioral health monitoring respectively) require documentation that a device or software tool was supplied, that the patient transmitted data on at least 16 days during the billing period, and the dates of that transmission. The 16-day threshold is the single most critical documentation element for these codes. Without evidence of 16-day compliance, the claim is not properly supported.

CPT 98980 (first 20 minutes of treatment management) requires documentation of the clinical staff member or practitioner who performed the service, the date and duration of each RTM service activity, and a description of the clinical activity performed. The total time documented must meet or exceed 20 minutes in the billing period. Time recorded in round numbers (“30 minutes” with no further detail) is a common audit flag — time documentation should reflect what actually happened, including start and end times where possible.

CPT 98981 (each additional 20-minute increment beyond the first) requires the same documentation as 98980 for the additional time segment, plus evidence that the total time for the billing period genuinely exceeded 20 minutes before the additional code was added. Billing 98981 in a month where the total documented time is 22 minutes — barely enough to support 98980 — is difficult to defend.

The Interaction Note Requirements

The clinical interaction note is the documentation element that most practices get wrong, not because the interactions don’t happen, but because the note doesn’t reflect enough clinical content to demonstrate that the monitoring data was actually used in patient management.

A compliant RTM interaction note should include: the date and duration of the interaction, a reference to what monitoring data was reviewed (specific to the patient and the billing period), a clinical interpretation of what the data shows, and the action taken or the decision made based on that interpretation. “Reviewed monitoring data. Stable.” is not a compliant interaction note. It shows data was received but not that it was clinically interpreted or that it influenced patient management.

A better version: “Reviewed 18 days of home exercise monitoring data for the period of [dates]. Patient logged 16 of 18 available days. Average pain score 4.2 out of 10, down from 5.8 in prior period. Exercise completion rate 86%. No new symptoms reported. Trending toward discharge criteria. Will review at next in-clinic session scheduled [date].” This note demonstrates data receipt, meaningful clinical review, trend analysis, and a prospective clinical decision. It is defensible in an audit.

When an interaction includes direct patient communication — a call, a secure message, a video check-in — that communication should be documented separately from the data review, with its own timestamp and duration, and a note describing the content of the interaction and any clinical decisions that resulted from it.

How Long to Retain Records

RTM documentation retention requirements follow general Medicare and commercial payer record retention rules. For Medicare patients, records supporting RTM claims should be retained for a minimum of seven years from the date of service. Many compliance programs recommend 10 years as a conservative standard that exceeds the Medicare requirement and most state statute of limitations for medical malpractice.

The retention requirement applies to all RTM documentation: consent forms, enrollment records, monitoring data receipt logs, clinical review notes, and time tracking records. Practices that retain clinical notes in the EHR but keep RTM time logs in a separate spreadsheet need a process for ensuring the time log is preserved as long as the associated claims record.

Digital RTM platforms that retain audit trails automatically — including timestamped records of when data was received, when staff reviewed it, and when patient interactions occurred — provide the strongest documentation infrastructure for both routine audits and targeted reviews. These audit trails should be treated as medical records, not just software logs, and should be included in the practice’s record retention policy.

Audit Red Flags to Avoid

Certain documentation patterns increase the likelihood of audit selection and complicate audit defense. Billing the device supply code (98977) consistently for every patient every month without variation in 16-day compliance documentation is a red flag — it suggests the practice is billing by rote rather than confirming eligibility. Similarly, billing exactly 20 minutes of treatment management every month for every patient, with identical notes across patients, suggests templated documentation that may not reflect actual services.

High RTM billing volume combined with low in-person visit volume for the same patients can trigger review, as auditors look for patterns suggesting remote monitoring is being billed for patients the practice is not actively treating. RTM is designed for patients in active treatment — billing it for patients who have not had a relevant in-person visit in 6 or more months is difficult to defend clinically.

Billing 98981 (additional 20-minute increment) for a majority of patients in most months is also a flag. The additional increment code should reflect genuine variation in patient need — some months where a patient requires more intensive management due to a setback or program change. When the majority of patients are billed for 40+ minutes of RTM management every month, the documentation needs to be unusually strong to support it.

Documentation is the difference between an RTM program that generates clean revenue and one that generates revenue at audit risk. The investment in documentation infrastructure — templates, workflow automation, time tracking, audit trail retention — is small relative to the claims it protects.

The Audit Process for RTM Claims

Understanding how RTM claims are audited helps practices build documentation that survives scrutiny. RTM audits can be triggered by several mechanisms: statistical outlier analysis (a practice billing RTM at significantly higher rates than peers), targeted review based on whistleblower complaints, routine post-payment review by Medicare administrative contractors, or as part of a broader billing audit triggered by another compliance issue.

In a targeted RTM audit, the reviewer will typically request medical records for a random or statistical sample of billed claims. They will look for: the signed patient consent form predating the first claim date, the monitoring plan, evidence of device supply, the data transmission record showing 16-day compliance, the clinical review notes for each billing period, and the time documentation supporting each 98980 or 98981 claim. The absence of any of these elements for a given claim is grounds for recoupment of that claim, plus potential extrapolation to the full audit period if the deficiency is systematic.

The extrapolation risk is the most financially significant aspect of RTM audits. If an auditor reviews a sample of 30 claims and finds that 40 percent lack adequate 16-day documentation, they may apply that error rate to the full population of RTM claims submitted in the audit period — which could represent thousands of dollars in recoupment on claims the practice never even reviewed. Building 16-day documentation into the standard billing workflow for every claim, every month, is the protection against this extrapolation risk.

Same-Day Service Documentation Considerations

RTM services can be billed in the same month as in-office evaluation and management visits, but the documentation must clearly delineate what occurred in the office visit versus what occurred as part of RTM services. A payer reviewing a claim may scrutinize months where RTM management time is billed alongside E&M visits to confirm that the RTM documentation reflects work that is separate from and additive to the in-person visit.

The clearest documentation approach is to maintain separate time logs for in-person visit activity and RTM activity. If a provider spends 15 minutes during an office visit reviewing a patient’s RTM data and discussing it with the patient, that time contributes to the E&M visit complexity — it does not also count toward the RTM 20-minute threshold. The RTM time must be documented separately, reflecting work that occurred outside of in-person appointments: asynchronous data review, clinical decision-making based on monitoring data, and patient outreach initiated as a result of reviewing monitoring data between visits.

Staff Documentation Responsibilities

In most RTM programs, clinical staff rather than physicians perform the majority of the monitoring data review and patient engagement work that supports 98980 billing. The documentation for this staff-performed work has the same evidentiary requirements as physician documentation, but the format can be adapted to the clinical staff role.

A medical assistant or clinical coordinator performing RTM data review should document: their name and role, the date and time of the review, the specific data reviewed, a clinical observation (what did the data show?), and any action taken — including “no action indicated, data within expected range.” This documentation should be in the medical record, not in a separate administrative system that is not retained as part of the patient file.

When a physician or NP reviews and signs off on monitoring data — as required by the supervision model for 98980 billing — that review should also be documented. The documentation does not need to be extensive: a brief attestation that the physician reviewed the monitoring summary and the staff notes, with any clinical additions or changes to the management plan, satisfies the supervision documentation requirement. Practices that document staff review but not physician review are documenting only half of the required supervision chain.