RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →Deep dives on the most common 99454 pitfalls and how to keep billing defensible.
Why extending the 30-day window to “reach 16 days” misstates the billed unit and risks denials.
Read the Block Stretching GuideHow pausing cycles until adherence returns can appear as period manipulation and beneficiary inducement exposure.
Read the Block Gapping GuideRPM uses FDA-defined medical devices to collect physiologic data at home (e.g., blood pressure, weight, glucose, pulse oximetry) and automatically transmit it to your team for review and treatment decisions.
Medicare allows RPM for acute or chronic conditions when remote monitoring is medically reasonable and necessary – for example uncontrolled hypertension, high-risk heart failure, brittle diabetes, or high-risk COPD.
RPM is not a video visit and not self-reported symptoms. It’s continuous physiologic data plus documented clinical management time, billed under a specific set of Part B codes.
In Medicare’s rules, RPM is distinct from other programs: it uses physiologic data only (RTM covers self-reported symptoms and therapy), requires automatic electronic transmission of data from a medical device, can support acute or chronic conditions, and may run alongside programs like CCM or APCM as long as the work and minutes are documented separately.
Start with established patients whose conditions genuinely benefit from home monitoring: uncontrolled hypertension, high-risk heart failure, complex diabetes, COPD, post-discharge risk, etc. RPM is billed per patient, not per diagnosis, and only one practitioner can bill it per month.
Explain RPM, including Part B coinsurance, responsibilities, and how long they’ll be monitored. Obtain and document consent (verbal or written) and capture a baseline plan so medical necessity is clear in the chart.
Provide a connected medical device (cellular, Wi-Fi, or equivalent) that automatically uploads data. Track usage so you know which patients meet the “16 days of data in 30 days” requirement for the device codes.
Clinical staff and clinicians review incoming data, triage alerts, adjust medications, and communicate with the patient. You log this time so you can bill the 20-minute management blocks and defend those claims in an audit.
To survive an audit, RPM must be more than a "data dump." You need a condition-specific protocol that dictates exactly when your team intervenes.
| Condition | Device Strategy | Alert Thresholds (Examples) | Clinical Action Protocol |
|---|---|---|---|
| Hypertension | BP Cuff (Daily AM/PM) |
Critical SBP > 180 or DBP > 110 Urgent SBP > 150 (2+ days) |
Assess med compliance/diet. If >150 for 1 week, escalate to MD for titration. |
| Heart Failure | Weight Scale (Daily) | Critical Weight ↑ >3 lbs in 24h | Nurse call same day to assess edema/SOB. Consider diuretic dose adjustment per standing order. |
| Diabetes | Glucometer/CGM | Critical Glucose < 70 or > 300 | Immediate outreach. For hypo: advise fast-acting carb. For hyper: check ketones/illness. |
There is no hard “21-diagnosis list” in the rules. The real test is whether physiologic monitoring is medically necessary and used to guide care.
Under Medicare, RPM devices must be medical devices that automatically upload data. Hand-typed logs and symptom surveys don’t qualify.
Connected cuffs are the backbone of RPM for hypertension, heart failure, and kidney disease.
Used for heart failure, CKD, and obesity-related programs where daily weight trends matter.
Glucose meters or CGM bridges for diabetes management, when trends are actively managed between visits.
Oximetry and other physiologic sensors where remote monitoring can realistically change decisions.
Devices can be shipped or supplied in-clinic, and many patients can also bring their own devices (BYOD) as long as they meet the medical device and automatic transmission requirements. Just note that the device-supply codes (99445/99454) generally require the practice to supply the device; BYOD scenarios typically support only the management codes, not the device-supply codes.
RPM is primarily a Medicare Part B benefit today, with broad but not universal adoption by Medicare Advantage, Medicaid, and commercial plans. You should always confirm specific payer policies, but the high-level pattern is consistent.
Effective January 1, 2026, the "all or nothing" 16-day rule is gone. You must now select the precise code based on data volume and time spent.
| Category | Code | Requirements (2026 Rules) | Approx. Rate* |
|---|---|---|---|
| Setup | 99453 | Initial Setup & Education. Billed once per episode of care. Requires the device to be used for at least 16 days in the first 30-day period to be payable. | ≈ $19 (one-time) |
| Device Supply (Select ONE per 30 days) |
99445 NEW | Low-Volume Data (2–15 Days). Covers device supply and transmission when 2 to 15 days of data are collected. Replaces write-offs. | ≈ $47 |
| 99454 | Standard Data (16–30 Days). Covers device supply and transmission when 16+ days of data are collected. | ≈ $47 | |
| Management (Select ONE base code) |
99470 NEW | Brief Management (10–19 Mins). Requires at least one interactive communication. Use when time does not reach the full 20 minutes. | ≈ $26 |
| 99457 | Standard Management (20 Mins). Requires 20+ minutes of clinical staff time and at least one interactive communication. | ≈ $48 | |
| 99458 | Add-on (Additional 20 Mins). Billed in addition to 99457 for extra blocks of time. (Cannot be billed with 99470). | ≈ $42 |
Stop using G0511 for RPM. As of January 1, 2026, the bundled G0511 code is obsolete for RPM services. RHCs and FQHCs must now unbundle and report the individual CPT codes (99453, 99454, etc.) to receive payment. Continued use of G0511 will result in denials.
The OIG is no longer just "watching." They are auditing based on specific quantitative patterns. Here are the exact signals we monitor to keep your practice safe.
OIG Signal: Patient enrollment increasing by >150% in a single month is a primary fraud indicator.
The Fix: Avoid mass-enrollment events. Ensure every patient has a prior E/M visit and documented medical necessity before enrollment.
OIG Signal: 43% of RPM patients failed to receive all three required components: Education, Device Supply, and Management.
The Fix: Never bill a monthly cycle unless you can prove Data Transmission AND Interactive Management occurred in the same period.
OIG Signal: Vendor fees calculated as a % of reimbursement or "per patient" fees for redundant services (Advisory Opinion 25-08).
The Fix: Ensure your vendor charges a Fair Market Value (FMV) flat fee for technology, unrelated to your billing volume.
Before submitting any RPM claim, run this 4-point check to prevent automated denials.
Use this FAQ as a reference when you’re designing or tuning your program. It focuses on how RPM actually works under current Medicare rules.
No. Medicare allows RPM for acute or chronic conditions when remote physiologic monitoring is medically necessary and will be used to guide treatment. Chronic conditions (hypertension, heart failure, diabetes, COPD, CKD, etc.) are most common, but short-term acute monitoring can also be appropriate when it truly changes care.
The 16-day rule currently applies to 99453 and 99454 – the setup and device supply codes – which require monitoring over at least 16 days in a 30-day period. It does not apply to 99457/99458, which are purely time-based treatment management codes.
Starting in 2026, 99445 will cover 2–15 days of transmitted data and the existing 99454 will be reserved for 16–30 days. For each 30-day period you pick the single device code (99445 or 99454) that matches the days of data; they are not additive.
In many cases, yes – RPM can be billed in the same month as CCM, APCM, or other care-management codes as long as you don’t double-count the same minutes or services.
You cannot bill both RPM and RTM for the same patient in the same period, and you must be able to explain which program covers which work. Within each category you also pick the single code that fits (e.g., 99445 or 99454 for devices; 99470 or 99457 for base management) rather than stacking multiple base codes for the same month. If you can’t clearly separate the minutes, don’t stack the codes.
RPM is a Part B service, so standard Part B cost-sharing applies: Medicare typically pays 80% of the allowed amount and the patient is responsible for 20% coinsurance, plus any unmet deductible. Medigap or secondary coverage may absorb some or all of that, but you can’t assume RPM is “free.”
Clear, upfront communication about coinsurance is critical to avoid patient surprise bills and reputation damage.
For 99457, you must document at least 20 minutes of treatment management time in the calendar month, including interactive communication with the patient or caregiver. From 2026 onward, 99470 gives you a 10-minute management option for lighter-touch months. Each 99458 adds another 20 minutes in the same month when justified.
Time should reflect real work: reviewing data, triaging alerts, adjusting the plan, communicating with the patient, and documenting those decisions. “Rubber-stamping” a dashboard once a month is not defensible.
OIG and payers are focused on patterns such as:
If your documentation can clearly answer “why this patient, why this device, why this amount of time,” you are operating where RPM was intended to be.
High Risk. The OIG has issued unfavorable opinions regarding vendor fees calculated as a percentage of reimbursement or "per-patient" fees where the vendor provides redundant services.
These arrangements can be viewed as kickbacks or referral payments. The safest model is a Fair Market Value (FMV) flat fee for technology and support services, regardless of how much you bill.
FairPath is built on operational work, not theory. We publish the playbooks and checklists we use to keep programs compliant and profitable. Use them whether you run FairPath or not.
Browse the Expert Library →The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →How to run Remote Therapeutic Monitoring for MSK, respiratory, and CBT workflows with the correct 9897x and 9898x rules.
Read the RTM Guide →Calendar-month operations for CCM: consent, initiating visit, care plan requirements, time counting, and concurrency rules.
Read the CCM Guide →The operator blueprint for Advanced Primary Care Management: eligibility, G0556–G0558 tiers, and monthly execution.
Read the APCM Playbook →