Major integrated health organizations — UnitedHealth Group, CVS Health, and Kaiser Permanente — have submitted letters opposing a Centers for Medicare and Medicaid Services (CMS) proposal that would change how Medicare pays for remote patient monitoring (RPM). According to the reporting, the proposed rule would require that RPM services billed to Medicare be delivered by direct employees of the practice that submits the claim. In practical terms, that requirement would prevent practices from contracting with outside vendors or third‑party contractors to provide RPM services while still billing Medicare for them.
The source article describes these insurer responses as a coordinated pushback against a proposal that could “significantly disrupt” current billing and care models for RPM. The accessible portion of the article emphasizes the prominence of the organizations that objected and notes their dual roles as payers and care providers.
UnitedHealth Group, CVS Health, and Kaiser Permanente argued against the employee-only mandate and instead recommended more narrowly focused regulatory guardrails on RPM. The insurers’ position, as summarized in the available text, favors targeted oversight measures rather than an across-the-board prohibition on vendor-provided monitoring services.
The article reports that these groups urged CMS to adopt policies that address specific concerns about program integrity or inappropriate billing without removing vendors from the delivery model. Exact language from the insurers’ letters, detailed legal or regulatory arguments, and any suggested alternative provisions were not included in the excerpt available to non‑subscribers.
Remote patient monitoring typically relies on connected devices such as blood pressure cuffs, scales, and blood glucose meters. Clinicians use RPM data to support management of chronic conditions including hypertension, diabetes, and heart failure. The source frames RPM as a tool that helps patients and clinicians monitor physiologic metrics between visits and manage long‑term conditions more continuously than episodic office encounters allow.
The reporting indicates that the proposed CMS change could materially alter workflows for practices that currently contract with outside vendors to supply devices, collect and transmit patient data, and perform portions of monitoring and care coordination that support RPM billing.
The article highlights that UnitedHealth Group’s opposition is notable in light of a previous move by its insurance subsidiary, UnitedHealthcare, which had attempted to stop paying for most RPM services on the basis of “insufficient evidence of efficacy.” That prior coverage decision drew attention because it signaled payer skepticism about broad RPM reimbursement, while UnitedHealth Group’s current letter to CMS argues against a vendor ban in the regulatory context.
The accessible portion of the reporting does not include the full text of UnitedHealthcare’s coverage policy, the scope of services affected, or data cited by the insurer to support the evidence claim. Those details were not reported in the excerpt.
If CMS were to adopt an employee-only delivery requirement for RPM billed to Medicare, practices that rely on third‑party vendors for device provisioning, data aggregation, or monitoring staff would face substantive operational changes. Such a policy would likely force practices either to hire staff and internalize monitoring functions or to alter their service offerings and billing practices.
The source notes that this could be a significant disruption but does not quantify how many practices or how many Medicare beneficiaries would be affected. The article also does not provide granular examples of how vendor partnerships are currently structured or the specific functions vendors perform in typical RPM programs.
The STAT article excerpt available to non‑subscribers is truncated and marked as exclusive to STAT+ subscribers. As a result, several important specifics were not present in the accessible text, including:
Because these items were not reported in the source excerpt, they cannot be restated or inferred here. Readers seeking the complete arguments, regulatory language, or additional stakeholder perspectives should consult the full STAT+ article or primary CMS rulemaking documents where available.
Based on the reporting, clinicians, health system administrators, and vendors that support RPM should monitor CMS communications and the formal rulemaking docket for details on whether and how the proposal evolves. Key items to watch include:
The available reporting documents a clear difference in perspective between CMS’s proposed approach and the preferred direction of large integrated insurers, but the full implications will depend on details not included in the excerpted story.
This summary is based on the STAT News reporting excerpt provided. The article indicates it is a STAT+ exclusive; the accessible portion reported that UnitedHealth Group, CVS Health, and Kaiser Permanente submitted letters opposing the CMS proposal and that UnitedHealthcare had earlier tried to curb RPM coverage for lack of evidence. Further specifics—such as the full content of the letters, regulatory citations, and CMS’s detailed rationale—were not included in the available text and therefore are not reported here.