RTM Billing Software

Remote Therapeutic Monitoring is a Medicare billing pathway for the systematic collection and clinical review of patient-reported health data between office visits. RTM captures revenue for work that chronic disease management already requires but that historically went uncompensated.

Chronic disease patients need ongoing monitoring to optimize their treatment. Pain management patients should track pain levels and medication response. Pulmonology patients should track breathing difficulty and rescue inhaler use. Behavioral health patients should track mood and symptom severity. Physical therapy patients should track function and activity tolerance. This monitoring data informs treatment adjustments and catches problems before they escalate into emergencies or hospitalizations.

Before RTM codes existed, this monitoring happened informally. Patients mentioned symptoms at quarterly visits, recalling weeks or months of experience imperfectly. Providers made treatment decisions based on incomplete information. The actual work of monitoring between visits went uncompensated because no billing mechanism existed to capture it.

CMS introduced RTM codes in 2022 and expanded coverage in subsequent years to create a reimbursement pathway for this work. Practices that systematize their between-visit monitoring can now bill for patient enrollment, data collection platform supply, and clinical time spent reviewing data and managing treatment based on findings. The revenue represents payment for work that should already be happening in quality chronic disease management.

RTM differs from Remote Patient Monitoring in the type of data collected. RPM uses physiological devices such as blood pressure cuffs, glucose monitors, and pulse oximeters that transmit measurements automatically. RPM requires distributing devices to patients and managing device logistics. RTM uses patient-reported data entered by patients themselves through the clinIQ app or web portal. RTM works with any smartphone or computer without requiring device distribution. Wearable device integration can supplement RTM data with continuous metrics from Apple Health, Oura Ring, and Android Health Connect. Many patients qualify for both RTM and RPM, and practices can bill both when clinical circumstances support it.

The revenue opportunity from RTM is substantial for practices with chronic disease patients. One hundred patients enrolled at one hundred twenty dollars monthly average reimbursement generates twelve thousand dollars monthly or one hundred forty-four thousand dollars annually. This revenue comes with minimal incremental cost because it compensates for monitoring work that quality practices already perform. Practice analytics track RTM program performance and identify optimization opportunities.

RTM billing uses five CPT codes that together capture the components of remote therapeutic monitoring. Understanding each code's requirements and reimbursement is essential for proper billing and revenue optimization.

CPT 98975 covers initial setup of the RTM program for a patient. This one-time code is billed at patient enrollment and covers the work of configuring the monitoring platform for the patient, educating the patient on how to use the clinIQ app for symptom reporting, and establishing the monitoring parameters appropriate for their condition. Reimbursement runs approximately twenty to twenty-five dollars. The code is billed once per patient when they enter the RTM program, not monthly.

CPT 98976 covers the monthly device or software supply for respiratory system conditions. This monthly code covers the technology platform that enables patient data collection for conditions such as COPD, asthma, and other chronic respiratory diseases managed by pulmonology practices. Reimbursement runs approximately fifty-five to sixty-five dollars monthly. Beginning in 2024, this code also applies to behavioral health conditions including depression, anxiety, and substance use disorders, expanding its applicability significantly to psychiatry and addiction medicine practices.

CPT 98977 covers the monthly device or software supply for musculoskeletal system conditions. This monthly code covers the technology platform for conditions such as chronic pain, arthritis, post-surgical recovery, and physical therapy conditions. Reimbursement runs approximately fifty to sixty dollars monthly. This is the most commonly billed RTM device supply code because musculoskeletal conditions are prevalent across many specialty types including pain management, orthopedic surgery, rheumatology, sports medicine, and chiropractic.

CPT 98980 covers treatment management services for the first twenty minutes of clinical time monthly. This monthly code covers the clinical work of reviewing patient-submitted data, analyzing trends, communicating with patients about findings through secure messaging, and adjusting treatment based on RTM data. Reimbursement runs approximately fifty to seventy dollars monthly. The code requires at least twenty minutes of qualified clinical time accumulated throughout the month. Time can be contributed by physicians, nurse practitioners, physician assistants, registered nurses, and clinical staff under physician supervision.

CPT 98981 covers treatment management services for each additional twenty-minute increment beyond the first twenty minutes. This add-on code captures additional clinical time for complex patients requiring more intensive management. Reimbursement runs approximately forty to fifty dollars per additional twenty-minute block. The code is billed alongside 98980 when total monthly time exceeds forty minutes, sixty minutes, or higher increments.

Typical monthly billing combines a device supply code with treatment management. A patient with chronic back pain might be billed 98977 for musculoskeletal device supply plus 98980 for twenty minutes of treatment management, yielding approximately one hundred to one hundred thirty dollars monthly. A complex patient requiring forty minutes of management adds 98981 for another forty to fifty dollars. The combination of codes provides meaningful revenue per patient that accumulates across an enrolled patient population.

RTM eligibility spans a wide range of chronic conditions where between-visit monitoring informs treatment decisions. The common thread is that patients experience symptoms or status changes that should be tracked and that tracking data influences clinical management.

Musculoskeletal conditions represent the largest category of RTM-eligible patients. Chronic pain of any type qualifies, making pain management practices ideal RTM candidates. Inflammatory conditions such as rheumatoid arthritis, osteoarthritis, and gout qualify — all common in rheumatology. Post-surgical orthopedic recovery qualifies during the period when patients should track pain, function, and rehabilitation progress. Physical therapy conditions qualify when tracking exercise compliance and functional improvement informs treatment progression. Fibromyalgia qualifies given its symptom variability requiring ongoing monitoring. Sports medicine injury recovery and chiropractic care for chronic spine conditions also qualify.

Respiratory conditions qualify under the respiratory RTM device supply code. COPD qualifies given the need to track dyspnea, exacerbations, and rescue medication use. Moderate to severe asthma qualifies given the need to track symptom control. Pulmonology practices find significant RTM opportunity with these patients. Interstitial lung disease, pulmonary fibrosis, and post-COVID respiratory complications all qualify when ongoing monitoring informs management.

Behavioral health conditions became explicitly eligible under the respiratory device supply code beginning in 2024. Depression qualifies with monitoring of mood, sleep, and functional status. Anxiety disorders qualify with monitoring of symptom severity and situational triggers. PTSD qualifies with monitoring of flashbacks, avoidance, and hyperarousal symptoms. Addiction medicine practices can monitor cravings, triggers, and recovery progress. Psychiatry practices can monitor medication response and symptom patterns. Behavioral health practices of all types can now implement RTM programs.

Cardiovascular conditions qualify under the musculoskeletal code in most billing guidance. Heart failure qualifies with monitoring of weight, edema, and dyspnea symptoms — common cardiology presentations. Hypertension qualifies when patients report blood pressure readings and symptoms. Cardiac rehabilitation patients qualify during recovery when monitoring exercise tolerance and symptoms informs progression.

Other chronic conditions qualify based on monitoring need. Endocrinology patients with diabetes qualify when patients report glucose readings and symptoms. Nephrology patients with chronic kidney disease qualify with monitoring of symptoms, weight, and dietary compliance. Gastroenterology patients with inflammatory bowel disease qualify with monitoring of symptoms and flares. Wound care patients qualify with monitoring of healing progress and complications. Neurology conditions such as multiple sclerosis and migraine qualify when symptom monitoring informs treatment.

The practical test for eligibility combines clinical appropriateness with payer coverage. Clinically, the patient should have a chronic condition where between-visit monitoring data would genuinely inform treatment decisions. From a coverage perspective, the patient's payer must reimburse RTM codes for the relevant condition. Medicare covers RTM broadly. Commercial payer coverage varies and should be verified per patient.

Enrollment rate determines RTM program revenue. A practice with one hundred eligible patients at twenty percent enrollment generates revenue from twenty patients. The same practice at seventy-five percent enrollment generates revenue from seventy-five patients, nearly four times the revenue. Enrollment strategy directly impacts program success.

Eligible patient identification begins with panel analysis visible in practice analytics. Review your patient population to identify patients with qualifying chronic conditions who visit regularly and have payer coverage for RTM codes. The analysis yields a target list for enrollment outreach. For a pain management practice, this might include nearly all active chronic pain patients. For a primary care practice, this might include patients with chronic conditions such as diabetes, COPD, and heart failure. The identification process should be systematic rather than relying on providers to remember which patients to enroll.

Provider recommendation drives the highest enrollment rates. When the physician or advanced practice provider explains RTM to the patient and recommends participation, enrollment rates reach fifty to seventy percent. Patients trust their provider's recommendation and understand that the monitoring benefits their care. The provider framing should emphasize clinical benefit rather than billing mechanics. The patient should understand that tracking their symptoms through the clinIQ app between visits helps the care team adjust treatment faster and catch problems earlier.

Enrollment workflow minimizes friction for both staff and patients. The enrollment conversation happens during a regular visit. The provider recommends RTM and briefly explains what it involves. The patient agrees. Staff obtains consent, which can be electronic signature through the clinIQ app. If the patient does not already have the app installed, staff assists with download and initial setup. The patient receives a walkthrough of how to submit symptom data. The entire enrollment process adds three to five minutes to a visit. For practices already using the app for check-in, patients are already familiar with the interface.

Consent documentation is required for compliance. The consent should explain what RTM involves, how data will be collected and used, and any patient responsibilities. The consent becomes part of the medical record and supports billing. The clinIQ app presents the consent clearly and captures electronic signature as part of the enrollment flow.

Post-enrollment activation ensures patients actually begin submitting data. Some patients agree to enrollment but never start using the app for symptom reporting. Activation outreach from staff — via phone or secure messaging — ensures the patient has the app installed, understands how to submit data, and has actually submitted at least one entry. This outreach happens within the first week after enrollment and catches patients who would otherwise become inactive before generating any billable activity.

Ongoing engagement maintains participation over time. Patients who stop submitting data receive outreach to re-engage them. The app tracks submission recency and the system flags patients who have gone quiet. Staff outreach reconnects these patients or, when appropriate, removes them from the program if they are unwilling to participate.

Data collection is the foundation of RTM. Without patient-reported data, there is nothing to review and no clinical value to bill for. The clinIQ app provides a collection method that patients actually complete regularly over months and years of ongoing monitoring.

The clinIQ app sends push notifications prompting patients to enter symptom data on their configured schedule. When the patient taps the notification, the app opens directly to the symptom entry screen. They answer condition-specific questions, taking two to three minutes to complete. The brevity is essential because patients will abandon lengthy questionnaires. A five-question check-in achieves far better compliance than a twenty-question assessment.

Patients who prefer web-based interaction can submit data through the clinIQ web portal. The portal provides the same symptom entry interface accessible through any browser. Some patients prefer the web option when they are at a computer. Data submitted through either channel synchronizes to the same patient record.

Wearable device integration supplements patient-reported data with continuous passive metrics. Patients who connect Apple Health, Oura Ring, or Android Health Connect contribute sleep data, heart rate trends, activity levels, and other measurements without any data entry burden. This continuous data enriches the clinical picture and provides objective metrics alongside subjective symptom reports. For cardiology patients, heart rate variability trends from wearables provide valuable monitoring data. For behavioral health patients, sleep patterns correlate with mood and symptom severity.

Question design balances clinical utility against completion burden. Every additional question reduces completion rate. The questions capture the minimum information needed to inform clinical decisions. For pain management patients, this includes pain intensity on a zero to ten scale, medication use, and functional impact. For pulmonology patients, this includes breathing difficulty, rescue inhaler use, and activity tolerance. For behavioral health patients, this includes mood rating, sleep quality, and any concerning symptoms. The specific questions are configured per condition and can be customized per practice preference.

Collection frequency balances data density against patient fatigue. Daily collection provides rich data but risks patient burnout over time. Weekly collection provides adequate data for most chronic conditions while being sustainable for long-term participation. The app sends notifications on the configured schedule and allows patients to submit additional entries whenever they want to report changes. Most practices use weekly collection as the default with flexibility for patient and provider preference.

Clinical questionnaire integration allows validated instruments to be administered through the app. The PHQ-2 or PHQ-9 for depression screening, GAD-7 for anxiety, PROMIS instruments for various conditions, and condition-specific assessments can be embedded in the data collection flow. These validated instruments add clinical rigor and support documentation.

Secure messaging through the app enables patient-provider communication about RTM findings. When a patient reports concerning symptoms, staff can message them directly through the app to follow up. When clinical review reveals a need for adjustment, the provider can communicate with the patient without requiring a phone call. This messaging is documented and can contribute to RTM time tracking.

Data quality monitoring within practice analytics ensures the collection system is working. Track submission rates to identify patients who are not participating. Track completion rates to identify questions that patients skip. Track response patterns to identify patients who might be clicking through without genuine engagement. This monitoring allows intervention before data gaps undermine program value.

The treatment management codes require documented clinical time. CPT 98980 requires at least twenty minutes of qualified clinical time per patient per month. Without proper time tracking, practices either underbill because they cannot prove they met the threshold or overbill because they estimate rather than document actual time. Both outcomes are problematic.

Qualified activities that count toward RTM time include reviewing patient-submitted data in the clinIQ dashboard, analyzing trends across multiple data points, reviewing wearable data trends, identifying concerning findings requiring intervention, communicating with patients about their data via secure messaging or phone, adjusting treatment plans based on RTM findings, documenting findings and clinical decisions, and coordinating care with other providers based on RTM findings. Time spent on these activities accumulates throughout the month toward the twenty-minute threshold.

Activities that do not count toward RTM time include administrative setup already covered by the 98975 enrollment code, patient time entering their own data in the app, time spent on activities billed under other codes such as office visits or chronic care management, and general chart review unrelated to RTM data. Practices must distinguish RTM time from these other activities to bill accurately.

Automatic time tracking eliminates the burden of manual logging and improves accuracy. The clinIQ platform tracks time spent in RTM workflows automatically. When a clinician opens the RTM dashboard to review a patient's submitted data, time tracking starts. When they complete their review or switch to another patient, time tracking stops. Communication through the secure messaging function is tracked. Documentation time is tracked. These automatic captures accumulate accurately without relying on staff memory or manual entry.

Time threshold visibility helps staff prioritize their review activity. The system shows each patient's accumulated time for the month and distance from the twenty-minute threshold. A patient at eighteen minutes needs only two more minutes of review to reach threshold. A patient at five minutes needs substantial additional review. Staff can prioritize attention toward patients close to threshold while being efficient with patients who have already exceeded it. This visibility appears in the analytics dashboard.

Monthly time reports document time by patient for billing support. When questions arise about whether a patient met the billing threshold, the time report provides detailed documentation of activities and duration. This documentation supports claims in the event of audit and provides confidence that billing reflects actual work performed.

Monthly RTM billing for dozens or hundreds of patients creates administrative complexity that manual processes struggle to handle. Automation ensures every billable patient gets billed, every eligible code is captured, and nothing falls through the cracks.

Month-end billing generation identifies patients meeting billing criteria. For each enrolled patient, the system verifies that data was collected through the app during the month, that clinical time met or exceeded the twenty-minute threshold, that consent is documented, and that no exclusions prevent billing. Patients meeting all criteria generate claims with appropriate codes. Patients failing criteria are flagged with specific reasons for review.

Code selection matches each patient's situation. The device supply code matches the patient's qualifying condition. A pulmonology patient generates 98976 while a pain management patient generates 98977. A behavioral health patient now generates 98976 under the expanded coverage. The treatment management code reflects actual time. Twenty to thirty-nine minutes generates 98980 alone. Forty to fifty-nine minutes adds one unit of 98981. Higher times add additional units. This precise code selection maximizes revenue while ensuring accuracy.

Billing verification allows staff review before claim submission. The system presents a summary of patients being billed, codes assigned, and any exceptions requiring attention. Staff reviews this summary, addresses any issues, and confirms billing generation. This verification step catches problems before claims submit rather than after denials occur.

Denial tracking within practice analytics monitors claim outcomes and identifies patterns. When RTM claims are denied, the denial reason is captured and categorized. Common denial reasons might include coverage limitations, bundling issues, or documentation questions. Pattern identification reveals systemic issues that process changes can address. A denial pattern from a specific payer might indicate a policy change requiring enrollment adjustment for that payer's patients.

Revenue reporting tracks RTM program performance over time. Monthly revenue, patients billed, revenue per patient, and trending allow program assessment. Leadership can see whether the program is growing, stable, or declining. Comparisons to benchmarks reveal whether performance is strong or has improvement opportunity. These reports in analytics support program optimization and demonstrate ROI to stakeholders.

Integration with practice management systems or clearinghouses streamlines claim submission. Rather than manually entering RTM claims, the billing automation generates claims in formats that flow into existing billing workflows. This integration reduces duplicate entry and ensures RTM claims process alongside other practice claims.

RTM implementation follows a phased approach that builds capability progressively rather than attempting full deployment immediately. Most practices move from initial pilot to full-scale operation within eight to twelve weeks.

The preparation phase lasting one to two weeks focuses on groundwork before any patient enrollment. The team identifies the target patient population through panel analysis in practice analytics. Data collection templates are configured for relevant conditions. Staff workflows are designed for enrollment, data review, and billing. EHR integration is configured if applicable. Staff training prepares the team for pilot operation including how to assist patients with app installation.

The pilot phase lasting two to four weeks enrolls a limited patient group to validate workflows before scaling. Twenty to thirty patients is a typical pilot size, small enough to manage intensively but large enough to reveal operational issues. The pilot tests enrollment process including app setup, patient experience with symptom submission, staff workflow for data review, time tracking accuracy, and billing generation. Issues discovered during pilot are resolved before scaling.

The scaling phase expands enrollment toward the full eligible population. Staff works through the target patient list systematically, enrolling patients at each visit and assisting with app installation. Enrollment can also happen during patient check-in when patients are already engaging with the app. Enrollment volume increases as staff becomes comfortable with the workflow. Data review and billing processes handle increasing patient counts. The program reaches steady state as most eligible patients are enrolled and ongoing enrollment captures new patients.

The optimization phase continues indefinitely as the program matures. Analytics reveal opportunities for improvement. Enrollment rates can be increased through workflow refinement. Data collection compliance can be improved through patient engagement adjustments including push notification timing and frequency. Wearable integration can be added to enrich data collection. Clinical integration can deepen as providers incorporate RTM data more fully into their care decisions. The program generates more value over time.

Return on investment math is straightforward. Revenue per patient runs approximately one hundred to one hundred thirty dollars monthly combining device supply and treatment management codes. Cost per patient includes platform fees typically running ten to twenty dollars monthly and staff time for data review typically running fifteen to thirty dollars monthly. Net margin per patient runs fifty to one hundred dollars monthly.

Scaled across a patient population, the returns are substantial. One hundred enrolled patients at seventy-five dollars net margin generates seventy-five hundred dollars monthly or ninety thousand dollars annually in net program revenue. Two hundred enrolled patients doubles this to one hundred eighty thousand annually. Larger practices with three hundred or more enrolled patients can generate net program revenue exceeding quarter million dollars annually.

The investment to launch is modest. clinIQ Professional at four hundred ninety-nine dollars monthly includes RTM along with patient check-in, patient flow, scheduling, analytics, and other modules. Implementation is seven hundred fifty dollars one-time. Total first-year investment under seven thousand dollars generates returns exceeding fifty thousand dollars for practices enrolling even modest patient numbers. Payback typically occurs within two to four months of launch.