Remote patient monitoring billing just got a shorter runway. As of January 1, 2026, a practice can bill Medicare for a device supply period as brief as two days of transmitted data, down from the 16-day minimum that governed RPM billing for years. That change makes documentation speed and accuracy matter more than ever, and it arrives just months after federal auditors published a detailed map of exactly where RPM billing already goes wrong. Agentic AI is emerging as the tool coding and RCM teams need to close that gap before claims go out the door.
A New CPT Code Cuts the RPM Billing Runway to Two Days
The CY2026 Medicare Physician Fee Schedule final rule, published by CMS on November 5, 2025 and effective January 1, 2026, created CPT 99445 for RPM device supply when a patient transmits data for just 2-15 days in a 30-day period. It’s reimbursed at the same rate as the existing 16-day-or-more code, 99454, and it sits alongside lower time thresholds for treatment management (down to 10-19 minutes) and broader acceptance of audio-only and asynchronous check-ins.
The intent is reasonable: match billing rules to how monitoring actually happens for patients who don’t need a full month of continuous data. But it also means claims can now be submitted, and reviewed, on a much tighter documentation cycle. A coding team that previously had weeks to confirm a patient relationship and a completed treatment management encounter now needs that same rigor compressed into days.
OIG Already Mapped Where RPM Billing Goes Wrong
Compliance teams don’t have to guess where the risk is. The HHS Office of Inspector General’s data snapshot on RPM billing, released August 25, 2025, analyzed 2024 claims and found Medicare RPM payments had reached $536 million, up 31% from 2023. Inside that growth, OIG flagged specific practice-level patterns: 45 medical practices billed for RPM services for more than 80% of their patients despite having no prior medical relationship with them, and 52 practices billed for more than 75% of enrollees who never received the required treatment management encounter. One practice added 3,400 new RPM enrollees in a single month, a growth curve OIG said could reflect legitimate expansion or could be a fraud marker.
None of that requires a new audit to become relevant. It’s a checklist for what a payer or OIG reviewer will look for in any RPM claim, and the new short-duration code only shrinks the window coding teams have to confirm those elements before submission.
Why Manual Documentation Review Can’t Keep Pace
Two specific failure modes drive most of the risk OIG identified, and both are hard to catch by hand at volume.
The Prior-Relationship Trap
Medicare requires an established relationship, through an in-person or telehealth encounter, before a practice can bill for RPM. That fact lives in one system while device transmission data lives in another, and a biller working a claims queue often has no easy way to cross-check the two before submission. At scale, that’s exactly the gap 45 practices in the OIG sample fell into.
The Treatment Management Blind Spot
Treatment management, a clinician actually reviewing the transmitted data and using it to make a care decision, is the part of the RPM code set most often billed without being performed. A note that says data was received isn’t the same as a note documenting that a clinical decision was made from it, and reviewers looking for that distinction one claim at a time miss it constantly.
How Agentic AI Closes the RPM Compliance Gap
Rather than relying on a biller to manually cross-reference a patient’s encounter history, device transmission logs, and clinician notes, an agentic system can check every one of those elements against every claim before it’s submitted, not just a sample. A validation agent built for RPM billing typically works through:
- Relationship verification — confirming a qualifying in-person or telehealth encounter exists in the chart before an RPM claim is allowed to proceed.
- Transmission-day counting — matching the actual number of days of transmitted data against the code being billed, so a 99445 claim isn’t submitted on five days of data that should have waited or been billed differently.
- Treatment management evidence — scanning the clinical note for language showing data was reviewed and used in a care decision, not just received.
- Enrollment pattern flags — surfacing unusual month-over-month enrollee growth at the practice level before it becomes a pattern an external auditor notices first.
- Documentation gap routing — sending claims missing any of the above back to a coder or clinician for completion instead of letting them go out incomplete.
The auditor’s judgment doesn’t disappear in this model. The agent’s job is narrower: make sure every claim gets the same checks a careful reviewer would run, at a volume no manual queue can sustain once the billing cycle shrinks to two days.
What RCM and Coding Teams Should Do Before Year-End
Practices billing RPM under the new short-duration code should treat this as a documentation-timing problem first and a coding problem second. That means confirming the EHR captures a clear, time-stamped treatment management note for every RPM period, not just a system log of data receipt, and making sure whatever coding or RCM technology sits in front of claims submission can actually see both the encounter history and the device data, rather than treating them as separate systems that never get cross-checked before a claim goes out.
That kind of cross-system validation, checking relationship history, transmission counts, and clinical documentation together before a claim is ever submitted, is the exact problem Medikode’s automated medical coding platform is built to solve, giving coding and RCM teams a defensible RPM claim the first time, not after a denial or an audit letter.