The Problem: Two Clocks
RPM billing operates on two fundamentally different timing systems. Device supply codes (99454, 99445) run on 30-day rolling cycles that start from each patient's individual enrollment date. Clinical time codes (99457, 99458, 99470) reset on calendar month boundaries — the 1st of each month, regardless of when the patient enrolled.
Notice the misalignment
Device Cycle 1 ends Feb 13, but the clinical calendar month runs through Feb 28. By month 3, the two clocks are nearly two weeks apart — creating reconciliation headaches for billing teams.
Why this matters: Your device codes and clinical codes are never guaranteed to be on the same schedule. A patient who starts January 15 has a device window that ends February 13 — but their clinical time resets February 1. By month three, the two clocks are nearly two weeks apart.
RPM CPT Code Reference
Six CPT codes govern RPM billing — split into two groups based on their timing cycle. The new 2026 codes (99445 and 99470) serve as safety nets for partial billing periods.
Device Supply Codes
30-Day Rolling Cycle
Initial Device Setup
One-time setup and patient education for RPM devices
Requirement: Once per patient per enrollment
Device Supply (16–30 Days)
30-day supply of RPM devices with daily data transmission for 16+ days
Requirement: 16–30 days of data in 30-day period
Device Supply (2–15 Days)
RPM device supply for 2–15 days of data transmission — same rate as 99454
Requirement: 2–15 days of data in 30-day period
Clinical Time Codes
Calendar Month Cycle
Clinical Time (First 20 min)
First 20 minutes of clinical staff time for RPM data review and patient interaction
Requirement: 20+ minutes in calendar month
Clinical Time (Each Add'l 20 min)
Each additional 20 minutes of clinical staff time beyond the first 20
Requirement: Each additional 20 min in calendar month
Clinical Time (10–19 min)
10–19 minutes of clinical staff time when the full 20-minute threshold for 99457 is not met
Requirement: 10–19 minutes in calendar month
For detailed CPT code documentation, see our Complete RPM Billing Guide and RPM & CCM CPT Codes Guide 2026.
Calendar Month vs. Rolling 30-Day
Two approaches exist for managing the device supply clock. Calendar month billing aligns everyone on the same schedule. Rolling 30-day billing maximizes each patient's individual window.
Approach A: Calendar Month
Bill all patients on the 1st of each month
6-Month Billing Cycles
Advantages
- All patients bill on the same schedule
- Aligns with payer expectations and clearinghouse cycles
- Simpler compliance and audit trail
- Industry-recommended by Prevounce, ThoroughCare, CoachCare
- Lower denial rates across all payers
Trade-offs
- First month may be partial (fewer billable days)
- ~$36/patient/year less revenue than rolling
- February (28 days) falls short of 30-day device minimum
Approach B: Rolling 30-Day
Bill each patient from their individual start date
6-Month Billing Cycles
Advantages
- Maximizes every 30-day window per patient
- Captures 12–13 device cycles per year (vs 11–12)
- ~$36/patient/year more revenue
Trade-offs
- Every patient has a different billing date
- Requires per-patient tracking software
- Higher denial rates from misaligned claim periods
- Audit complexity increases with patient count
- Staff must track individual cycles manually or via software
Calendar month is the right choice for most practices. Backed by industry consensus — Prevounce, ThoroughCare, CoachCare, and Chronic Care Staffing all recommend it. Simpler operations, lower denial rates, and easier audits. Rolling 30-day only makes sense with robust tracking software and high patient volume where the extra ~$36/patient/year justifies the complexity.
The Full Billing Flow, Step by Step
The best way to understand the two approaches is to follow the same patient through the first four months under each one. Let's say a patient starts RPM on January 5th.
Calendar Month Billing
Device monitoring period = the calendar month. All patients bill on the same schedule.
Jan 5 — Device arrives, patient starts monitoring
Bill 99453 ($21.71) for initial setup. The monitoring period is January (whatever's left of it).
Jan 5–31 — 27 days of monitoring available
Patient takes daily readings. By Jan 20 (day 16), the 16-day threshold is met. Bill 99454 ($52.11).
Feb 1 — Next billing period starts
Regardless of when the patient started, everyone's next period begins Feb 1. February has 28 days — short of the 30-day minimum for 99454, so you bill 99445 ($52.11, same rate).
Mar 1 → Apr 1 → May 1 — Repeats monthly
Each month is one billing period. Bill 99454 for months with 30+ days, 99445 for February. At end of each month, batch-submit device + clinical codes together.
Full year result: 12 billing periods (one per month), but the first month was partial. Effectively ~11.5 full device cycles worth of monitoring time.
Rolling 30-Day Billing
Device monitoring period = exactly 30 days from each patient's start. Next cycle begins the day after the previous ends.
Jan 5 — Device arrives, patient starts monitoring
Bill 99453 ($21.71) for initial setup. The monitoring period is Jan 5 → Feb 3 (exactly 30 days).
Jan 5 – Feb 3 — Full 30-day window (Cycle 1)
Patient takes daily readings. By Jan 20 (day 16), the threshold is met. Bill 99454 ($52.11) after the window closes.
Feb 4 — Next 30-day window starts immediately
No waiting for a new month. Cycle 2: Feb 4 → Mar 5. Again exactly 30 days. February's short length doesn't matter — the window crosses into March.
Mar 6 → Apr 4 → May 4 → Jun 3 — Repeats every 30 days
Each cycle is exactly 30 days. The next cycle begins the day after the previous one ends. No gaps, no "wasted" days in 31-day months. But every patient has a different schedule.
Full year result: 365 days ÷ 30 days = ~12.2 device cycles. No partial first month. No February problem. But clinical time codes (99457/99458) are still calendar month — so you're managing two different schedules.
Where the ~$36/Patient/Year Gap Comes From
Rolling billing fits in about 0.7 extra device cycles per year because it never wastes the extra day in 31-day months and never has a February gap. Calendar month billing "throws away" those extra days because each month is one billing period regardless of length.
~11.5
Calendar cycles/yr
~12.2
Rolling cycles/yr
+$36
Per patient/yr
0.7 extra cycles × $52.11 per cycle = ~$36. Clinical time codes (99457/99458/99470) are the same in both approaches — the entire gap is from device supply billing only. For a 100-patient program, that's ~$3,650/year — a 3% increase that comes with higher denial rates, per-patient tracking software, and more staff overhead.
Patient Start Date Scenarios
When a patient starts RPM determines how much revenue you can capture in their first month. The interactive tool below shows the impact of five common enrollment timing scenarios.
Patient starts January 1
31 days remaining in first month
First Month Revenue
$103.88
Recommendation: Best case — both clocks perfectly aligned for the entire first month.
The Reporting & Compliance Challenge
The two clocks problem isn't just about billing math. When device readings and clinical documentation operate on different calendars, every downstream process gets harder — from monthly reports to audit preparation.
Monthly Reports Don't Match
Your clinical reports run January 1–31. But a patient who enrolled January 15 has a device cycle running January 15 → February 13. When you pull a January compliance report, which readings count? The device data spans two clinical months, and the clinical month contains only a partial device cycle.
Audit Trail Complexity
If audited, you need to prove two separate things for the same patient: 16+ days of device data within a 30-day window (for 99454), and 20+ minutes of clinical time within a calendar month (for 99457). These reference different date ranges, require different documentation, and must be reconciled against each other.
Care Coordination Confusion
A nurse reviewing patient data on March 1 sees the clinical month has reset — but the patient's device cycle, which started February 15, still has 14 days left. Is the patient "non-compliant" with their device? No — they're mid-cycle. But the monthly dashboard doesn't show that context.
EHR Reconciliation
Your EHR tracks encounters by calendar month. Your RPM platform tracks device data by rolling 30-day cycles. Reconciling claims between these two systems requires manual date mapping for every patient — or specialized integration software that translates between the two timelines.
Example: Patient Enrolled January 15
What your billing team sees on March 1
Device Clock Says
Current cycle: Feb 14 → Mar 15
Days of data so far: 15 of 30
Status: Mid-cycle — not yet billable
Clinical Clock Says
Current period: March 1 → March 31
Clinical time this month: 0 minutes
Status: New month — timer reset
On March 1, the billing team sees a patient with zero clinical minutes and an incomplete device cycle — even though the patient has been continuously monitored since January 15. Without understanding both clocks, this looks like a compliance problem when it's actually normal operation.
The hidden cost: this operational complexity is what the ~$36/patient/year revenue gap doesn't capture. Every staff member who touches billing, reporting, or compliance has to mentally translate between two different date systems — or your software has to do it for them.
The February Problem
February is the only month shorter than the 30-day minimum required for CPT 99454. This affects every RPM patient in calendar month billing programs — and CMS has never published guidance on how to handle it.
Days Per Month vs. 30-Day Minimum
Jan
31
Feb
28
Mar
31
Apr
30
May
31
Jun
30
Jul
31
Aug
31
Sep
30
Oct
31
Nov
30
Dec
31
February has only 28 days (29 in leap years) — 2 days short of the 30-day minimum required for CPT 99454. Without intervention, you cannot bill 99454 for February under calendar month billing. This affects every single RPM patient in your program.
Three Solutions
Choose the approach that fits your practice
Start the March device cycle on March 3 instead of March 1. This gives you a full 30-day window (March 3 → April 1) and lets you bill 99454 with a clean 30-day period.
Clean 99454 billing with full 30-day compliance documentation
Creates a 2-day gap where no device code is active
Timeline Adjustment
Standard (fails in February)
Adjusted (push March to 3rd)
Revenue Impact by Patient Count
The revenue difference between calendar month and rolling 30-day billing scales linearly with patient count — but so does the operational complexity.
Annual Revenue by Patient Count
| Patients | Calendar Month | Rolling 30-Day | Annual Delta |
|---|---|---|---|
| 50 | $61,026 | $62,849 | +$1,824 |
| 100 | $122,051 | $125,698 | +$3,647 |
| 200 | $244,102 | $251,396 | +$7,294 |
| 500 | $610,256 | $628,490 | +$18,234 |
Key insight: The revenue difference between approaches is modest — about $36 per patient per year. For a 100-patient program, that's ~$3,650 annually. But rolling 30-day billing comes with higher denial rates, more staff overhead, and greater audit complexity. Most practices find the operational savings of calendar month billing outweigh the incremental revenue.
Optimization Recommendations
For All Practices
Start patients in the first week
Batch new RPM enrollments during days 1–7 of each month to maximize first-month reimbursement for both device and clinical codes.
Use 99445 and 99470 for partial months
Never lose revenue on late-month starts or short months. The new 2026 codes capture partial-period revenue that was previously unbillable.
Track clocks separately
Whether you use calendar month or rolling, maintain clear records of both the device supply window and clinical time accumulation for each patient.
Plan for February every year
Build your February billing strategy before December. Choose push-March, bill-99445, or rolling-30 and document it in your billing procedures.
Calendar Month Practices
Push March forward by 2 days
Run February device cycles as Feb 1–Mar 2 (30 days) and shift March to Mar 3–Apr 1. This preserves full 99454 reimbursement.
Handle late-month starts proactively
If a patient starts after the 20th, bill 99445 + 99470 for the partial first month, then switch to standard codes starting the following month.
Rolling 30-Day Practices
Invest in tracking software
Manual rolling cycle tracking breaks down at 20+ patients. RPM platforms like CCN Health automate per-patient cycle management.
Bill every 31 days as a buffer
Use 31-day cycles instead of exactly 30 to build in a buffer day. This prevents edge cases where a reading arrives hours after the window closes.
Frequently Asked Questions
01What is the two clocks problem in RPM billing?
RPM billing operates on two different timing cycles simultaneously. Device supply codes (99453, 99454, 99445) run on 30-day rolling cycles tied to each patient's individual enrollment date. Clinical time codes (99457, 99458, 99470) reset on calendar month boundaries (the 1st of each month). These two clocks gradually drift apart, creating reconciliation complexity for billing teams — especially when a patient's 30-day device window ends mid-month while clinical codes reset on the 1st.
02Should I use calendar month or rolling 30-day billing for RPM?
Calendar month billing is recommended for most practices. Every major RPM platform vendor (Prevounce, ThoroughCare, CoachCare, Chronic Care Staffing) recommends it. Calendar month billing aligns all patients on the same schedule, simplifies compliance, and results in lower denial rates. Rolling 30-day billing captures approximately $36 more per patient per year, but requires per-patient tracking software and creates significantly more operational complexity.
03How do I handle February in RPM billing?
February has only 28 days (29 in leap years), which falls short of the 30-day minimum for CPT 99454. Three solutions exist: (1) Push the March device cycle forward by 2 days so February runs from Feb 1 to Mar 2, creating a full 30-day window. (2) Accept the 28-day February and bill 99445 instead — CMS set 99445 at the same rate as 99454 ($52.11), so there is no revenue loss. (3) Use rolling 30-day billing, which naturally crosses February boundaries without issues.
04What are CPT codes 99445 and 99470?
CPT 99445 and 99470 are new codes finalized for 2026 that serve as safety nets for partial billing periods. 99445 covers device supply for 2–15 days of data transmission at the same rate as 99454 ($52.11) — CMS intentionally set them equal because device supply cost is the same regardless of transmission days. 99470 covers 10–19 minutes of clinical time ($26.05), compared to 99457 which requires 20+ minutes ($51.77). These codes let practices capture partial-period revenue that was previously lost entirely.
05When should patients start RPM to maximize billing?
Patients should ideally start RPM in the first week of each month. Starting on the 1st gives you the maximum 31 days for both device and clinical codes. Starting between the 5th and 10th still provides enough days for full 99454 (16+ days) and 99457 (20+ minutes). Starting after the 15th becomes tight, and starting after the 25th typically requires using the partial-period safety net codes (99445/99470) for the first month.
06How much more revenue does rolling 30-day billing generate?
Rolling 30-day billing generates approximately $36 more per patient per year compared to calendar month billing. For a 100-patient program, that amounts to roughly $3,650 annually. However, this incremental revenue must be weighed against higher denial rates, increased staff overhead for per-patient cycle tracking, greater audit complexity, and the need for specialized RPM billing software that can manage individual patient cycles.