RPM Documentation Requirements: A Checklist for Every Patient Month

RPM documentation requirements come down to one test: could someone outside your practice open the record months from now and see why the patient was monitored, that the patient agreed, which days had readings, who spent how many minutes on what, and when staff spoke with the patient? This checklist sorts what to record by when you record it. It follows general Medicare guidance, which changes every year and differs by payer, so confirm the details with current CMS guidance, your MAC and your payer contracts.

Why RPM records carry the claim

Every RPM code is built on something countable: days with readings, minutes of work, a live conversation in the month. A claim says those things happened. The record is the only proof that they did. If a payer reviews the claim later and the minutes are not in the chart, or the readings cannot be tied to a date, the payment can be taken back.

Two habits make everything below easier:

• Record the work when it happens, not from memory at month end.
• Never overwrite an entry. Correct it with a new line that says what changed, who changed it and why, and keep the original.

Before the first reading: the enrollment record

• An order or note from the treating practitioner saying what is being monitored and why it is reasonable and necessary for this patient.
• The diagnosis or diagnoses being monitored. CMS allows acute or chronic conditions.
• The date of the visit that establishes the patient's relationship with the billing practitioner.
• Consent: the date, who obtained it, whether it was written or verbal, and what the patient was told. That includes what the service is, that cost sharing may apply, that only one practitioner can bill it in a period, and that the patient can stop at any time.
• A note that you asked whether another practice already monitors the patient. CMS allows only one practitioner to bill the device codes in a period.
• The patient's alert limits for each reading type, set by the provider, with who set them and when.
• The plan for what staff do when a reading crosses a limit, and when they escalate to a provider.

Our checklist on RPM patient consent and enrollment covers the consent conversation itself.

The device record

• The device type and what it measures.
• That the device meets the FDA definition of a medical device and sends readings automatically. Readings the patient types in or reports by phone do not count as RPM data under CMS rules.
• The serial number, or IMEI for a cellular device, tied to this patient.
• The ship date and the delivery date.
• The setup and patient education: the date, who did it and what the patient was taught. This supports the setup code.
• The date of the first reading.
• Any replacement or return, with the date and the reason.

Every day: the readings

• Each reading stored as the device sent it, with the date and time it was taken.
• A count of the days with at least one reading in each 30-day period. The device supply codes depend on it.
• Gaps noted when the patient stops sending readings, with what staff did about it.
• Corrections kept beside the original reading, never in place of it.

Every review and contact: the minutes log

The treatment management codes are time based, so each entry needs enough detail to stand on its own.

• The date, the minutes spent and who did the work, with their role or credentials.
• Which readings were reviewed.
• What was done: a call, a text, education, a check-in, a change requested from the provider.
• For a live conversation with the patient or caregiver: the date, who took part and how long it lasted. CMS describes the required interactive communication as real-time and two-way, such as a phone or video call. A text or a voicemail generally does not count as one. Confirm the current definition with your MAC.
• Unanswered calls and voicemails too. They do not count as interactive communication, but they show the effort to reach the patient.
• Every escalation to a provider: what was sent, when, and the provider's response, including any change to the care plan.
• Time corrections as new lines with the reason, never as edits to the original figure.

Before each monthly claim

Check each patient month against the code requirements before anything is billed. The codes run on two different clocks: the device codes on a 30-day period, the treatment management codes on a calendar month.

• Days with readings in the 30-day period meet the device code you plan to bill. The long-standing device supply code requires at least 16 days.
• Minutes in the calendar month meet the management code: 20 minutes for the first code, each additional 20 minutes for the add-on.
• At least one interactive communication with the patient or caregiver happened in the month.
• Starting in 2026, CMS added codes for shorter periods (2 to 15 days of readings, and the first 10 minutes of management). Check the current code descriptors and whether each payer covers them before you bill them.
• The setup code is billed only once per episode of care.
• No minute counted here is also counted toward another service, such as chronic care management.
• The billing practitioner and the supervision arrangement are on the record.

If a month falls short, bill only the codes it meets. The guide to RPM CPT codes explained lists what each code requires, and RPM vs CCM covers billing the two together.

How long to keep RPM records

Keep RPM records for as long as federal rules, your state's law and your payer contracts require, whichever is longest. Retention periods differ by record type and by state, so ask your compliance adviser for the number that applies to you. Keep the readings, the minutes log, the consent and the notes together: a minutes log without the readings it refers to proves little on its own.

Frequently asked questions

Does a text message count as interactive communication for RPM?

CMS describes the interactive communication required for the treatment management codes as real-time, two-way communication, such as a phone or video call. A text message or a voicemail generally does not meet it. Record texts anyway, as part of the work, and confirm the current definition with your MAC.

Do I need to document every reading?

Store every reading the device sends, with the date and time it was taken. The device codes depend on the number of days with readings, so a missing day in the record is a missing day for billing.

Who can document RPM time?

Whoever did the work records it, with their role or credentials. CMS generally allows clinical staff to furnish treatment management time under general supervision, but state rules on what each role may do differ. Check yours.

What if a month does not meet the requirements?

Do not bill a code the month does not meet. Keep the full record of the month anyway: it shows the care given and explains why no claim went out.

Sources

• Telehealth & Remote Monitoring (MLN901705), CMS
• CY 2026 Payment Policies Under the Physician Fee Schedule (final rule), Federal Register
• CY 2024 Payment Policies Under the Physician Fee Schedule (final rule), Federal Register
• Chronic Care Management Services (MLN909188), CMS