RTM and HEP for Workers' Compensation and Occupational Injury Claims
TL;DR
- A patient telling an adjuster "yes, I did my exercises" carries no evidentiary weight in a workers' comp file. Claims and return-to-work decisions turn on documentation, and paper HEP logs rarely provide it.
- RTM adherence data closes that gap with objective records: session completion, sets and reps logged, pain and difficulty ratings, and milestone alerts tied to functional benchmarks a case manager can act on.
- Workers' comp billing diverges from Medicare's RTM framework. State fee schedules, timely filing windows, and payer authorization rules vary, so RTM CPT codes 98975, 98977, 98980, and 98981 don't apply the same way across payers.
- Evaluate a platform on multi-discipline support for PT and OT, Epic integration for hospital-based programs, and claims-ready reporting rather than a generic clinical dashboard.
Why self-reported exercise compliance fails workers' comp claims
A workers' comp claim moves toward resolution on documentation, not on a patient's word. When an injured worker tells a treating clinician "yes, I did my exercises," that statement carries no evidentiary weight with an adjuster or a utilization review nurse deciding whether to authorize continued care or clear a return-to-work milestone. The decision-maker needs a record they can defend, and a verbal report leaves nothing in the file.
From the adjuster's seat, the problem is specific. To close a claim or approve the next phase of treatment, they need proof that the worker is following the prescribed program and improving against functional benchmarks. A paper home exercise log fails that test on two fronts. It records what the worker chose to write down, often days after the fact, and it offers no way to verify that any session actually happened. A checkmark on a photocopied sheet tells an adjuster nothing about frequency, intensity, or whether pain trended down over three weeks.
Case managers face the same evidentiary gap when they coordinate between the clinic, the employer, and the payer. They chase the clinic for status updates, wait for a progress note that summarizes the clinician's impression, and still cannot see the underlying adherence pattern that would justify or challenge an RTW decision. Self-report and clinician summary both filter the data through someone's judgment before it reaches the file. That filtering is exactly what a payer disputes when a claim stalls.
Objective adherence data closes the gap by capturing what the worker did, when they did it, and how they rated it, without depending on memory or manual logging. Remote therapeutic monitoring records session completion, the sets and reps a worker logs during a session, and pain and difficulty ratings entered at the point of exercise. Home exercise program completion records timestamp each session as it occurs. Together they produce a longitudinal, time-stamped account of functional progress that an adjuster or case manager can read directly. How that data is billed and structured for a claims workflow is where the mechanics get specific.
RTM CPT codes in workers' comp billing vs. Medicare
Remote therapeutic monitoring runs on a small set of CPT codes, and they behave differently once a workers' comp payer sits at the other end instead of Medicare. Code 98975 covers the initial setup and patient education on the monitoring device, billed once per episode. Code 98977 covers the device supply and data transmission for musculoskeletal monitoring across a 30-day period, and it requires at least 16 days of recorded data in that window. Codes 98980 and 98981 cover the treatment management time a clinician spends reviewing data and communicating with the patient, billed in the first 20 minutes and each additional 20 minutes per calendar month. CMS's 2026 update added two lower-threshold codes alongside these: 98985 covers device supply and data transmission for 2 to 15 monitored days in a 30-day period, and 98979 covers the first 10 to 19 minutes of treatment management in a calendar month. A claim bills either the higher-threshold code or its lower-threshold counterpart, not both, so clinics should map whichever pair fits the actual monitoring and management time logged for that patient.
Medicare publishes national valuations and a single set of documentation rules for these codes. Workers' comp does not work that way. Each state sets its own fee schedule, so the reimbursement for 98977 in California can differ sharply from the same code billed in Texas or Florida. Some states adopt Medicare rates as a reference point, while others maintain independent schedules or leave RTM codes unpriced entirely, which forces case-by-case negotiation with the payer.
Timely filing is the second place workers' comp diverges. Medicare gives you a full year to submit a claim. Workers' comp payers often impose much shorter windows that vary by state and sometimes by individual carrier, and a late RTM claim gets denied regardless of how clean the underlying data is. Because RTM codes bill on monthly cycles, a clinic that treats the filing deadline the way it treats Medicare will miss it.
Authorization is the third difference, and it is the one clinics underestimate. Medicare does not require prior authorization for RTM. Many workers' comp payers do, and utilization review can reject monitoring that was not approved before it started. Billing 98975 on a claim where RTM was never authorized produces a denial and an unpaid setup cost. You have to confirm coverage and authorization per claim, not assume the code is payable because it was payable last month on a different carrier.
Physitrack's real-time CPT eligibility tracking helps clinics stay accurate against these moving rules. The platform tracks the day count toward the 16-day threshold for 98977 and the accumulated management minutes for 98980 and 98981, so a clinician knows when a code has actually met its billing requirement rather than guessing at month-end. That timing matters more in workers' comp than in Medicare, because a code billed one day early against a payer with a strict filing window and a specific authorization on file leaves less room to correct the error. Tracking eligibility as data accrues keeps the claim submittable within the window the payer allows.
What objective data actually moves a claim or RTW decision
Four data types carry actual evidentiary weight in a claim file, and each answers a question an adjuster or utilization reviewer will otherwise ask the clinic. Session completion shows whether the injured worker started and finished the prescribed program. Sets and reps logged confirm the worker did the actual work volume, not a shortened version of it. Pain and difficulty ratings recorded at each session trace the trajectory of recovery over time. Milestone alerts tied to functional benchmarks flag the moment a worker reaches a threshold that supports a return-to-work decision.
Collected data and actionable data are not the same thing, and the difference decides whether a case manager can move a file. Many home exercise tools record activity inside a clinician dashboard that only the treating clinic can see. When a case manager needs proof of adherence, they email or call the clinic, wait for a summary, and hope the numbers arrive before the timely filing window closes. Data trapped behind that request loop slows the claim even when the underlying compliance is strong.
Exportable data removes the request loop. A case manager who can pull a report showing session completion, logged volume, and pain trend over eight weeks has the documentation to advance or close the file without chasing the clinic. The same report supports an RTW decision because it shows the worker meeting functional benchmarks rather than asserting they feel better.
Physitrack builds adherence data into claim-file evidence through milestone alerts and exportable reports. Milestone alerts fire when an injured worker hits a functional benchmark the clinician set, so the treating team and the case manager learn about RTW readiness at the same moment rather than at the next scheduled review. Exportable reports package session completion, sets and reps, and pain and difficulty ratings into a document a payer or case manager can act on directly. That combination turns weeks of logged home exercise into the objective record a claims workflow runs on, and it keeps the injured worker's progress visible to everyone deciding the claim.
Employer and payer compliance reporting for multi-site programs
An occupational health program running across ten clinic sites produces ten different versions of the same report unless the reporting format is fixed at the platform level. A hospital-based site might export a PDF with pain scores, a satellite clinic might send a spreadsheet of session counts, and the employer or payer receiving both has no consistent way to compare injured-worker progress across locations. Standardized roll-up reporting solves this by defining the same fields, the same milestones, and the same export structure for every site, so an employer's benefits team or a payer's utilization reviewer reads one report and understands it regardless of which clinic generated it.
Roll-up reporting for this audience needs three things. It needs per-worker adherence and functional progress that maps to the same benchmarks across every site. It needs aggregation, so a program manager can see caseload status for one employer's injured workers without opening ten separate dashboards. And it needs exports formatted for a claims or benefits workflow rather than a clinical chart, because the person reading it is adjudicating a file, not treating a patient.
Physitrack builds reporting for this cross-site reality rather than for a single clinic. Because the platform covers both physical therapy and occupational therapy in one exercise library and one adherence record, a multi-site program using both disciplines reports on them through the same structure instead of stitching together separate tools. Adherence data, milestone status, and functional progress export in a consistent format across every location, which gives the employer or payer a single, comparable view of the whole population under care.
That consistency matters most when a program spans acute hospital departments and community satellite clinics under one contract. A generic HEP dashboard shows one clinician one caseload, which is the wrong unit of visibility for a program manager answering to an employer. Physitrack's reporting is scoped to the program, so the person accountable for return-to-work outcomes across sites sees the same evidence the treating clinicians logged, without chasing each location for its own version of the numbers.
What to evaluate in an RTM/HEP platform for workers' comp
Four criteria separate a platform that can carry a workers' comp claim from a generic exercise app. Score any vendor against these before you commit an occupational medicine program to it.
Multi-discipline coverage for PT and OT
Injured-worker rehabilitation rarely stays in one discipline. A shoulder claim moves from physical therapy strengthening into occupational therapy work-conditioning and simulated job tasks, and your platform needs a library and adherence model that follows the worker across both. A PT-only tool forces your OT staff into workarounds or a second system, which fractures the claim file. Confirm the exercise library and RTM tracking cover PT and OT under one record, so a case manager sees one continuous history rather than two disconnected ones.
EHR integration for hospital-based programs
Hospital-based occupational health programs run inside an existing electronic health record, and an RTM tool that lives outside it creates double documentation your clinicians will resent and eventually abandon. Epic integration matters most here, because it lets adherence data, prescribed programs, and session logs flow into the same chart your treating clinicians already use. Ask whether the integration is live and bidirectional, or a roadmap promise, before you weigh it in a decision.
Reporting built for a claims workflow
A generic clinical dashboard shows a clinician how one patient is trending. A claims workflow needs something different. It needs exportable, standardized reports a case manager or adjuster can pull without emailing the clinic for updates. Evaluate whether the platform exports adherence and milestone data in a format a payer can act on, and whether reporting rolls up consistently across sites rather than requiring you to reconcile mismatched formats by hand.
Data governance and certifications
For multi-site procurement, trust in how the platform handles patient data decides whether it clears review at all. Injured-worker health data crosses clinics, employers, and payers, so information security has to be verifiable rather than asserted. Look for independent certification against recognized standards rather than a vendor's own assurances.
How Physitrack measures against each
Physitrack covers PT and OT in one multi-discipline library, so a claim that moves from strengthening into work-conditioning stays in a single record. Its Epic integration puts RTM and HEP data into the chart hospital-based occupational health teams already work in. RTM adherence, milestone alerts, and CPT eligibility export as billing and compliance reports a case manager can use directly, and reporting stays consistent across locations rather than per-clinic. On governance, Physitrack holds ISO 27001 for information security and ISO 13485 for medical device quality management, which give procurement teams a verifiable trust anchor rather than a self-reported claim.
Comparison: what a claims-ready RTM/HEP platform needs
A claims-ready platform does five things a generic home exercise builder does not. Generic tools log that a patient opened the app. Claims work needs proof of what the patient did, exported in a form a case manager can act on.
Physitrack covers every row above. Use this table alongside the evaluation criteria, not as a substitute for scoring vendors against your own payer mix and site count.
FAQ
What does CPT code 98975 require? CPT 98975 covers the initial setup and patient education for remote therapeutic monitoring, billed once per episode of care. A clinician must configure the monitoring program and instruct the patient on how to use the device or app. Physitrack logs the setup and enrollment that support this code.
What is the difference between 98977 and 98980? CPT 98977 covers the supply of a device that monitors musculoskeletal system status, requiring at least 16 days of data in a 30-day period. CPT 98980 covers the first 20 minutes of treatment management, including at least one interactive communication with the patient during the month. The two codes measure different things, so a claim can carry both when the thresholds are met. CMS's 2026 update also added 98985 and 98979 as lower-threshold versions of 98977 and 98980, covering 2 to 15 monitored days and 10 to 19 management minutes respectively, for patients who don't reach the higher thresholds in a given period.
What does 98981 add? CPT 98981 bills each additional 20 minutes of RTM treatment management within the same calendar month, on top of the first 20 minutes captured by 98980. You report it in whole 20-minute increments, so partial blocks do not qualify. Physitrack tracks accrued management time so clinics know when a second increment becomes eligible.
How does workers' comp timely filing differ from Medicare? Workers' comp claims run on state-specific fee schedules and filing windows rather than Medicare's national RTM framework, so the same code can pay differently or require prior authorization depending on the state and payer. Some workers' comp payers do not adopt RTM codes at all, or apply their own documentation rules. Confirm authorization and the filing deadline with the payer before you start monitoring, because Medicare's rules do not transfer automatically.
What counts as sufficient documentation for a return-to-work milestone? An RTW milestone needs objective adherence data tied to a functional benchmark, such as logged sets and reps, session completion over time, and pain or difficulty ratings that trend toward the target. A case manager should be able to read the progress against the milestone without calling the clinic for an update. Physitrack's milestone alerts and exportable reports package this evidence in a form an adjuster or payer can act on directly.
Getting started with claims-ready RTM and HEP
A workers' comp claim moves when the file holds objective proof of functional progress, and a return-to-work decision holds up when that proof is exportable and tied to milestones. Self-reported exercise compliance never gives an adjuster or utilization reviewer that evidence. RTM adherence data and HEP completion records do, which is why the platform you choose decides whether your clinicians spend their time treating injured workers or chasing documentation.
Physitrack builds this for multi-site occupational health programs, with real-time CPT code eligibility tracking, milestone alerts, a PT and OT exercise library, Epic integration for hospital-based programs, and exportable compliance reports backed by ISO 27001 and ISO 13485 certifications.
If you run an occupational medicine clinic or manage injured-worker rehabilitation across sites, talk to our team about mapping RTM and HEP data to your claims and return-to-work workflow.
