RPM Documentation That Holds Up
Remote patient monitoring has become a routine part of chronic care in Medicare practices, and federal reviewers are reading the records behind those claims more closely than ever.
If the Office of Inspector General or a Medicare contractor requested a patient's RPM file tomorrow, could the practice support every billed month with what the chart shows?
This guide explains what RPM billing documentation needs to contain for a claim to hold up under review.
OIG Billing Measures
The OIG Uses Five Billing Measures in Its RPM Audit
In the active OIG audit of remote patient monitoring, reviewers are checking whether practices furnished and billed RPM according to Medicare requirements. In its August 2025 data snapshot, the OIG identified five billing measures that reviewers can use to single out specific practices.
For that analysis, the OIG reviewed claims from 4,639 practices that routinely billed for RPM in 2024. Each measure, with the number of practices flagged under it:
- Sudden spikes in new RPM enrollees in a single month: 32 practices
- No prior relationship with more than 80 percent of RPM patients: 45 practices
- More than 75 percent of enrollees never receiving treatment management: 52 practices
- Frequent billing for patients shared with two or more other practices: 34 practices
- Frequent billing for two or more devices per patient per month: about 20 practices
Practices Flagged Under Each OIG Billing Measure
Out of 4,639 practices that routinely billed for RPM in 2024
Source: HHS-OIG, Billing for Remote Patient Monitoring in Medicare (OEI-02-23-00261)
The OIG states that it hasn't confirmed fraud at any practice through these measures alone. It also states that practices well outside the normal range warrant further review, which makes each measure a likely starting point for an RPM audit.
Each measure corresponds to a record a reviewer expects to find in the chart, and the sections below cover those records in order. Treatment management is the subject of Part 2 of this series.
OIG Work Plan
RPM Billing Is an Active Item on the OIG Work Plan
The OIG lists an audit of Medicare Part B RPM services as active on the OIG work plan, announced on December 16, 2024. Its stated goal is to determine whether providers furnished and billed RPM in line with Medicare requirements.
The OIG also names the risks it's watching for: unsolicited device shipments, inadequate monitoring, and inappropriate billing. Reviewers look for evidence of each risk, or its absence, in the patient record.
The OIG points to rapid spending growth as a reason for that attention. Medicare and Medicare Advantage paid $536 million for RPM in 2024, a 31 percent increase over 2023, while enrollment grew 27 percent to nearly 1 million patients.
Medicare Payments for RPM, 2019 to 2024
Original Medicare and Medicare Advantage, in millions of dollars. Select a year.
Medicare paid $536 million for RPM in 2024.
Source: HHS-OIG, Billing for Remote Patient Monitoring in Medicare (OEI-02-23-00261)
Practices engaged in RPM billing should expect the OIG and Medicare contractors to treat these claims as a review priority for the foreseeable future.
Medical Necessity
RPM Requires Medical Necessity Documentation for Every Patient
Medicare expects practices to name the monitored condition in the chart, explain why monitoring suits the patient, and include the order and the patient's consent. That medical necessity documentation is the first thing a reviewer reads.
Medicare covers RPM for acute and chronic conditions. The practitioner names the specific diagnosis in the note and states how remote readings will guide care, such as using blood pressure readings to adjust medication for uncontrolled hypertension.
Reviewers can't verify a generic line stating that a patient "qualifies for RPM." They look for an individual clinical reason, a signed order from the billing practitioner, and a plan for how the readings will inform treatment.
Practices answer the question of who qualifies for remote patient monitoring in the same note. The patient has a qualifying condition, an established relationship with the practice, and consent on file.
Consent belongs in the record from the start. CMS requires patient consent at the time RPM services are provided, and reviewers look for that consent in the chart.
Established Patient Relationship
Practices Must Document a Prior Visit Before Billing RPM
CMS requires an established patient relationship before a practice bills RPM, which means a provider in the practice has seen the patient in person or by telehealth. During that visit, the provider reviews the patient's condition and decides whether monitoring will help.
It's one of the simplest RPM billing requirements to document, and one of the most visible when it's missing. The OIG found 45 practices with no prior relationship for more than 80 percent of the patients they billed for RPM in 2024.
Source: HHS-OIG, Billing for Remote Patient Monitoring in Medicare (OEI-02-23-00261)
At the far end, one practice lacked a prior relationship with more than 30,000 enrollees. Reviewers tend to follow up on patterns like that with a records request rather than a phone call.
Reviewers will look for the earlier visit in the chart, with its date, the provider who saw the patient, and whether it took place in person or by telehealth. Medicare Advantage plans may have different requirements, though the OIG flagged missing relationships across both programs.
Device and Transmission Days
CMS Sets Device and Transmission-Day Rules for RPM Billing
Medicare requires practices to collect data on 2 to 15 days, or 16 or more days, in each 30-day period, depending on the code billed, according to CMS. Under the 2026 CPT code set, practices bill 99454 for 16 or more days and 99445 for 2 to 15 days.
CMS requires readings to be uploaded automatically by a device that meets the FDA definition of a medical device. Values a patient types into an app or reports by phone don't count toward billable days.
Medicare counts distinct days with data, not the number of readings. A patient who takes five readings on a single Tuesday has one day of data.
Transmission-Day Counter
Select a day to log a reading. Selecting the same day again adds another reading to that day.
Under the RPM billing guidelines for 2026, a practice bills either 99454 or 99445 for a 30-day period, never both. The RPM 16 day rule still applies to 99454, so a practice relies on the dated transmission log to choose the code.
Medicare also generally allows billing for one device per patient per month. The OIG flagged about 20 practices that each billed for multiple devices more than 100 times in a year, and 34 practices that frequently billed for patients shared with two or more other practices.
For remote patient monitoring billing, a practice that records an intake question about other monitoring programs can show it checked before enrolling the patient.
Documentation by Code
Medicare Documentation Requirements Apply to Each Billed RPM Code
Medicare contractors look for the condition, medical necessity, consent, an FDA-defined device, transmission days, and management records for each billed code. Practices can check those Medicare documentation requirements against the table below, organized by the RPM codes billed most often.
What the chart should show
Patient name, date of service, and billing provider on each page; diagnosis supporting the codes billed; authenticated signatures
Setup and education
Signed order, patient consent, device type, a note that the patient or caregiver learned to use the device, and at least 2 days of data in the 30-day period; billed once per episode of care
Device supply
Dated transmission log showing distinct days per 30-day period, and one device-supply claim per period
Treatment management
Time spent, who performed the work, and the interactive communication with the patient (covered in Part 2)
With complete RPM documentation in place for each month, a practice can answer a records request without reconstructing anything after the fact.
Audit Readiness
Practices Prepare for a Medicare Audit by Reviewing Their Own RPM Claims
Practices prepare for a Medicare audit by reviewing their RPM claims against the OIG's five measures and confirming each record can be retrieved quickly. The OIG has published its measures, so a practice can run the same checks first.
In an internal review, the practice asks the questions a reviewer will ask. Did new enrollment spike in any month? Does every RPM patient have a documented prior visit? Was any patient billed by another practice, or for more than one device in a month?
When a Medicare contractor sends an additional documentation request for RPM, the practice gathers the order, consent, prior-visit note, transmission log, and management notes for each billed month. The practice can use the same file for routine RPM medical review by the contractor.
Device data is often stored on a vendor platform outside the EHR. Practices that work with an RPM vendor benefit from confirming they can export dated transmission logs on request, since the billing practice remains responsible for every claim.
Common Questions
Frequently Asked Questions
Can two practices bill RPM for the same patient in the same month?
CMS allows only one practitioner to bill for remote monitoring per patient in a 30-day period, even when different practices monitor different conditions. The OIG flags practices that frequently bill for patients shared with two or more others.
Can a practice bill 99454 for more than one device?
A patient can use more than one device, such as a blood pressure cuff and a scale. The practice still bills the device-supply code once per patient per 30-day period.
Is the 16-day rule still in effect for RPM?
Yes, for 99454. Since January 1, 2026, Medicare also pays for 2 to 15 days of data under 99445, and a practice bills one code or the other for each 30-day period.
Does RPM require an established patient relationship?
Yes. A provider in the billing practice must see the patient in person or by telehealth before the practice bills RPM.
Build an RPM Program Ready for Review
RPM records often sit in three places: a device platform, the EHR, and staff notes. When a records request arrives, pulling them into one file takes time most practices don't have.
TrueBlueMD runs remote patient monitoring and chronic care management for practices, with a clinical team that includes doctors employed directly by TrueBlueMD. Monitoring, documentation, and patient communication stay with one accountable team and are organized for review from the first reading.
Talk to TrueBlueMD about an RPM program built to hold up under review.
Book a Consultation