The proposed rule is giving healthcare organizations an opportunity to audit and reveal current risks in their RPM programs.
That is the most useful way to approach the CY 2027 Physician Fee Schedule proposal. CMS has proposed changes involving initiating visits, clinical-staff employment, remote-monitoring valuation, and possible future code restructuring. The comment period closed September 14, but the operational questions remain valuable while the rule is still not final.
Instead of rebuilding a program around a possible outcome, use this planning window to compare the workflow on paper with the workflow patients and staff actually experience.
Start with the real workflow
Most RPM process maps describe the happy path. A patient is identified, enrolled, shipped a device, monitored, contacted when needed, documented, and prepared for billing. Real operations contain waits, exceptions, missing data, after-hours events, and workarounds between systems.
The audit should follow one patient from identification through billing readiness. At every stage, record the owner, backup owner, system of record, required evidence, next handoff, and most common failure point. If three team members describe the process differently, that disagreement is part of the finding.
Twelve questions worth asking
What event makes a patient eligible for the RPM enrollment workflow?
Who confirms that the required initiating step is complete and documented?
What prevents a device from shipping before the program is ready for the patient?
Who confirms delivery, activation, and the first usable reading?
How quickly does the team notice that a patient has stopped transmitting?
What triggers a reminder, which channel is used, and when does a person take over?
Which readings or thresholds require review during business hours?
What is monitored after hours, who receives it, and what is the backup escalation path?
Where are clinical time, interactive communication, notes, and escalations recorded?
Who determines whether the documented activity is ready for CPT-code and claims review?
What happens when evidence is incomplete near the organization’s submission cutoff?
Which workflow depends most heavily on a spreadsheet, inbox, or one person’s memory?
Look for invisible operating work
The most important audit findings are the repeated acts of checking, waiting, reconciling, reminding, routing, and assembling evidence around those decisions.
HHS OIG has continued to focus attention on RPM billing patterns as Medicare use and payments grow. That oversight makes reliable documentation and explainable billing operations more important, not less. The objective is to create a traceable path from patient activity and staff work to a qualified billing review.
The same principle applies to patient engagement. A reminder is a workflow with a trigger, an approved channel, a cadence, a stopping condition, and a point where human judgment becomes necessary.
Audit first, then design automation
Automation should not be the first answer. A team first needs to know which steps should happen consistently and which decisions require context.
At Impilo, we are building and implementing a future operational layer that can watch for missing events, wait across multi-day workflows, route exceptions, trigger approved reminders, and assemble supporting evidence. The aim is not full autonomy. It is to let repeatable coordination run in the background, then bring the right person the patient, context, or decision that needs judgment.
A useful future-state design test is simple: Can the workflow explain what triggered it, which sources it used, which rule it applied, where it stopped for review, and what happened next?
Preparation is operational clarity
RPM leaders do not need to predict the final rule to make progress. They can clarify ownership, close after-hours gaps, improve reminder logic, strengthen documentation flow, and identify work that cannot scale today.
The opportunity is bigger than regulatory readiness. A program that can explain its current operation can adapt faster, automate more responsibly, and give patients a more consistent experience.
Frequently asked questions
What is an RPM operational audit? It is a structured review of how patients, data, staff actions, documentation, and billing evidence move through the program. It compares the intended workflow with the work teams actually perform.
Should an organization change its program now because of the CY 2027 proposal? The proposal is not final. Organizations can use it to identify operating questions and model scenarios, while asking qualified billing, legal, and compliance leaders to interpret potential requirements.
Where should RPM workflow automation begin? Begin with a high-volume, repeatable workflow whose trigger, inputs, rules, human review points, and evidence requirements are clear. Missing-reading follow-up and billing-readiness preparation are useful areas to examine, but the right starting point depends on the program.
