The Rural Patient Monitoring (RPM) Access Act would adjust Medicare’s RPM payments by adding a floor to the practice expense and malpractice geographic indices, with a concrete minimum starting January 1, 2026. It also imposes new quality requirements on RPM providers, including anomaly response, Vitals and treatment-note transmission to supervising clinicians’ electronic health records, and data reporting to support CMS cost-savings analysis.
The bill includes small-practice exemptions and requires a congressionally mandated report within two years to evaluate savings from RPM, medication adherence, and related practice expenses. The overall aim is to improve care for rural Medicare beneficiaries who rely on RPM while giving CMS the data needed to assess effectiveness and costs.
At a Glance
What It Does
Adds a floor of 1.00 to RPM practice expense and malpractice geographic indices for payments starting in 2026. Establishes RPM quality requirements for providers, enables anomaly-response capabilities, and requires data transmission and reporting to support cost-savings analyses. Defines RPM and provides small-practice exceptions.
Who It Affects
Medicare RPM providers and supervising clinicians; rural health clinics and hospitals that offer RPM; Medicare beneficiaries in rural areas who rely on RPM; RPM platform vendors.
Why It Matters
Sets payment realism for RPM in rural areas and creates enforceable quality standards. The data requirements will enable CMS to quantify savings and guide future policy on RPM adoption and reimbursement.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The RPM Access Act focuses on three core areas: payment, quality, and measurement. First, it adds a floor to the geographic indices used to price RPM services, ensuring reimbursement reflects the actual costs of delivering remote monitoring in less densely populated areas.
This floor becomes effective for RPM services furnished beginning January 1, 2026, and is paired with a parallel rule that the floor should not be applied in a budget-neutral way. Second, the bill imposes concrete requirements on RPM providers.
They must be capable of quickly responding to data anomalies with clinical support, and they must transmit relevant vitals and treatment-management notes to the supervising clinician’s electronic health record as needed for effective care management. The bill also requires the collection and reporting of data necessary to evaluate potential Medicare cost savings stemming from RPM adoption.
Small-practice exemptions are provided where the Secretary determines appropriate to ease implementation burden. Third, the bill clarifies what RPM is—a non-face-to-face monitoring and analysis of physiologic data used to develop and manage a chronic or acute condition treatment plan.
It also requires a congressionally mandated report within two years of enactment, analyzing Medicare savings from earlier interventions and reduced hospitalizations, the impact of improved medication adherence, and the full spectrum of practice expenses related to RPM, including connectivity and platform maintenance.
The Five Things You Need to Know
The bill adds a floor (minimum) to the practice expense and malpractice geographic indices for RPM payments, effective 2026.
RPM providers must respond to data anomalies with clinical support and transmit vitals and management notes to the supervising clinician’s EHR.
RPM is defined as non-face-to-face monitoring and analysis of physiologic data used to manage chronic or acute conditions.
Small-practice exemptions are authorized to ease compliance for practice-size differences.
A not-more-than-two-year reporting requirement to Congress will assess Medicare savings from RPM, medication adherence, and related costs.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Findings on RPM and rural access
Congress finds that RPM supports coordinated care, improves patient outcomes, and can lower Medicare costs. Rural areas face a shortage of health professionals, and rural residents travel farther for care. Reimbursement for RPM is lowest in states with higher prevalence of heart failure, hypertension, and diabetes. Practice expenses and malpractice costs do not vary dramatically by state and are not lower in rural settings, underscoring the need for targeted payment adjustments and supports.
Floor for practice expense and malpractice indices
The act adds a new floor (1.00) to the practice expense and malpractice geographic indices for RPM payments, starting in 2026, ensuring rural RPM services are not underfunded. It also explicitly states that the floor will not be applied in a budget-neutral manner, signaling a funded approach to rural RPM pricing rather than a cost-offset strategy.
Ensuring high-quality RPM services — provider requirements
The Secretary must ensure RPM services meet key requirements: providers must be capable of responding to data anomalies with clinical support (directly or via a contracted partner) and must transmit relevant vitals and treatment-management notes to the supervising provider’s EHR as needed for care management. Providers must collect and report data necessary to evaluate potential Medicare savings from RPM proliferation. The Secretary may establish exceptions for small medical practices as appropriate.
Reporting to Congress
Not later than two years after enactment, the Secretary must submit a report to Congress analyzing: (1) estimated Medicare savings from earlier interventions and reduced hospitalizations due to RPM; (2) savings from improved medication adherence among RPM beneficiaries; and (3) practice expenses related to RPM, including cellular connectivity and platform maintenance.
Definition of remote physiologic monitoring
RPM is defined as non-face-to-face monitoring and analysis of physiologic factors used to understand a patient’s health status and to develop and manage a treatment plan for chronic or acute conditions.
This bill is one of many.
Codify tracks hundreds of bills on Healthcare across all five countries.
Explore Healthcare in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Rural Medicare beneficiaries relying on RPM for ongoing monitoring and timely intervention, improving access and outcomes.
- Rural health clinics and critical access hospitals expanding RPM capabilities to serve Medicare patients more efficiently.
- Primary care physicians and supervising clinicians who manage RPM programs with standardized data and EHR integration.
- RPM technology vendors with interoperable platforms that can meet new data-reporting and integration standards.
- CMS and HHS program offices gain clearer data to evaluate RPM’s cost-effectiveness and inform future policy.
Who Bears the Cost
- Small medical practices that must implement new RPM data-reporting and EHR transmission requirements, though exemptions may apply.
- RPM providers upgrading systems to meet anomaly-detection, data-reporting, and privacy standards.
- Rural hospitals and clinics investing in RPM infrastructure and connectivity upgrades.
- The federal government (CMS) funding additional administrative and data-collection activities to monitor RPM adoption.
- Technology vendors providing connectivity and platform maintenance may see ongoing compliance-related costs.
Key Issues
The Core Tension
The central tension is between ensuring high-quality, data-driven RPM care in rural populations and the administrative and financial burden of implementing new performance, reporting, and interoperability requirements, especially for smaller practices that may be partially shielded from the standards.
The bill reflects a policy choice to reinforce rural RPM with a explicit payment floor and a defined set of data-collection and interoperability requirements. While the floor helps ensure rural RPM is adequately funded, the added obligations on providers—especially around anomaly response, EHR transmission, and data reporting—raise implementation costs and potential interoperability challenges.
The small-practice exemption acknowledges differing scales of operation, but there remains a policy question about how broadly that exemption will apply and what the baseline costs will be for non-exempt providers. The reporting requirement introduces a data-driven mechanism to assess effectiveness, yet it depends on consistent data capture across diverse platforms and settings, which may require additional technical and privacy safeguards.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.