Discover the world’s most extensive home exercise library.
Explore remote therapeutic monitoring and billing solutions for your clinic
Measure, benchmark, and improve patient outcomes.
Empower patients with tools to support their recovery.
Customized patient mobile experience under your own clinic brand.
The solution that organizes your patient activities, from triage to discharge.
A step-by-step guide to implementing RTM in a physical therapy practice, platform selection, team ownership, workflow design, and billing setup.
RTM offers real clinical and financial value for physical therapy practices, but the rollout is where most programs succeed or stall. The gap between clinics running strong RTM programs and clinics running weak ones is almost never about the technology, it’s about how the implementation was designed.
A good rollout answers three questions upfront: who owns each part of the workflow, how RTM integrates into existing clinical operations, and how billing readiness gets built into daily work rather than reconstructed at month-end. Get those right, and the program tends to run cleanly at any scale. Skip them, and the workflow tends to compound problems as caseload grows.
Platform selection is the foundation of everything else in the rollout. The wrong platform makes every downstream decision harder, workflow design becomes a workaround, tracking gets manual, documentation runs on parallel systems. The right platform absorbs most of the operational complexity RTM would otherwise generate.
A few evaluation criteria matter more than the marketing pages suggest. Whether the platform meets FDA regulatory requirements for RTM. Whether it tracks monitored days and management time against the 2026 CPT code thresholds automatically. Whether it captures consent and documentation as part of enrollment rather than as a separate step. And whether it integrates with the EMR the practice already uses, so RTM stays tied to the plan of care rather than sitting as a separate data silo.
Platforms built specifically for rehab fit PT workflows better than general remote monitoring platforms adapted for therapy, the underlying design accounts for home exercise programs, plans of care, and adherence tracking rather than physiological data collection. That distinction shows up quickly once the program is running: rehab-specific platforms tend to feel like extensions of existing clinical work, while general platforms tend to feel like translations.
RTM involves three kinds of work that each need clear ownership: clinical work (data review, patient communication, plan of care adjustments), operational work (patient enrollment, consent capture, onboarding logistics), and billing work (threshold tracking, claim submission, denial follow-up). Trying to hand every part of RTM to the treating PT tends to burn out therapists and slow adoption, one of the most common reasons early programs stall.
A scalable ownership model works across clinic sizes. Clinicians own enrollment decisions, clinical data review, and management time. Front-desk or clinic operations staff own onboarding logistics and consent capture. Billing teams own threshold verification and claim submission. The specific pattern adapts to clinic scale, but the underlying principle stays consistent: distribute the workflow across roles where possible, so RTM doesn’t compete with clinical time.
Worth flagging for practices thinking about long-term ownership decisions: CMS has released a CY 2027 proposed rule that would only allow payment for RTM services when performed by clinical staff employed by the practice, not by contractors. This is a proposed rule, not final, and details will likely shift during the comment period. But the direction it signals reinforces the in-house ownership pattern already recommended here, practices building their RTM staffing model around employed clinical staff are positioning themselves for the direction of travel, while practices relying on contracted RTM delivery may need to adjust if the rule finalizes.
Not every patient needs RTM. Enrolling patients who won’t engage produces neither clinical value nor billable activity, and the operational overhead of managing a low-engagement patient costs more than it earns. Selective enrollment in the first few months tends to produce meaningfully better outcomes than the “everyone gets RTM” approach.
A few features make a patient a good RTM candidate: an active plan of care, a treatable condition that produces monitored data over time (post-surgical recovery, orthopedic rehab, chronic pain, longer recovery arcs), the ability to use the monitoring platform (or a caregiver who can), and a plan of care extending long enough to justify the setup work, short episodes rarely produce enough data for RTM to add clinical or financial value.
Clinics often over-enroll early and then discover most of those patients don’t engage. A more selective approach in the first month or two, focusing on 15 or 20 well-selected patients rather than 50 or 60 marginal ones, tends to produce better outcomes, cleaner billing, and a workflow that’s ready to scale when enrollment volume increases later.
The operational move that separates strong RTM programs from weak ones happens at enrollment. Programs where enrollment is an afterthought tend to see eligible patients leave appointments unenrolled, not because anyone objected, but because no one owned the ask. Programs where enrollment is a defined touchpoint owned by a specific team member see enrollment rates that support the program’s long-term math.
A working enrollment flow includes identifying eligible patients during the initial PT evaluation, documenting the clinical need for RTM as part of the plan of care, capturing consent at that point, delivering substantive patient education on how the platform works and what the patient’s role in the program looks like, and confirming the patient can use the platform before they leave the appointment. This is the setup work that determines whether the rest of the program actually runs.
The important reframe: RTM should run alongside prescribed in-clinic care, not replace it. Patients enrolled at evaluation continue attending their scheduled clinic visits while RTM captures what’s happening between them. As visits taper toward discharge, RTM supports the transition from active in-clinic care to independent home exercise program management, a distinct pattern from treating RTM as a post-discharge handoff.
Once patients are enrolled, the ongoing clinical work of RTM starts, reviewing transmitted data on a defined cadence (weekly is common), tracking adherence trends and patient-reported symptoms, and adjusting home programs when the data shows the plan of care needs to shift. This is where RTM actually produces clinical value, and where the code structure was designed to compensate for the work.
A distinction most implementation guides miss: the monitored days that trigger device supply billing (CPT code 98985 for 2–15 days of MSK data in 30 days, or 98977 for 16+ days) reset on a rolling 30-day period from patient enrollment, while management time codes (CPT code 98979, 98980, and 98981) reset by calendar month. The monitoring cadence has to be visible against both timelines simultaneously, which is where manual tracking tends to break down at any meaningful scale. The platform should surface patients approaching threshold transitions so clinical decisions about re-engagement happen consciously, not by accident at the end of the billing period.
RTM communication is the between-visit work that makes the program clinically meaningful: check-ins, messages, program adjustments, and phone or video conversations that respond to what the transmitted data shows. This is where the management time codes live, and where documentation discipline matters most, because reconstructed time logs are one of the highest audit-risk patterns in RTM billing.
What qualifies as interactive communication under CMS guidance is specific: a real-time synchronous audio or video interaction (phone calls, telehealth visits), or in-person time discussing RTM data and program modifications when clearly documented as occurring outside other billable in-clinic therapy services. What doesn’t qualify as interactive communication but still counts toward management time: texting and emailing with patients, which can be included in the monitoring and management time tally but don’t satisfy the interactive communication requirement on their own.
Communication workflows work best when they’re integrated into existing PT touchpoints rather than layered on top. A therapist who reviews RTM data before each patient’s next visit brings that data into the conversation naturally. A therapist who reviews it in a separate weekly block generates a parallel process that tends to fragment over time. The integrated approach also captures more billable management time cleanly, because the clinical thinking is already happening as part of the plan-of-care work.
Billing readiness sits at the end of the workflow but has to be designed from the beginning. Consent capture verified before submission. Monitored days confirmed against the correct device supply code. Management time documented in real time (minutes and seconds, not rounded estimates). CQ or CO modifiers applied when a PTA or OTA delivered the work under general supervision, noting that these modifiers apply only to the management time codes (98979, 98980, 98981), not to the device supply codes (98977, 98985), which are excluded from the modifier requirement.
The six-code system PT practices will use: CPT code 98975 (Initial RTM setup and patient education, once per episode of care), CPT code 98985 (RTM device capturing 2–15 days of MSK data in 30 days), CPT code 98977 (RTM device capturing 16+ days of MSK data in 30 days), CPT code 98979 (10–19 minutes of RTM treatment-management time), CPT code 98980 (20 minutes of RTM treatment-management time), and CPT code 98981 (each additional 20 minutes of RTM treatment-management time). The 2026 RTM CPT code overview walks through each code’s requirements in depth.
A few predictable errors show up in the first three months of a new RTM program. Over-enrolling patients who won’t engage, leading to a program that looks bigger on paper than it produces in practice. Treating enrollment as informal rather than owned by a defined team member, leading to eligible patients leaving appointments unenrolled. Letting the treating PT absorb every part of the workflow, leading to therapist burnout and inconsistent execution. Reconstructing time logs at month-end instead of capturing them as work happens, leading to documentation that doesn’t hold up under audit.
Clinics often skip substantive patient education at setup, submitting 98975 with vague documentation that describes what was covered generically rather than what was actually taught and confirmed. The setup work is the foundation of the rest of the program’s audit trail, a thin setup note weakens every subsequent claim in the episode.
The biggest predictor of a program’s long-term success isn’t the initial launch enthusiasm; it’s whether the operational infrastructure holds up in month four, when the novelty has worn off and the workflow is running against real caseload pressure. Programs that survive that month tend to run cleanly for years.
PT owners raise a real concern about RTM: it sounds good on paper but adds work in practice, especially when the treating PT is asked to also handle enrollment, monitoring, communication, and billing coordination for every patient. If that’s how the program is structured, the concern is justified, no clinician can sustainably add all of that on top of a full caseload.
The honest answer is that RTM does add work, but the burden is a design problem, not an inherent feature. Clinics that distribute the workflow across roles, with the platform absorbing threshold tracking, documentation, and modifier application, report meaningfully lower therapist burden than clinics running everything through the treating PT. Manual tracking creates the burden that gets attributed to RTM itself, when in reality it’s the tracking method, not the program, that’s generating the burden. Programs that stop treating RTM as a therapist’s responsibility and start treating it as clinic infrastructure tend to see the burden question resolve on its own.
An RTM implementation actually looks like a six-month arc in most successful cases. Month one: launch with a small, well-selected patient cohort of 10–20 patients. Months two and three: stabilize the workflow, catch operational patterns that need adjustment, refine ownership and enrollment. Months three through five: expand enrollment as the team gains confidence and the workflow proves out. Month six and beyond: add multi-location or multi-clinician layers once the core operational patterns are working reliably.
The operational milestone most programs miss is the point at which manual tracking stops working. Clinics running RTM at 40 patients often function fine on spreadsheets and reconstructed logs; the same workflow breaks at 100 or 200 patients because the manual layer can’t scale. Programs that plan for that transition from the beginning, by starting on infrastructure that handles automated threshold tracking, documentation, and modifier application, avoid the painful re-platforming that clinics running manual RTM eventually face. Understanding the reimbursement math and revenue potential across an engaged patient panel makes the infrastructure case clearer.
Wibbi structures RTM around the implementation realities described above. Enrollment workflows that build consent and patient education into the intake process, real-time monitored-day tracking against the 98985 and 98977 thresholds, management time logging with CQ and CO modifier application handled at the practitioner level (applied only where the modifiers actually apply), and audit-ready documentation prepared as work happens, not reconstructed at month-end. Built specifically for rehab RTM, integrating with the rehab EMRs PT practices already use, and running the same way for a physical therapy RTM program as it does across the broader rehab disciplines Wibbi supports.
A successful RTM rollout isn’t defined by the platform choice alone, it’s defined by clear ownership of every workflow step, disciplined patient selection, real integration into existing clinical operations, and a platform that absorbs the operational complexity that would otherwise fall on the therapists.
What to look for in the first 90 days of a new program: consent captured cleanly for every enrolled patient, monitored days tracked in real time against the correct code thresholds, management time documented as work happens rather than reconstructed at month-end, and CQ or CO modifiers applied correctly when assistants deliver the work under general supervision on the management time codes. Programs that hit those four markers in the first three months tend to run cleanly at scale. The details will vary by practice size, patient population, and clinical workflow, but the underlying structure of a good implementation is consistent across settings.
