Remote Patient Monitoring Devices: What Medicare Requires of the Data

Remote patient monitoring is where connected health hardware meets Medicare billing, and CMS's eligibility conditions decide whether a device and its data path can be part of a billed service. Everything below comes from the Centers for Medicare & Medicaid Services' remote patient monitoring page, last modified May 13, 2026, plus FDA, FTC and HIPAA regulation text where the device and privacy questions lead, all read on October 17, 2026. It is not billing or legal advice.

What CMS says remote patient monitoring is#

"Remote patient monitoring allows a patient to collect their own health data, like blood pressure, weight, and glucose levels, using a connected medical device that automatically transmits the data to their health care provider." The provider then uses that data "to treat or manage (remotely monitor) the patient's condition." CMS names connected blood pressure cuffs, weight scales and pulse oximeters as example devices, and says "Medicare broadly covers remote patient monitoring (sometimes called remote physiologic monitoring) for the collection of any type of physiologic data using a wide range of devices, for chronic and acute conditions."

The device and data conditions#

CMS lists what makes a patient eligible:

The page states the data floor two ways. The eligibility list counts days, "at least 2 days every 30 days", while its description of the device-supply component counts readings: "the collection and transmission of at least 2 readings every 30 days". In our reading, a system that records both the number of readings and the number of distinct days per patient per period can show either.

What Medicare pays for#

CMS splits the service into three components and pays for each one separately:

1. Education and setup, so the patient uses the device appropriately and collects accurate data.
2. Device supply, the internet-connected device and its readings.
3. Treatment and management, the provider reviewing the data and using it to manage the patient's condition.

CMS says it pays "the same rate, regardless of the type of device the patient uses or the health data they collect", and that it doesn't "require that physicians or other qualified health care providers order the services or that the information of the ordering provider be included on the claim." The page names no procedure codes or payment amounts, and neither do we.

CMS also flags a compliance problem. It has covered remote patient monitoring since 2018, use has grown every year, and "Many patients don't get education or help with device setup." It tells providers to deliver all three components. In our reading, that makes a record of completed education and setup a feature a platform's customers will ask for.

Where a consumer wearable fits#

CMS's test is the FDA's device definition, and the FDA's general wellness guidance cuts the other way for many fitness products. The guidance says section 520(o)(1)(B) of the FD&C Act makes software intended "for maintaining or encouraging a healthy lifestyle and is unrelated to the diagnosis, cure, mitigation, prevention, or treatment of a disease or condition" not a device. In our reading, a tracker marketed only for general wellness is not positioned to meet CMS's condition, while hardware its manufacturer markets as a medical device may be. Whether a specific product meets the definition is a question for the manufacturer and the FDA, not something CMS's page settles; our FDA and fitness apps page covers the line.

Privacy and records in the data path#

A company that runs the monitoring software for a practice is in HIPAA territory. The FTC's Mobile Health Apps Interactive Tool asks whether you are "developing, offering, or operating an app on behalf of a HIPAA covered entity (such as a hospital, doctor's office, health insurer, or health plan's wellness program)", and answers that if so, "You likely are a HIPAA business associate". HIPAA's own definitions make a business associate a person who, on behalf of a covered entity, "creates, receives, maintains, or transmits protected health information", and CMS says a covered entity that engages a business associate "must have a written business associate contract or other arrangement". See does my fitness app need HIPAA.

To land readings in the provider's record, HL7's FHIR Observation resource and Vital Signs profile set the shape; getting wearable data into health records with FHIR walks through the required elements.

What we could not verify#

• Remote therapeutic monitoring. CMS's telehealth section lists a remote patient monitoring page and no remote therapeutic monitoring page, and we found no CMS text describing remote therapeutic monitoring's device rules, so this page makes no claims about it.
• Codes and payment amounts. CMS's page names neither.
• The 2027 rules. CMS's proposed 2027 physician fee schedule rule, CMS-1848-P, went on display on July 14, 2026, with comments closing on September 14, 2026. We have not reviewed its remote monitoring provisions, so check the final rule before building billing logic on any number here.