For many practices, remote patient monitoring (RPM) became a natural extension of existing chronic care management (CCM) efforts, creating new opportunities to support patients between visits. Like CCM and other remote care services, RPM introduced its own workflows, documentation requirements, and billing rules.
That approach helped practices expand remote care offerings. But it also meant that programs often operated independently, with separate processes and limited coordination between them.
As Medicare explores new ways to pay for care, the future of remote patient monitoring looks less like adding another program and more like connecting the pieces already in place. Practices need to consider how patient data, clinical follow-up, and reporting work together, especially as payment models evolve.
The question is no longer just which service to offer next. It's whether a practice has the people, processes, and technology to support connected care as requirements change.
The First Wave Was Built One Program at a Time
RPM, chronic care management (CCM), principal care management (PCM), remote therapeutic monitoring (RTM), and advanced primary care management (APCM) each have their own requirements. Under fee-for-service, Medicare generally pays for eligible services when a practice meets the applicable billing and documentation rules. For many practices, this will remain an important part of the business.
The challenge comes when each program operates on its own.
Patient readings may sit in a separate portal. Staff may be unsure who should respond to an alert or how quickly they need to act. Follow-up can happen outside the EHR, leaving gaps in the patient record. And even when a practice delivers the service, it may not have a clear picture of whether the patient's health is improving.
These gaps become harder to manage as enrollment grows. Staff spend more time coordinating care, clinicians have less visibility into what's happening between visits, and practice leaders struggle to demonstrate the value of their programs.
The issue isn't a lack of billing codes. It's whether the care process behind them works as a whole.
Outcomes Are Becoming the Scoreboard
Some of the most important remote patient monitoring trends are tied to a broader shift in healthcare payment: measuring results, not just the services delivered.
CMS is testing payment models that put greater emphasis on patient outcomes. The ACCESS Model, a voluntary model that began in July of 2026, ties payment to measured results for chronic conditions rather than to the volume of services delivered. Depending on the condition, outcomes may include measures such as blood pressure, A1c, weight, and physical function.
The Ambulatory Specialty Model (ASM) is scheduled to begin in January 2027 for selected specialists, initially focusing on heart failure and low back pain. It connects payment to the quality and cost of care over an episode.
Not every practice will participate in these models, but both illustrate a change in how healthcare organizations may be evaluated: what happens to patients matters, not just how many services a practice provides.
For practice leaders, that affects how success is measured. Enrollment and monitoring activity still matter under fee-for-service. But when payment depends more directly on outcomes, practices also need to track clinical improvements, close care gaps, and understand what's happening between appointments.
A patient reading, for example, is only part of the picture. What matters is whether someone reviews it, responds when needed, documents the intervention, and follows up to see what changed.
Fee-for-service isn't disappearing, and many practices will likely work across multiple payment models. The challenge is supporting different reimbursement requirements without creating a separate care process for every program.
Reporting Needs to Be Part of Everyday Care
Quality reporting has often been periodic. Collect the data, complete the submission, send it in. The newer models ask for something more continuous. According to CMS, ACCESS participants report outcomes electronically through FHIR-based APIs, and CMS plans to publicly report risk-adjusted outcomes so that patients and clinicians can see how participants perform.
Flexibility Matters More Than Ever
Remote patient monitoring reimbursement and other payment rules will continue to evolve. New codes may be introduced, existing requirements may change, and emerging models may bring different quality measures or reporting expectations.
Each change can affect staffing, documentation, billing, and daily workflows. For a practice focused on patient care, continually rebuilding these processes can quickly become a burden.
That's why flexibility matters. Rather than building an operation around a single program's requirements, practices need a way to adapt as those requirements change.
Some organizations have the internal resources to monitor policy updates and manage changes themselves. Others may prefer to work with an outside partner that can help manage the operational side of remote care. Neither approach is right for every practice. What matters is having a clear plan for who tracks changes, updates workflows, and makes sure the practice is ready to respond.
One question can help clarify whether that plan is realistic: If the rules change next year, who will make the necessary adjustments, and how quickly can they happen?
Keep Your Options Open
Decisions about technology often outlast the programs that prompted them.
A practice might start with RPM, add CCM or other services, and eventually participate in a payment model that didn't exist when the original program launched. It might also change EHRs somewhere along the way.
If remote care depends entirely on a single EHR's built-in module, that product's capabilities and development plans may limit the practice's options. Switching systems or expanding into new services can become more complicated than expected.
EHR integration still matters. Clinicians need relevant patient information in the systems they already use, and asking staff to enter the same information twice adds unnecessary work.
The key is to make sure the integration supports the care workflow without limiting what the practice can do next. Capabilities vary by EHR, so it's worth asking specific questions: What patient data can be exchanged? Which readings or events trigger follow-up? How are interventions documented? What information makes its way back into the patient chart?
Clear answers help practices understand what an integration supports today and where they may need additional capabilities as their programs grow.
What Does Readiness Look Like?
No one can predict exactly how remote care or Medicare payment models will develop. Fortunately, practices don't need to anticipate every change to prepare for it.
A good starting point is to assess the fundamentals:
- Know your patient population. Which conditions, payers, and patient needs are you serving, and which care pathways make the most sense?
- Define ownership and follow-up. When a reading comes in, who reviews it, what protocol guides the response, and how quickly does action need to happen?
- Connect care to the EHR. Can patient information move between remote care tools and the EHR without creating duplicate work?
- Measure what matters. Which clinical, operational, and financial metrics do you track, and who is responsible for acting on them?
- Understand your reimbursement requirements. How is the work paid for today, and what additional outcomes or documentation might another model require?
Together, these questions help practices see how their remote care operations fit together. Patient data leads to action, that action is documented, and the results help guide future care decisions.
It's also important to measure performance before expanding a program. Adding more patients doesn't automatically mean better outcomes or a stronger business case. Practices need to understand whether their workflows are effective and sustainable before increasing enrollment.
Build for What Comes Next, Not for the Next Code
RPM helped expand the possibilities for care beyond the exam room. Now, the opportunity is to connect monitoring, clinical follow-up, and multiple care programs in ways that work for both patients and the teams supporting them.
The future of connected care won't be defined by a single code or payment model. It will depend on how well practices coordinate care, track meaningful results, and adapt as requirements change.
That means having workflows that support timely follow-up, documentation that makes reporting easier, and technology that can work across programs without creating more administrative work. It also means making sure remote care works alongside the EHR and other systems the practice relies on, rather than becoming another disconnected tool.
The programs and payment rules may change. The need to deliver coordinated care and understand its impact on patients will remain.
Want to see how CoachCare connects remote care with the EHR your practice already uses? Explore CoachCare’s EHR integrations to learn which capabilities are available for your system.
