CMS services · remote monitoring versus telehealth
Remote patient monitoring collects and transmits physiologic data for a provider to review and manage. Medicare telehealth generally describes a remote encounter. The categories can support the same care plan without becoming the same service.
What CMS calls remote patient monitoring
CMS describes remote patient monitoring as a patient using a connected medical device to collect health data such as blood pressure, weight or glucose and automatically transmit those data to a healthcare provider. The provider uses the information to manage the patient’s condition.
The current CMS page organizes the service around education and setup, device supply, and treatment management. Those components distinguish monitoring from a video or telephone visit whose central service is the live encounter.
Why the distinction matters
A connected device can transmit data between visits, but the data feed does not automatically replace an evaluation. A telehealth visit can occur without a remote-monitoring device. Payment rules, consent, documentation and eligible practitioners may differ between the categories.
Ask what work occurred: device setup, automated data transmission, review and management, or a synchronous encounter. A product label or general “virtual care” description does not determine the Medicare category.
A source-based comparison
- Information flow: device data over time versus encounter communication.
- Evidence record: transmitted readings and management versus visit documentation.
- Policy source: remote-monitoring guidance versus telehealth service rules.
- Clinical role: longitudinal information can inform, but not automatically substitute for, an encounter.
What readers can verify next
Ask the provider which service category is being offered, what device and data flow are involved and how Medicare coverage will be checked. Current code and payment questions require the applicable calendar-year CMS materials, not this overview.