Documentation Requirements To Improve Revenue Cycle for RPM
Master RPM billing documentation code by code. Rhythm360 automates the documentation-to-claim map so you bill clean and audit-ready every time.
Last updated: September 22, 2026
Key Takeaways
- Five documentation pillars support every RPM claim: initiating visit, consent, FDA-cleared device, time logs, and clinical interventions.
- Accurate CPT selection depends on transmission-day logs: the eligibility floor is data on at least 2 days in 30 days, with 99454 and 99445 applied using those thresholds and separate calendar-month tracking for 99457 and 99458.
- Cardiology practices must track 90-day CIED cycles and 30-day physiologic cycles alongside monthly RPM codes without double-counting services.
- Pre-bill hard-stop edits that verify setup education, transmission logs, qualifying minutes, and interactive communication prevent common audit triggers.
- Rhythm360 enforces a documentation-to-claim standard across CIED and physiologic RPM workflows so staff do not track cycles manually.
See the Documentation-To-Claim Map in Action
What Are the Documentation Requirements for RPM Billing?
Every RPM claim rests on nine documentation elements, and each one maps to a specific staff action that must be completed before submission. Miss any single element and the claim is exposed at audit. The following checklist maps each documentation requirement to the operational action your staff must complete before a claim is submitted:
- Established patient relationship — confirm the patient has a prior clinical relationship with the billing practitioner before enrollment.
- Acute or chronic condition — the diagnosis supporting medical necessity must appear in the record and on the claim.
- Initiating visit documentation — an in-person or telehealth visit that establishes the patient as a candidate for remote monitoring and documents the ordering practitioner’s intent.
- Patient consent — verbal or written, documented in the chart with date and scope, obtained before services begin.
- FDA-cleared device confirmation — the record must confirm the device meets the FDA definition of a medical device and transmits physiologic data automatically, not via patient-keyed entry.
- Transmission-day log — a per-period record of which calendar days the device transmitted data, used to select the correct device-supply code based on the 99454 and 99445 thresholds described below.
- Time entries for management codes — dated entries naming the staff member, role, activity performed, and duration, totaled per calendar month.
- Interactive communication record — date, modality, and participant of the real-time two-way audio or video contact required for 99457.
- Clinical decision documentation — the care-plan changes or clinical actions taken in response to the transmitted data.
Medical Necessity and Initiating Visit Documentation
The initiating visit record should document the clinical basis for remote monitoring before the first RPM service is billed. That note should include:
- Condition being monitored — the specific diagnosis (for example, heart failure, hypertension, post-surgical status) with the corresponding ICD-10 code.
- Physiologic parameter — the specific data type the device will collect (for example, blood pressure, weight, pulmonary artery pressure, cardiac rhythm).
- Monitoring goal — the clinical objective the data will serve (for example, medication titration, fluid management, arrhythmia detection).
- Management purpose — a statement that remote monitoring is medically necessary to treat the patient’s condition.
- Ordering practitioner’s intent — the record must make the practitioner’s decision to initiate remote monitoring visible, including who ordered it and why.
CMS’s RPM coverage page states that the provider must determine RPM is medically necessary to treat the patient’s condition before the service is furnished. A device shipment record alone does not establish medical necessity; the initiating visit note must carry the clinical rationale.
Auxiliary personnel may furnish RPM services under the general supervision of the billing practitioner, per CMS Telehealth Services MLN Fact Sheet MLN901705 (Dec. 2025). The ordering practitioner’s intent must be visible in the record regardless of who performs the monitoring work.
Patient Consent Documentation
Consent is a documentation requirement that directly affects payment. CMS MLN901705 (Dec. 2025) requires patient consent at the time RPM services are furnished. The consent record must contain:
- The date consent was obtained.
- The modality, written or verbal, with a notation that verbal consent was received if written was not obtained.
- The scope of services the patient agreed to receive.
- Acknowledgment that cost-sharing may apply.
- The patient’s right to stop services at any time.
For RPM and CCM compliance, the consent record must be stored in the patient’s medical record in an easily retrievable format that makes its date, method, and scope easy to locate, so it can be presented at audit without manual reconstruction. Retrievability matters because stale or missing consent on re-enrollment is one of the most common reasons RPM claims are denied. And because consent for RPM does not cover CCM enrollment, each program needs its own retrievable record.
Device and Data-Supply Documentation for 99453 and 99454
Correcting the 16-Day Claim: A 16-day data-transmission figure circulates widely in secondary billing sources, but it does not reflect the current CMS framework. CMS MLN901705 (Dec. 2025) sets the eligibility floor at data transmission on at least 2 days in a 30-day period. Building on that floor, the 2026 Physician Fee Schedule introduced CPT 99445 to cover device supply when data is transmitted on 2 to 15 days, and revised the 99454 descriptor to cover 16 to 30 days explicitly. The practical consequence is that practices that hard-code 16 days as the only threshold will misclassify patients who transmitted on 2 to 15 days and leave valid 99445 claims unbilled.
99453 — Setup and Education: The record must show:
- That the patient received instruction on how to use the device and transmit health data.
- The date education was completed.
- The staff member who provided the education.
- Confirmation that the device is FDA-cleared and transmits data automatically.
99454 — 30-Day Device Supply: The record must substantiate:
- A per-period log identifying each calendar day on which the device transmitted data.
- That data was transmitted automatically by the device, not entered manually by the patient.
- That only one practitioner is billing device supply for this patient in this 30-day period.
The 30-day supply period runs on its own clock independent of the calendar month used for management codes. The day count selects the correct code and must be archived in a format retrievable at audit.
Time-Tracking and Clinical Review Documentation for 99457 and 99458
The record must substantiate what staff did and when. An auditor reviewing a 99457 claim will look for individual dated entries, not a number typed into a field in the last week of the month.
Each time entry must include:
- The date the activity occurred.
- The staff member’s name and role.
- A description of the specific activity performed, such as reviewed blood pressure trend or called patient to discuss weight gain.
- The duration of that activity.
Interactive communication is a separate documentation element from clinical review time. CPT 99457 requires at least one real-time, two-way audio or video contact with the patient or caregiver during the calendar month. A text message thread does not satisfy this requirement. The record must note the date, modality, and participant of the live contact.
CPT 99458 covers each additional 20 minutes of management time beyond the first 20 and attaches only to 99457, never to 99470. Each unit of 99458 requires a full additional 20 documented minutes. Time billed under RPM management codes cannot also count toward CCM, TCM, BHI, or PCM thresholds in the same month.
For cardiology practices, that general RPM framework sits alongside a second, device-driven code family.
Cardiology Dual Workflow: CIED Codes and Physiologic RPM Codes in One Documentation Standard
Cardiology and electrophysiology practices run two distinct remote monitoring code families simultaneously, each with its own billing cycle and documentation structure. A single documentation standard can serve both without double-counting.
The two families run on different clocks, 90 days for CIEDs and 30 days for physiologic monitors, and each has its own device-specific codes. Keeping them straight prevents device-type mismatch denials.
Pacemakers and ICDs — 90-Day Cycle:
- 93294 — remote interrogation of a pacemaker system (professional component), reported once per 90-day period.
- 93295 — remote interrogation of an ICD system (professional component), reported once per 90-day period.
- 93296 — remote interrogation of pacemaker and ICD systems (technical component), reported once per 90-day period.
Physiologic Monitors and Loop Recorders — 30-Day Cycle:
- 93297 — remote interrogation of an implantable cardiovascular physiologic monitor (for example, CardioMEMS pulmonary artery pressure sensor). It is billable once per 30 days and is a device-specific code, not a professional-component code. It can be billed global, with modifier -26, or with modifier -TC.
- 93298 — remote interrogation of a subcutaneous cardiac rhythm monitor or implantable loop recorder, billable once per 30 days. This is a device-specific code, not a technical-component code. It can be billed global, with modifier -26, or with modifier -TC. Never apply 93297 to a loop recorder or 93298 to a physiologic monitor.
Each 93297 and 93298 documentation package must include the start and end dates of the 30-day period, the device type, the transmitted findings, a signed interpretation by the responsible clinician, and, where only the -26 modifier is reported, identification of the entity that supplied the equipment and collected the data.
The physiologic RPM codes run on separate 30-day and calendar-month clocks. A single documentation standard keeps each code family’s time accounting, transmission logs, and signed reviews in separate, non-overlapping fields.
Automate the Documentation-To-Claim Map With Rhythm360
Rhythm360 turns this dual cardiology workflow into a consistent, auditable documentation standard. The platform keeps device data, time logs, and CPT cycles aligned so staff do not manage complex spreadsheets.

- Vendor-neutral data ingestion: Rhythm360 ingests and normalizes data from major cardiac device manufacturers, including Medtronic, Boston Scientific, Abbott, and Biotronik, into a single source of truth. This consolidation eliminates manual portal logins and transcription errors.
- Bi-directional EHR integration: The platform integrates with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7, so documentation flows directly into and out of the chart.
- Automatic CPT cycle tracking: Rhythm360 tracks device-specific CPT pairings, including the 90-day pacemaker and ICD cycles and the 30-day physiologic monitor and loop recorder cycles, as well as physiologic RPM codes such as 99453, 99454, and 99457.
- Auditable documentation generation: Rhythm360 maintains an audit trail. The Patient Profile Page displays the patient’s action history within the Rhythm360 portal, and the platform includes security and compliance features that support retrospective review. See the Patient Profile Page documentation for details.
Practices using Rhythm360 have achieved up to an 80 percent reduction in critical alert response times and up to a 300 percent increase in revenue capture.
Automate Your CIED and RPM Cycles
Pre-Bill Hard-Stop Edits and Overlap Rules
Pre-bill hard-stop edits catch missing documentation before claims reach payers. Configure the following hard-stop edits before any RPM or CIED claim is submitted:
- No 99453 without documented setup and education — the record must show the patient received device instruction before the setup code is released.
- No 99454 or 99445 without a transmission-day log — the day count must be confirmed and archived before the device-supply code is selected.
- No 99457 or 99458 without documented qualifying time — the calendar-month time total must reach the applicable threshold, with individual dated entries supporting it.
- No 99457 without documented interactive communication — the real-time contact record must exist before the management code is released, consistent with the interactive-communication requirement described above.
- No 99470 billed in the same month as 99457 — only one management-tier code per patient per calendar month.
- No 99445 billed in the same month as 99454 — only one device-supply code per patient per 30-day period.
- No double-counting across RPM, CCM, TCM, BHI, and PCM — each program’s time must be logged in a separate, non-overlapping bucket. A single block of staff time supports only one program.
- No concurrent RPM and RTM — a patient is enrolled in one remote monitoring program per period.
RPM and CCM may be billed for the same patient in the same month when each program’s time is documented separately with distinct activity descriptions and timestamps. When those entries are vague or combined, auditors cannot tell which program the time supported, which is why vague time entries are the second most common RPM audit finding, after missing proof of the transmission requirement. The result is usually recoupment of the claim.
2026 Policy Watch
The CY 2027 Medicare Physician Fee Schedule Proposed Rule, issued July 14, 2026, proposes three changes. It would require a separately reportable initiating visit for RPM and RTM services, restrict monitoring to clinical staff who are direct employees of the billing practice, and solicit comments on consolidating the current RPM and RTM CPT code families into four new HCPCS G-codes.
None of these proposals are final. Practices should avoid hard-coding workflows around old thresholds or assuming the current code structure will remain unchanged after January 1, 2027. Monitor the final rule, expected by its statutory publication deadline of November 1, 2026, with an implementation date of January 1, 2027, before updating billing logic.
Frequently Asked Questions
What Are the Billing Guidelines for Remote Patient Monitoring?
The core billing guidelines for remote patient monitoring are:
- The patient must have an established relationship with the billing practitioner and an acute or chronic condition requiring monitoring.
- The device must meet the FDA definition of a medical device and transmit physiologic data automatically.
- Patient consent must be documented before services begin.
- 99453 is billed once per episode of care for device setup and patient education.
- Device-supply codes follow the 99454 and 99445 thresholds described above, and only one device-supply code is billed per period.
- 99457 covers the first 20 minutes of management time per calendar month and requires at least one real-time interactive communication. 99458 covers each additional 20 minutes and attaches only to 99457.
- 99470 covers the first 10 minutes of management time and cannot be billed in the same month as 99457.
- Only one practitioner may bill RPM for a given patient in a 30-day period.
- As noted in the hard-stop edits, RPM and RTM cannot be billed concurrently for the same patient.
What Are the Requirements for Remote Patient Monitoring?
The requirements for remote patient monitoring are:
- An established patient relationship between the patient and the billing practitioner.
- An acute or chronic condition that requires physiologic monitoring.
- A device that meets the FDA definition of a medical device, digitally uploads data, and transmits physiologic data automatically to a secure location available to the billing practitioner.
- Patient consent documented in the medical record before services are furnished.
- Data transmitted on at least 2 days in a 30-day period to meet the eligibility floor.
- At least one real-time interactive communication with the patient or caregiver per calendar month to support the management codes.
- Documentation maintained in the patient’s medical record and available for retrospective review.
What Are the New CPT Codes for Remote Patient Monitoring in 2026?
The CY 2026 Medicare Physician Fee Schedule final rule introduced two new RPM codes effective January 1, 2026. CPT 99445 covers device supply when physiologic data is transmitted on 2 to 15 days within a 30-day period, filling a gap that previously left short-transmission months unbillable. CPT 99470 covers the first 10 minutes of RPM treatment management in a calendar month, providing a billing pathway for months where documented management time falls between 10 and 19 minutes. Neither 99445 nor 99470 may be billed in the same period as 99454 or 99457, respectively. These codes extend the existing RPM code family to cover previously uncompensated service periods.
What Are the CMS Guidelines for RTM Services?
Remote therapeutic monitoring (RTM) covers non-physiologic data, such as therapy adherence and response, musculoskeletal activity, respiratory data, and cognitive behavioral therapy applications, rather than the physiologic data covered by RPM. RTM codes include 98975, 98976, 98977, 98980, and 98981. Unlike RPM, RTM does not require an established patient relationship under current rules, though the CY 2027 proposed rule would add that requirement. As noted in the hard-stop edits, RPM and RTM cannot be billed concurrently for the same patient.
What Documentation Supports RPM Medical Necessity?
Documentation supporting RPM medical necessity must identify the specific diagnosis and ICD-10 code for the condition being monitored, the physiologic parameter the device will collect, the clinical goal the monitoring will serve, and a statement that remote monitoring is medically necessary to manage the patient’s condition. The initiating visit note must make the ordering practitioner’s intent visible in the record. A device shipment record alone does not establish medical necessity. The record must also confirm the device is FDA-cleared and transmits data automatically, distinguishing it from consumer wellness devices.
What Does RPM Patient Consent Documentation Need to Include?
RPM patient consent documentation must include the date consent was obtained, the modality, written or verbal, the scope of services the patient agreed to receive, acknowledgment that cost-sharing may apply, and the patient’s right to stop services at any time. Verbal consent is acceptable but must be documented in the chart. Consent must be obtained before services are furnished, not retroactively. Consent for RPM does not cover enrollment in CCM or other care management programs; each program requires its own documented consent. For RPM and CCM compliance, the consent record must be stored in the patient’s medical record in an easily retrievable format that makes its date, method, and scope easy to locate, so it can be presented at audit without manual reconstruction.
How Should RPM Time-Tracking Documentation Be Structured for 99457 and 99458?
Time-tracking documentation for 99457 and 99458 must consist of individual dated entries, not an aggregated monthly total. Each entry must identify the staff member by name and role, describe the specific activity performed, and record the duration of that activity. Entries must be created as the work is performed, not reconstructed at month end. The calendar-month total is derived from the sum of individual entries. Interactive communication, the real-time two-way audio or video contact required for 99457, must be documented separately, noting the date, modality, and participant. Each unit of 99458 requires a full additional 20 documented minutes beyond the prior threshold and attaches only to 99457.
Conclusion: Build the Standard Before the Audit
RPM denials are almost always documentation failures, not coding errors. When the record cannot substantiate medical necessity, consent, transmission days, management time, or interactive communication, the claim fails regardless of how accurately it was coded. Practices that survive payer audits build a field-level documentation standard before the audit letter arrives.
Rhythm360 automates the documentation-to-claim map described throughout this guide, so the standard you design is enforced on every claim without manual tracking.
.avif)