All posts
The Practitioner's Edge

RTM Documentation Requirements for Mental Health: What You Need for Clean Claims

2026-04-0510 min read

The number one reason mental health clinicians avoid RTM billing is not that the codes are complicated or that the reimbursement is too low. It is that they are unsure what to document. That uncertainty leads to either not billing at all (leaving money on the table) or billing with incomplete documentation (leading to denials and potential audit risk).

This post covers exactly what you need to document for each RTM code, with specific guidance for mental health practice contexts. No ambiguity. No jargon. Just the requirements.

Before You Bill Anything: Foundational Documentation

Three pieces of documentation must be in place before you submit your first RTM claim for any client.

1. Patient Consent

Written or verbal consent must be documented before initiating RTM services. The consent should cover what data will be collected (biometric data, check-in responses, therapy adherence metrics), how the data will be used clinically, that the client understands they are being enrolled in a remote monitoring program, and that they can opt out at any time.

There is no CMS-mandated consent form. Your practice can create its own. What matters is that the consent is documented in the client's record with a date and the specific elements covered.

If consent is verbal (for example, obtained during a session), document it in the session note: "Client provided verbal consent to RTM services on [date]. Discussed data collection scope, clinical use, and opt-out rights."

2. Clinical Rationale

Document why this specific client needs between-session monitoring. This is not a generic statement. It should be tied to the client's clinical presentation.

Examples of strong clinical rationale:

"Client is in active medication taper from sertraline. Between-session biometric monitoring will track sleep quality, HRV, and activity levels to provide objective data on stability during dose reduction."

"Client presents with recurrent major depressive episodes with poor insight into prodromal patterns. Continuous monitoring of sleep architecture and circadian rhythm will enable early detection of emerging episodes."

"Client reports significant anxiety between sessions with limited ability to self-assess severity. RTM will provide objective HRV and sleep data to complement self-report and inform treatment planning."

The clinical rationale should be documented in the treatment plan or in a standalone RTM enrollment note.

3. Device or Software Identification

Document what monitoring tool is being used. Identify the platform by name, what data it collects, and how data is transmitted. If using consumer wearable data (such as data from a smartwatch) through a clinical software platform, document both the wearable device and the clinical platform.

Documentation by Code

CPT 98975: Initial Setup and Patient Education

This code is billed once per episode of care. Document:

The date of setup.

What device or software was configured for the client.

What education was provided (how to use the device, what data will be collected, what to expect from check-ins, how to contact the provider with questions).

Confirmation that at least 2 days of data transmission occurred before billing.

A sample documentation note: "RTM setup completed [date]. Client educated on use of [platform name] for between-session monitoring of sleep, HRV, activity, and daily check-ins. Client demonstrated understanding of data collection process and confirmed consent. First data transmission confirmed [date]."

CPT 98978 / 98986: CBT Device Supply

These are the monthly device supply codes. 98978 covers 16-30 days of data transmission. 98986 (new for 2026) covers 2-15 days. Document:

The specific dates of data transmission during the 30-day billing period.

The total count of transmission days (must be 16+ for 98978, or 2-15 for 98986).

Confirmation that the monitoring device or software remained active and accessible to the client throughout the billing period.

A data transmission log is the cleanest documentation format. If your monitoring platform generates this automatically, export it and attach it to the billing record. If not, maintain a manual log.

Example: "Data transmission log for [client name], billing period [start date] to [end date]: 22 days of data transmitted. Data includes sleep stages, HRV, resting heart rate, activity levels, and daily check-in responses. Billing code 98978."

CPT 98980 / 98979: Treatment Management Services

These are the monthly treatment management codes. 98980 covers 20+ minutes of provider time. 98979 (new for 2026) covers 10-19 minutes. These are the codes with the most documentation requirements.

Time tracking. Document the total time spent on treatment management activities for this client during the calendar month. Activities that count include reviewing monitoring data, interpreting biometric trends, updating the treatment plan based on monitoring findings, communicating with the client about their data, and coordinating with other providers about monitoring results.

Time tracking does not need to be to the minute but should be defensible. "Approximately 25 minutes of treatment management services provided during [month]" is acceptable. Keeping a simple time log (date, minutes, activity) is stronger.

Interactive communication. This is the requirement most likely to cause a denial if missed. CPT 98979, 98980, and 98981 all require at least one real-time interactive communication with the client during the calendar month. CMS defines this as "at a minimum, a real-time synchronous, two-way audio interaction that is capable of being enhanced with video or other kinds of data transmission."

In practice, this means a phone call or video call. It does not need to be long. A 5-minute call reviewing the week's data and checking in satisfies the requirement.

What does not currently qualify: text messages alone, asynchronous chat, automated messages, or AI-powered check-ins without a live provider interaction. CMS has indicated it will adopt whatever definition the 2026 CPT Manual provides for "interactive communication," and there is discussion about expanding the definition. But as of today, document a live call or video session.

Document the date, duration, and content of the interactive communication: "Interactive communication with client on [date], 8 minutes via phone. Reviewed sleep data showing decline from baseline over past 4 days. Discussed sleep hygiene strategies and agreed to monitor for 3 more days before considering treatment adjustment."

Clinical actions taken. Document what you did with the monitoring data. This is what distinguishes billable treatment management from passive data collection. Examples:

"Reviewed HRV trend showing 20% decline from 30-day baseline. Cross-referenced with check-in data showing increased anxiety reports. Discussed with client during phone check-in. Adjusted session focus to address emerging anxiety pattern."

"Sleep data shows consistent improvement in deep sleep percentage over past 3 weeks (12% to 21% of total sleep). HRV trending upward. Data supports current treatment approach is producing measurable physiological improvement. No changes to treatment plan."

"Activity data shows step count dropped from 6,200 baseline to 1,800 over 5 days. Check-in engagement declined simultaneously. Pattern consistent with depressive withdrawal. Moved next session up by 3 days."

CPT 98981: Additional Treatment Management (each additional 20 minutes)

If you spend more than 40 minutes on treatment management for a single client in a month (20 minutes base under 98980 plus an additional 20 minutes), you can bill 98981. Document the same way as 98980 but clearly show that total time exceeded 40 minutes.

Common Documentation Mistakes That Cause Denials

Missing the interactive communication. This is the most frequent denial trigger. You reviewed the data, you adjusted the treatment plan, but you did not make a phone call or video call to the client during the month. The data review alone does not satisfy the treatment management codes. You need the live interaction documented.

Not counting data transmission days. Billing 98978 when the client only transmitted data on 14 days instead of 16. If your platform does not automatically count transmission days, you need to verify manually before billing. When in doubt, bill 98986 (2-15 days) instead.

Missing modifiers. If RTM services are provided under a therapy plan of care, GP, GO, or GN modifiers are required. If provided by a therapy assistant, CQ or CO modifiers are required. Missing these will cause denials.

Generic clinical rationale. "Client will benefit from monitoring" is not sufficient. The rationale must be specific to the client's clinical presentation and linked to treatment goals.

No documentation of clinical action. Billing treatment management codes without documenting what clinical decisions were informed by the data. If the data did not change anything, document that: "Data reviewed, all metrics within baseline range, no changes to treatment plan." The key is that you reviewed it and made a clinical judgment, even if the judgment was to continue as-is.

How a Monitoring Platform Helps

The documentation burden is the primary reason many clinicians do not bill RTM even when they are eligible and the revenue is available. A well-designed monitoring platform automates the hardest parts:

Automatic data transmission logging with day counts per billing period.

Exportable compliance reports showing exactly which clients meet the 16-day or 2-15 day threshold.

Time tracking for treatment management activities.

Clinical review records showing when and how the provider accessed monitoring data.

AI-generated summaries of client biometric trends that can be incorporated into clinical notes.

Flagging when the interactive communication requirement has not yet been met for a billing period.

This is what we built Reyma to do. The platform handles data collection, clinical interpretation, and RTM documentation so that billing is a byproduct of clinical use, not an additional administrative task.

Start Clean, Stay Clean

RTM billing in mental health is new enough that there is no established audit case law or enforcement precedent specifically for mental health RTM claims. That is both good news (no one is being targeted) and a reason to be careful (you are establishing your own compliance baseline).

The safest approach is to document more than you think you need to for the first 6-12 months. Build habits and templates. After you have a rhythm, you can streamline. Starting sloppy and trying to clean up later is much harder than starting clean.

For the complete code breakdown, reimbursement rates, and billing process, see our complete RTM billing guide. To verify your provider eligibility and estimate your revenue opportunity, follow those links.

Reyma. Always with you.

FAQ

What documentation is required for RTM billing in mental health?

Each RTM claim requires documented patient consent, clinical rationale for monitoring, device or software identification, dates and count of data transmissions, clinical review notes showing how data was used, and records of interactive communications with the patient. Missing any of these elements is a common denial trigger.

What is the interactive communication requirement for RTM?

RTM treatment management codes (98979, 98980, 98981) require at least one real-time interactive communication with the patient during the calendar month. CMS defines this as a synchronous two-way audio interaction, at minimum a phone call. Text messaging and asynchronous chat do not currently qualify on their own.

What are the most common reasons RTM claims get denied?

The most common denial triggers are missing or incorrect modifiers, insufficient documentation of data transmission days, no record of interactive communication for treatment management codes, missing patient consent documentation, and lack of clinical rationale linking RTM to the treatment plan.