What RTM Is and Why Spine Surgery Is the Perfect Use Case
Remote Therapeutic Monitoring (RTM) — established by CMS in the 2022 Physician Fee Schedule — is a set of CPT codes that allow providers to bill for the collection and interpretation of non-physiological data from patients outside the clinical setting. Unlike Remote Patient Monitoring (RPM, CPT 99453–99458), RTM captures musculoskeletal and respiratory data rather than vital signs, making it structurally aligned with spine surgery post-operative care. The four RTM codes relevant to spine surgery are: CPT 98975 (initial setup and patient education, billed once per episode), CPT 98977 (device supply for musculoskeletal data collection, billed monthly), CPT 98980 (first 20 minutes of clinical staff time for monitoring and patient communication), and CPT 98981 (each additional 20 minutes beyond the first, billed per additional increment). Spine surgery creates an ideal RTM population for three reasons. First, post-op spine patients have high clinical monitoring needs — pain trajectories, functional recovery, wound healing, and physical therapy compliance all benefit from structured remote tracking. Second, these patients are motivated and engaged in their recovery, leading to high device compliance rates (typically 75–85% in spine-specific programs). Third, the monitoring data is clinically meaningful — it allows the surgical team to identify patients trending toward complications, readmission, or PT non-compliance before these become expensive problems. The combination of genuine clinical value and recoverable billing makes RTM one of the highest-ROI programs a spine practice can implement in 2025.
Setting Up RTM: The Device, Consent, and Enrollment Workflow
A compliant RTM program requires a FDA-cleared monitoring device or software platform that transmits data to the clinical team. For spine surgery, the most common approaches are: (1) a wearable activity and pain-tracking device, (2) a mobile application with structured daily symptom questionnaires and photo capture for incision monitoring, or (3) a hybrid combining wearable data with app-based self-reporting. CMS does not specify the device type — the requirement is that the device automatically transmits data to the provider without patient-initiated uploads. Platforms that require patients to manually log in and upload data do not qualify. The enrollment workflow begins pre-operatively. Ideally, RTM consent is obtained at the pre-op appointment or during surgical scheduling — not in the immediate post-op period when patients are managing pain and discharge anxiety. Your clinical coordinator should obtain written consent, set up the patient's device or app, and verify data transmission before surgery. CPT 98975 (setup and education) can be billed once the device is set up and the patient has received education on its use — this does not require 16 days of data collection and can be billed in the month of setup. The 16-day data requirement applies to CPT 98977 (device supply) — this code requires that the device collects and transmits data on at least 16 of the 30 days in the billing month. Your RTM platform must generate a compliance report showing the days of data collection for every patient every month. Missing this documentation is the most common RTM audit failure.
What to Monitor: Pain, Function, Incision, and PT Compliance
For post-operative spine patients, a well-designed RTM program tracks four data domains that together give the clinical team a complete picture of recovery trajectory. Pain tracking uses daily VAS or NRS pain scores submitted through the patient's app. The clinical team should set alert thresholds — for example, a VAS score above 7 on three consecutive days triggers a nurse call — and document interventions when thresholds are breached. Pain data is also the primary evidence of RTM clinical value for payer audits. Functional recovery is captured through activity metrics (step counts, movement patterns from wearable data) and structured functional questionnaires at defined intervals — typically 2 weeks, 4 weeks, 6 weeks, and 12 weeks post-op. For lumbar fusion patients, validated instruments like the Oswestry Disability Index (ODI) administered digitally through the RTM platform provide longitudinal functional data that also feeds your MIPS/MACRA quality reporting. Incision monitoring is increasingly included in spine RTM programs through photo submission — patients photograph the incision daily for the first 2 weeks and the clinical team reviews images for signs of dehiscence, infection, or abnormal healing. Early detection of wound complications reduces readmission rates and associated costs. Physical therapy compliance is tracked by integrating RTM data with PT attendance records and home exercise program (HEP) completion logs. Patients who are non-adherent to their PT protocol are identified early enough to intervene — whether that means a motivational call, scheduling adjustment, or clinical escalation. Document every clinical intervention in the patient chart with the date, the triggering RTM data, the action taken, and the outcome.
Billing RTM: Code-by-Code Requirements and Common Errors
CPT 98975 — Initial setup and patient education — is billed once per device type per patient. The 2025 Medicare national non-facility payment rate is approximately $19.50. This code requires documentation that the device was set up, the patient received education on its use, and the patient consented to monitoring. It can be billed in the same month as the first 98977 and 98980 claims. CPT 98977 — Device supply with daily recordings for musculoskeletal monitoring — is billed monthly at approximately $47.00 (2025 Medicare). It requires the 16-day data collection threshold be met. Do not bill 98977 in months where the patient's compliance falls below 16 days — instead, document the non-compliance reason and contact the patient. CPT 98980 — 20 minutes of clinical staff time — is the primary revenue driver at approximately $50.50 (2025 Medicare). This time includes reviewing RTM data, communicating with the patient, and documenting the interaction. Time must be tracked at the individual patient level, and documentation must include the date of service, total time spent, staff member who provided the service, and the clinical activity performed. CPT 98981 — each additional 20 minutes — is billed at approximately $40.50 (2025 Medicare). Complex post-op spine patients — particularly those with multi-level fusions, complications, or comorbidities — frequently generate 40+ minutes of monitoring time per month, making 98981 a regular billing event for this population. Common billing errors include: billing 98980 without documenting time at the individual patient level, billing 98977 in months with fewer than 16 data days, and failing to verify that the ordering provider has an established patient relationship before billing RTM codes.
Revenue Math: What RTM Is Worth Per Spine Patient
Let's calculate the per-patient RTM revenue for a standard lumbar fusion patient monitored for 90 days (3 months) post-operatively using 2025 Medicare rates. Month 1 (first post-op month): 98975 (setup, billed once) = $19.50 + 98977 (device supply) = $47.00 + 98980 (first 20 min) = $50.50 + 98981 (additional 20 min, assuming 40 total minutes for complex patient) = $40.50. Month 1 total = $157.50. Month 2: 98977 = $47.00 + 98980 = $50.50 + 98981 = $40.50. Month 2 total = $138.00. Month 3: 98977 = $47.00 + 98980 = $50.50. Month 3 total (assuming monitoring needs decrease) = $97.50. Total per-patient RTM revenue over 90 days: approximately $393. For commercial payers, rates are typically 115–140% of Medicare, pushing the per-patient total to $450–$550. A spine practice performing 20 lumbar fusions per month (240 annually) that enrolls 70% of eligible patients in RTM generates approximately: 240 × 0.70 = 168 enrolled patients × $393 average = $66,024 in annual RTM revenue at Medicare rates, or $75,600–$92,400 at commercial rates. For practices performing higher volumes or billing at higher commercial rates, RTM revenue can exceed $150,000 annually. These figures do not include the downstream revenue from avoided readmissions (average DRG readmission cost to the practice in quality penalties and rework: $3,000–$8,000 per event) or improved MIPS scores.
Clinical Staff Workflow: Who Does What and When
A well-functioning spine RTM program does not require significant physician time — the clinical model is built around medical assistant or RN-level staff performing the majority of monitoring activity under the supervision of the treating surgeon. The workflow operates as follows. Daily (MA or RN): Log into the RTM platform dashboard, review flagged patients (those with alert threshold breaches), and contact flagged patients by phone or secure message. Document the contact, the patient's status, and any recommendations in the EHR. Flag cases requiring surgeon review. Weekly (RN or Care Coordinator): Review all active RTM patients for trends — patients whose pain scores are not improving on expected trajectory, patients with low activity levels suggesting PT non-compliance, patients with wound photo submissions showing concerning findings. Generate a weekly summary for surgeon review. Monthly (Billing or MA): Pull compliance reports from the RTM platform, verify 16-day threshold is met for each patient before submitting 98977, calculate total time logged for each patient, bill 98980 and 98981 accordingly, and audit a 10% sample of documentation for completeness. The surgeon's role is limited to: (1) reviewing escalated cases flagged by staff, (2) approving clinical orders or medication adjustments triggered by RTM data, and (3) signing off on monthly RTM reports as the supervising provider. Physician time on RTM should average 2–5 minutes per patient per month for routine cases. The billing codes do not require physician time — they require clinical staff time under the physician's general supervision for 98980/98981.
Payer Coverage and Compliance: What Spine Practices Need to Know
Medicare coverage for RTM codes 98975–98981 is established through the CMS Physician Fee Schedule and does not require prior authorization. However, Medicare does require that the ordering provider have an established patient relationship — defined as at least one prior E/M service — before RTM codes can be billed. For spine surgery patients, the pre-operative surgical consultation satisfies this requirement. Commercial payer coverage for RTM varies significantly as of 2025. Major payers with confirmed RTM coverage policies include: Aetna (covers RTM for musculoskeletal conditions, requires documentation of device compliance), Cigna (covers RTM under their behavioral and physical health technology policy, requires prior authorization for some plans), and UnitedHealthcare (covers RTM per their Remote Monitoring policy, 98975–98981 covered for musculoskeletal indications). BCBS coverage varies by state affiliate — many Blue plans now cover RTM, but some require a separate authorization. Before enrolling any commercial patient in a billable RTM program, verify coverage with the patient's specific plan and benefit year. Compliance documentation requirements for RTM are stricter than most practices expect. CMS has signaled increased audit activity for RTM codes, and the documentation must support: (1) the patient's consent to monitoring, (2) the device's compliance data showing 16-day threshold, (3) a time log for each billing date for 98980/98981 with staff identity and activity description, and (4) the clinical rationale for continued monitoring each month. Practices using clinIQ's RTM module generate these compliance reports automatically, eliminating the manual documentation burden and audit risk.
clinIQ for Spine Surgery
clinIQ's RTM module automates enrollment, compliance tracking, and billing for post-op spine surgery patients — turning monitoring into recoverable revenue.
Learn More