A billing team should not have to reconstruct an RPM program at the end of the month. Yet that is exactly what happens when device activity, staff work, communication, notes, and exceptions live in separate tools or depend on individual memory. By the time the gap appears, the people closest to the event may no longer remember the context.
The scale of RPM makes this more than an administrative inconvenience. HHS OIG reported that Medicare RPM payments exceeded $500 million in 2024 and continued to call for additional oversight. In an earlier review, OIG found that 43% of Medicare enrollees receiving RPM did not receive all three components it examined. These findings do not tell a practice whether a particular service is billable, but they reinforce the need for transparent, consistent operations.
CMS’s CY 2027 Physician Fee Schedule proposal adds another reason to inspect the workflow. As of mid-October, the policy remains proposed, and CMS had requested comment on multiple RPM and RTM payment issues. Teams should monitor the final rule and work with qualified billing and compliance experts. They can also improve operational readiness now without predicting the final outcome.
Define Readiness Without Making a Billing Determination
Billing readiness means the operating record is complete, traceable, and organized for qualified review. It does not mean a workflow engine, dashboard, or checklist has decided that a claim should be submitted. Keeping that boundary clear helps operations teams improve the inputs while preserving appropriate coding, billing, and compliance judgment.
A useful readiness checkpoint asks whether the record tells a coherent story: what activity occurred, what work was performed, what communication happened, what clinical or operational action followed, and whether any exception remains open.
Connect Five Evidence Streams
Device and reading activity. The team should be able to view relevant activity in context and identify missing or inconsistent patterns early enough to investigate.
Staff work. Approved workflows should make staff activity visible without requiring duplicate entry or a separate end-of-month reconstruction.
Interactive communication. The record should allow a qualified reviewer to trace when and how communication occurred, according to the organization’s policies and applicable requirements.
Notes and escalations. Documentation should explain the action, disposition, and handoff. A threshold event without a visible next step leaves an incomplete operational story.
Open exceptions. Missing information needs a named owner and a next action. An exception queue is useful only when the team knows who resolves each item and when it returns for review.
Run Readiness Checks Throughout the Month
The highest-value check often happens before the deadline. A weekly review can surface missing records while the context is fresh and the appropriate teammate can still respond. It can also reveal recurring failure patterns: one device type creates extra support work, one handoff repeatedly loses context, or one communication step is documented inconsistently.
Start with one narrow checkpoint. Select a small sample of de-identified records and ask whether a reviewer can follow each stream without opening multiple spreadsheets or messaging the care team. Track why items are returned. The reasons become the improvement backlog.
Use Automation to Surface Gaps
Automation can flag missing activity, route an exception, track an unresolved item, and assemble records for review. It can reduce the manual work of finding evidence. It should not silently convert an incomplete record into a complete one or replace the qualified reviewer responsible for billing and compliance decisions.
Impilo’s RPM infrastructure tracks monthly RPM CPT code billing thresholds, tracks monthly live contact with patients, and gives the team visibility on patient interactions and clinical notes. That connected view can make readiness work part of normal operations instead of a separate month-end rescue.
Prepare the Operation, Even While Policy is Unsettled
A proposed rule can change. A strong operating discipline still creates value. If final policy requires a workflow adjustment, a team with clear evidence streams, owners, and checkpoints can identify the affected step and adapt it deliberately. A team that cannot trace the current process has to discover the operation before it can change it.
This week, choose one readiness checkpoint to move upstream. Ask what should be visible, who resolves an exception, and when the item is ready to return for qualified review. The goal is not to forecast a claim. It is to make the program easier to understand, govern, and improve.
FAQ
What does RPM billing readiness mean? It means the operational record is organized and traceable for review by qualified billing and compliance stakeholders. It is not itself a bill-ability decision.
How often should an RPM team review readiness? The right cadence depends on volume and workflow, but a weekly checkpoint can identify gaps while the underlying context is still current. Higher-volume programs may use continuous exception monitoring.
Can automation determine whether an RPM service should be billed? Automation can surface missing information, like when patients aren't going to meet the monthly reading thresholds. Automation can also trigger reminders for patients who are close to meeting that billable threshold. Organizations should still preserve qualified human review for coding, billing, compliance, and unusual exceptions.
