Remote patient monitoring (RPM) documentation needs to show more than that data was collected. For Medicare claims, the medical record and supporting documentation should allow the practice to substantiate the applicable service requirements, including the clinical rationale for RPM, qualifying device data, treatment-management activity, required interactive communication, and time when applicable.
The specific documentation needed can vary by CPT code, payer, and the circumstances of the service. This guide focuses primarily on Medicare RPM requirements and practical documentation considerations for independent practices.
Medical Necessity Comes First
RPM documentation should establish why remote patient monitoring is clinically appropriate for the patient and how the service relates to the patient’s condition and treatment.
Recording transmission days or treatment-management time does not, by itself, replace documentation supporting the clinical rationale for the service. CMS states that medical-record documentation may be used to support the medical necessity of Part A or Part B services and may include orders, assessment notes, correspondence, and other supporting documentation.
For an independent practice, the chart should therefore make the clinical reason for RPM reasonably clear and connect the monitoring service to the patient’s care.
Documenting RPM Device Setup and Data Transmission
For CPT 99453, documentation should support the initial setup of the RPM service and patient education on using the monitoring equipment.
For device-supply services, the applicable 2026 code depends on the number of days of qualifying data transmission during the 30-day period:
- 99445: 2–15 days of RPM data transmission during a 30-day period
- 99454: 16–30 days of RPM data transmission during a 30-day period
CMS’s 2026 materials identify 99445 as the RPM device-supply code for 2–15 days and 99454 for 16–30 days.
The RPM device must meet Medicare’s applicable requirements. CMS has stated that the device supplied for RPM must be a medical device as defined under the Federal Food, Drug, and Cosmetic Act, must be reliable and valid, and must automatically collect and electronically transmit the patient’s physiologic data rather than rely on patient self-reporting.
Documentation should therefore allow the practice to substantiate the device used and the actual qualifying transmission activity for the applicable monitoring period.
Documenting Interactive Communication
Treatment-management codes have communication and time requirements that should be supported by the medical record.
For 99457, 99458, and 99470, practices should document the required interactive communication and the treatment-management work performed during the applicable period. In particular, the record should make the nature of the interaction and the clinical work understandable from the documentation.
A useful documentation entry can identify:
- The date of the interaction
- The patient or caregiver involved
- The communication method
- The clinical issue or RPM data discussed
- The assessment or intervention, when applicable
- Any resulting change to the patient’s care plan or follow-up
Simply documenting that RPM data was reviewed is not the same as documenting the required interactive communication.
For example:
Data review: “Reviewed patient’s blood pressure trend.”
This documents review of data, but by itself does not establish the required interactive communication.
A more complete entry could state:
Interactive communication: “Contacted patient regarding recent elevated blood pressure readings. Discussed readings and current medication adherence and provided instructions for continued monitoring and follow-up.”
The exact documentation should reflect what actually occurred. Practices should not create or reconstruct interactions that did not take place
Understanding the 2026 RPM Treatment-Management Codes
The 2026 RPM code structure includes 99470, which covers the first 10 minutes of RPM treatment management per month. CMS’s 2026 materials list 99470 as the RPM treatment-management code for the first 10 minutes per month.
Practices should make sure their documentation and billing workflows reflect the applicable 2026 code requirements rather than relying exclusively on older RPM documentation templates.
The applicable code should be supported by the services actually furnished and documented during the relevant period.
Documenting RPM Time
Time-based RPM services require documentation that supports the time reported.
A practical documentation workflow is to maintain dated entries showing:
- The date of the activity
- The activity performed
- The time spent
- The cumulative time when applicable
- The clinical relevance of the work
A practice does not necessarily need to use a particular EHR format or create a separate note for every individual activity solely because CMS has not prescribed one universal charting format. The important point is that the records should support the service and the time billed.
For patients receiving multiple care-management services, practices should also make sure that the same time is not counted toward more than one separately billed service when the applicable billing rules prohibit overlapping time.
Consent Should Be Documented
Medicare requires beneficiary consent for RPM services. CMS has clarified that consent for RPM may be obtained at the time the RPM services are furnished; it does not require Medicare RPM consent to be obtained before monitoring begins.
Practices should document the consent in accordance with applicable Medicare requirements and should also consider any additional requirements imposed by their payer, state law, or organizational policies.
Consent documentation should be clear enough to establish that the patient agreed to receive the applicable RPM service.
What Should a Defensible RPM Record Show?
There is no single CMS-mandated note template that every independent practice must use. Instead, the documentation should allow the practice to substantiate the requirements applicable to the services billed.
For a Medicare RPM episode, supporting documentation should allow the practice to identify, as applicable:
- The clinical rationale and medical necessity for RPM
- The RPM device used
- Initial device setup and patient education, when applicable
- The actual number of qualifying transmission days during the applicable 30-day period
- Required interactive communication
- The time spent on applicable treatment-management services
- Relevant assessment, intervention, or care-plan management supported by the RPM information, when applicable
- Patient consent
- Documentation supporting that time or activities were not improperly counted toward multiple services
The goal is not to create unnecessary documentation. The goal is to ensure that the record accurately reflects the services that were actually provided and contains enough information to support the claim if the documentation is reviewed.
How Long Should RPM Documentation Be Kept?
CMS’s current medical-record maintenance guidance states that applicable providers, suppliers, and professionals must maintain the required documentation for 7 years from the date of service under 42 CFR 424.516(f). CMS also explains that the documentation must be made available when requested by CMS or a Medicare contractor.
State medical-record retention laws, payer requirements, contractual obligations, and organizational policies may impose different or longer retention requirements. Practices should confirm the requirements applicable to their specific circumstances.
Common RPM Documentation Gaps
Several documentation problems can make an otherwise legitimate RPM service difficult to substantiate.
Data review documented without required interactive communication
A note stating that RPM data was reviewed does not, by itself, establish the interactive communication required for applicable treatment-management services.
Transmission days are assumed rather than verified
Practices should be able to substantiate the actual qualifying transmission activity for the applicable 30-day period rather than relying on an assumption that the patient generally transmits data.
Time is documented only as a monthly lump sum
A single unexplained total can make it difficult to determine what work was performed and how the reported time was calculated. Dated activity records can provide stronger supporting documentation.
Consent is not documented
Even though Medicare permits RPM consent to be obtained at the time services are furnished, the practice should maintain documentation showing that the required consent was obtained.
Documentation does not explain the clinical context
RPM data should be connected to the patient’s clinical management when applicable. Documentation that contains numbers and timestamps but provides no understandable clinical context may make the record harder to evaluate.
Documentation is copied forward without verification
CMS has emphasized that EHR information should be reviewed and verified for accuracy rather than copied forward without confirming that it remains accurate for the current service.
Frequently Asked Questions
Does reviewing RPM data count as interactive communication?
Not by itself. Data review and interactive communication are distinct documentation concepts. Where a CPT code requires interactive communication, the record should support that the required communication actually occurred.
How many transmission days are required for RPM in 2026?
The 2026 RPM device-supply codes distinguish between 2–15 days under 99445 and 16–30 days under 99454 during a 30-day period.
Does Medicare require RPM consent before monitoring begins?
No. CMS permits Medicare RPM consent to be obtained at the time the RPM services are furnished.
How long should Medicare documentation be retained?
CMS’s current guidance under 42 CFR 424.516(f) requires applicable documentation to be maintained for 7 years from the date of service. Other state, payer, contractual, or organizational requirements may apply as well.
Does every RPM code require a completely separate note?
Not necessarily. CMS does not prescribe one universal note format for all RPM services. A single record can contain information supporting multiple services, provided the documentation clearly supports the applicable requirements for each service and does not improperly combine or double-count activities.
The Bottom Line
Good RPM documentation is not about creating more notes. It is about making the record accurately reflect what happened.
For independent practices, the documentation should make it possible to understand:
Why was RPM appropriate for this patient? What device was used? What data was transmitted? What treatment-management work occurred? Was the required communication performed? How much qualifying time was spent? And can the practice substantiate those services from its records?
A well-designed RPM workflow can make these records easier to maintain by capturing transmission activity, communication, time, and relevant clinical information as the work occurs rather than requiring staff to reconstruct the month later.
Want RPM documentation captured as part of your workflow instead of reconstructed at month’s end? Talk to the Advaa Health team about how its remote patient monitoring software can support RPM workflows within an integrated healthcare platform.
