Does Medicare require patient consent before billing RPM?

Yes. Medicare generally requires that patients be informed about and agree to remote physiologic monitoring before a practice bills for it. Consent can typically be verbal or written, but it must be documented in the patient's record.

Do I need to get a new consent from the patient every month?

No. A single, well-documented consent obtained at enrollment is generally understood to cover ongoing RPM services, as long as the patient remains enrolled and the scope of the program doesn't materially change. It does not need to be re-obtained each billing cycle.

What should a patient be told before enrolling in RPM?

Patients should understand that their physiologic data will be transmitted to and reviewed by their care team, that cost-sharing such as a copay or coinsurance may apply, and that they can stop participating in the program at any time without it affecting their other care.

Who typically has the consent conversation with the patient?

This varies by practice and by payer policy. In many settings a physician, qualified health professional, or trained clinical staff member acting under appropriate supervision can conduct and document the consent conversation, but practices should confirm this against current payer and state rules.

Compliance · remote monitoring

RPM Patient Consent & Enrollment: What's Required

6 min read · Updated July 2026

Before a practice can bill for remote physiologic monitoring (RPM), the patient needs to know what they're agreeing to — and that agreement needs to be documented. This is a general overview of how consent typically works, not a substitute for your own compliance review.

Why consent matters for RPM

RPM involves collecting a patient's physiologic data — glucose readings, blood pressure, weight, and similar measurements — outside the walls of a clinic, on an ongoing basis, and billing for the time spent reviewing and acting on that data. Because this is a recurring service with recurring charges, payers generally expect the patient to have been informed about the program and to have agreed to participate before billing starts. This isn't unique to RPM; it reflects a broader expectation that patients understand and consent to services that generate ongoing charges to their insurance.

Under Medicare, RPM consent is generally understood to be satisfied by either a verbal or written agreement, as long as it is captured in the patient's medical record. Some commercial and Medicare Advantage payers may layer on additional documentation preferences, so it's worth checking payer-specific guidance alongside the general Medicare framework.

Consent is a one-time step, not a monthly one

A common point of confusion is whether consent has to be refreshed every billing period. In general, it does not. Once a patient has been informed about the RPM program and has agreed to participate — and that conversation has been documented — the same consent is generally understood to carry forward for as long as the patient remains enrolled in that program, without needing to be re-obtained each month.

That said, if the scope of the program changes materially — for example, a new device type is introduced, or the monitoring purpose shifts — it's reasonable to revisit the conversation and document it again. And if a patient disenrolls and later re-enrolls, a fresh consent conversation is the safer approach.

What should be communicated to the patient

Regardless of whether the consent is captured verbally or in writing, the conversation should generally cover a few things in plain language:

What's being monitored. Which device(s) will be used, what data will be collected (e.g., continuous glucose readings), and how often.
Who sees the data. That readings are transmitted to the care team and reviewed as part of ongoing care, not just stored.
Cost-sharing may apply. That RPM is a billed service and the patient may be responsible for a copay, coinsurance, or deductible amount depending on their plan — this is worth stating clearly so it isn't a surprise on a later statement.
Participation is voluntary and reversible. That the patient can decline to enroll, or stop participating at any time, without it affecting their access to other care.
How to reach the care team. A basic point of contact if the patient has questions about a reading, the device, or the program itself.

Documenting consent

Documentation doesn't need to be complicated, but it should be specific enough to show that the conversation actually happened. At minimum, most practices document: the date of the conversation, who conducted it, that the patient was informed of the items above, and that the patient agreed to enroll. This is typically logged as a note in the EHR or on a signed enrollment form, depending on the practice's workflow and payer preference.

Because consent requirements and acceptable documentation formats can vary by payer and are updated periodically, it's worth confirming your practice's approach against current CMS guidance and any payer-specific manuals before finalizing a workflow.

A simple RPM enrollment workflow

Most practices that run RPM programs smoothly follow some version of this sequence:

Order. The billing clinician identifies a clinically appropriate patient and places an order for RPM, specifying the device or monitoring type.
Consent conversation. A qualified staff member explains the program — what's monitored, who reviews it, potential cost-sharing, and that participation is voluntary — and documents the patient's agreement in the record.
Device setup and education. The patient receives the device and is walked through how to use it, how often to take readings, and who to contact with questions.
Confirm data flow. Before considering the patient fully enrolled, staff confirm that readings are actually transmitting to the platform the care team monitors — catching connectivity issues early avoids gaps in billable monitoring days later.
Begin monitoring. Once data is flowing reliably, the patient is formally enrolled and ongoing review, interactive communication, and any qualifying management time can begin.

Keeping this sequence consistent — and documenting each step — tends to make both the patient experience and the compliance picture cleaner, especially as a program scales beyond a handful of patients.

Building or refining an RPM workflow?

See how CGM-based remote monitoring fits into a primary care visit flow, from enrollment through ongoing review.

For clinical GPs

This article is educational and does not constitute legal or medical advice. Consent and documentation requirements vary by payer and change over time; consult your compliance counsel and current CMS guidance before implementing an RPM program.