CPT Code 99454 Requirements for RPM Billing: 2026 Guide
Meet every CPT 99454 billing requirement in 2026. Rhythm360 automates documentation so every RPM claim is audit-ready. See how it works.
Last updated: October 19, 2026
Key Takeaways
- CPT 99454 covers device supply and automatic data transmission when patients send qualifying readings on at least 16 days in a 30-day monitoring period and is billed once per patient per cycle.
- Effective January 1, 2026, new code CPT 99445 fills the gap for 2–15 transmission days, while CPT 99454 remains the code for 16+ days, and the two codes are mutually exclusive.
- Key requirements include an FDA-cleared device, automatic data transmission, documented patient consent, and qualified provider oversight.
- Qualifying transmission days are counted at the patient level across all devices, using a rolling 30-day window that begins when monitoring starts.
- Rhythm360 tracks qualifying days automatically, consolidates multi-vendor device data, and generates audit-ready documentation to support compliant 99454 billing.
Talk With Rhythm360 About RPM Compliance
What Changed For RPM Device-Supply Codes In 2026
Effective January 1, 2026, the AMA CPT 2026 code set introduced two new codes that restructure the RPM device-supply billing landscape. CPT 99445, finalized in the CY 2026 Medicare Physician Fee Schedule final rule (CMS-1832-F), covers device supply and data transmission when a patient transmits qualifying data on 2 to 15 days of a 30-day period, closing a gap where monitoring work below the 16-day threshold previously generated no billable device-supply code. As noted above, 99454 still requires at least 16 qualifying transmission days. CPT 99470, also new for 2026, covers the first 10 minutes of monthly RPM treatment management, giving practices a billing option for lighter-touch management months.
The practical effect for cardiology practices is a device-supply decision that now depends on the per-cycle day count. A heart failure patient who transmits on 18 days one month bills under 99454. If that same patient transmits on only 12 days the following month, the claim switches to 99445. The code follows the data.
See How Rhythm360 Handles 99445 And 99454
CPT Code 99454 Requirements For Remote Patient Monitoring Billing
Every 99454 claim must meet specific requirements that map to named policy sources and clear thresholds a MAC reviewer will check.
- FDA-Cleared Device. The device must meet the FDA definition of a medical device. In the United States, CPT code 99454 requires an FDA-cleared medical device used under a clinician-directed plan of care and does not extend to patient-owned, patient-initiated consumer-grade wearables, regardless of any FDA-cleared features they may have.
- Automatic Transmission Of Readings. CMS requires data to be collected electronically and uploaded automatically to a secure location the billing practitioner can review; readings a patient types into a portal or reports by phone do not count.
- At Least 16 Qualifying Transmission Days In A 30-Day Period. CPT 99454 requires data collection and transmission for 16 or more days over a 30-day period, per CMS MLN901705 (December 2025) and the AMA CPT guidance stating not to report 99454 for monitoring of less than 16 days; MLN901705 frames the general remote monitoring requirement as 2–15 or 16+ days out of 30 days depending on the code descriptor.
- Once-Per-30-Days Billing Limit. Only one device-supply code may be billed per patient per 30-day period, never both 99445 and 99454 for the same cycle.
- Qualified Provider Ordering And Oversight. Only physicians and non-physician practitioners who can bill evaluation and management services can bill RPM. CMS does not require that remote patient monitoring services be ordered, nor that the ordering provider's name and NPI be included on the RPM claim.
- Documented Patient Consent. Consent must be obtained and documented at the time RPM is furnished. For a full discussion of consent documentation requirements, see the Rhythm360 guide to RPM billing guidelines.
Matching The Device-Supply Code To The Day Count: 0–1, 2–15, And 16–30 Days
Device-supply code selection now follows a simple day-count rule for each 30-day monitoring period.
Match the code to the day count for each 30-day period:
- 0–1 days: no device-supply claim.
- 2–15 days: CPT 99445.
- 16–30 days: CPT 99454.
Because the two codes are mutually exclusive, billing both in one cycle is a coding error that triggers denial and audit flags.
How Many Days Of Data You Need To Bill 99454
The 16-day rule is the single most common reason a clean-looking RPM claim is denied. Now that the code tiers are clear, the key question is what actually counts toward that 16-day threshold.
What counts as a qualifying transmission day. A qualifying transmission day requires physiologic data to be recorded and transmitted electronically by the connected device to a secure location where the billing practitioner can review it. A day qualifies if data is transmitted at any point during that calendar day, even a single transmission late in the evening. Days with no transmission do not count. Patient-reported readings or values manually entered into a portal do not satisfy the automatic-transmission requirement.
How multi-device readings combine. CPT 99454 counts qualifying transmission days at the patient level across the entire RPM program, not separately per device. For a heart failure patient using both a weight scale and a blood pressure cuff, transmissions from both devices are consolidated into a single patient-level day count. That means a day on which only the scale transmits and a separate day on which only the cuff transmits each count as one qualifying day, so the platform must aggregate across all device sources and apply CMS counting rules at the patient level. In a cardiology context, such as a patient with a CIED plus an RPM blood pressure sensor, the RPM device-supply day count applies only to the RPM physiologic monitoring program. The CIED is billed under its own device-specific codes (93294, 93295, 93296, 93297, or 93298 depending on device type and billing component) on their respective 90-day or 30-day cycles.
How the rolling 30-day window is defined. The CPT 99454 measurement period is a 30-day rolling cycle that begins when monitoring starts, not a calendar month. Practices tally qualifying distinct transmission dates within that 30-day window. The RPM device-supply codes run on a 30-day period, while the treatment-management codes (99457, 99458, 99470) run on the calendar month. CMS declined to align the two clocks, so practices must track both separately for every patient.
Timestamp precision matters. A blood pressure cuff that syncs at 11:58 PM one night and 12:02 AM the next can register as either one transmission day or two depending on which system's timestamp is used. Practices should validate raw device logs against the billing platform before claim submission.
Billing 99454 When Patients Use Multiple Devices
CMS treats the device-supply codes as "not additive": one device code per patient per 30-day period, never both 99454 and 99445, and never one per device, and a patient with a blood pressure cuff and a scale is billed once, with qualifying days combined at the patient level. Multiple devices do not generate multiple 99454 claims for the same period. The once-per-30-days limit is absolute regardless of how many FDA-cleared connected devices the patient uses simultaneously.
See Rhythm360 In Action For Multi-Device Patients
CPT 99454 Documentation Requirements: The Audit-Ready Chart Checklist
Growing DOJ and OIG scrutiny means every 99454 claim must stand up to an audit. The following checklist maps each documentation element to what a MAC reviewer expects to find in the chart.
The Department of Justice has begun pursuing RPM cases under the False Claims Act, and the HHS OIG's August 2025 follow-up report OEI-02-23-00261 proposed audit flags including many enrollees with no prior history at the practice and multiple devices billed per enrollee in one month.
- Clinical Rationale. The medical record must document the specific chronic or acute condition being monitored, such as heart failure or hypertension, and the medical necessity for remote physiologic monitoring. For cardiology patients, this includes the relevant diagnosis code and any supporting clinical history such as prior hospitalizations or decompensation events.
- Documented Consent. Consent must be obtained at the time RPM is furnished and retained in the patient record. The consent document should confirm the patient understands the service, the device, and their cost-sharing responsibility.
- Device Details. The record must identify the specific device supplied, confirm its FDA clearance status, and establish that it transmits data automatically rather than relying on patient entry. Retain evidence of the device's FDA clearance alongside the clinical rationale.
- Transmission Log. Audit-ready documentation for CPT 99454 should include complete, timestamped transmission logs showing the date, device or data source, and successful electronic transmission, aggregated at the patient level to establish the qualifying-day total.
- Billing Period And Qualifying-Day Count. The record must show the start and end dates of the 30-day monitoring period and the distinct count of qualifying transmission days. For a 99454 claim, that count must be 16 or greater. The day count must reconcile between the platform export and the submitted claim.
- Practitioner Oversight And Review. Documentation must reflect that the ordering practitioner reviewed the transmitted data. CMS does not require that RPM services be ordered, nor that the ordering provider's name and NPI be included on the RPM claim. Medicare documentation must be retained for at least 7 years from the date of service under 42 CFR 424.516(f), and state rules may require longer retention.
How Rhythm360 Automates CPT 99454 Requirements And Billing Documentation
Rhythm360 is built for the compliance and workflow demands that 99454 billing creates in 2026. For cardiology practices managing heart failure, hypertension, and CIED patients simultaneously, Rhythm360 tracks qualifying days, consolidates vendor-neutral device data from all major OEMs into one dashboard, and generates auditable billing documentation for 99454 and related RPM codes.

- Automated Qualifying-Day Tracking. Rhythm360 tracks each patient's transmission-day count in real time against both the 16-day threshold for 99454 and the 2–15-day tier for 99445. It flags patients at risk of falling short before the 30-day window closes.
- Vendor-Neutral Device Data Consolidation. The platform ingests data from all major OEMs, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into a single dashboard. This structure removes the need to reconcile transmission logs across separate portals when building a qualifying-day count.
- Auditable Billing Documentation. Rhythm360 generates timestamped transmission logs, qualifying-day summaries, and billing-period records for 99454 and related RPM codes that map directly to what a MAC reviewer expects to find in the chart.
- AI-Powered Alert Triage. The platform's AI-driven alert system reduces critical alert response times by up to 80%. It surfaces clinically significant events such as new-onset atrial fibrillation, significant weight gain in heart failure patients, and device anomalies so teams can act quickly.
- Revenue Capture Improvement. By automating CPT code capture and documentation accuracy, Rhythm360 helps practices achieve up to a 300% increase in revenue capture and profitability.
Explore Rhythm360 For 99454 Workflows
How 99454 Relates To 99453, 99457, 99458, And 99470
CPT 99454 is the device-supply code within a broader RPM code family. CPT 99453 covers one-time device setup and patient education, billed once per monitoring episode. CPT 99457 covers the first 20 minutes of monthly RPM treatment management and requires at least one real-time interactive communication. CPT 99458 is the add-on for each additional 20-minute increment. CPT 99470, new for 2026, covers 10–19 minutes of monthly management for lighter-touch months and is mutually exclusive with 99457 in the same period. For a detailed comparison of how 99454 and 99457 interact in a complete RPM billing workflow, see CPT 99454 Vs 99457: RPM Billing Differences Explained.
Frequently Asked Questions
What Is The Description Of CPT Code 99445?
CPT 99445 is a remote patient monitoring device-supply code, effective January 1, 2026, that covers the supply of an FDA-cleared connected device and the collection and automatic transmission of physiologic data when a patient transmits qualifying readings on 2 to 15 separate days within a 30-day monitoring period. It was created by the CY 2026 Medicare Physician Fee Schedule final rule to capture device-supply work that previously fell below the 16-day threshold required for CPT 99454. Like 99454, it is billed once per patient per 30-day cycle, and the two codes are mutually exclusive within the same period.
How Are New CPT Codes For Remote Patient Monitoring Changed In 2026?
The CY 2026 Medicare Physician Fee Schedule final rule (CMS-1832-F) introduced two new RPM codes effective January 1, 2026. CPT 99445 created a billable device-supply tier for 2–15 qualifying transmission days, converting the previous all-or-nothing 16-day threshold into a tiered structure. CPT 99470 created a lower-threshold treatment-management code covering 10–19 minutes of monthly management, below CPT 99457's 20-minute requirement. Together, these additions mean that shorter monitoring periods and lighter-touch management months that previously generated no billing can now produce a compliant claim when the day count and time documentation support the selected code.
Can You Bill 99454 And 99445 Together?
CPT 99454 and CPT 99445 are mutually exclusive for the same patient in the same 30-day period. A practice must bill one device-supply code based on the actual qualifying-day count for that cycle. If a patient transmits on 16 or more days, bill 99454. If the patient transmits on 2 to 15 days, bill 99445. Submitting both codes for the same patient in the same period will trigger an automatic mutual-exclusivity edit rejection from the payer.
What Happens If The Patient Has Only 14 Days Of Data?
A patient with 14 qualifying transmission days in a 30-day period does not meet the 16-day threshold for CPT 99454. The correct device-supply code for that cycle is CPT 99445, which covers 2–15 qualifying days. Billing 99454 when the documented day count is 14 is an audit risk and constitutes billing the incorrect code. Treatment-management codes 99457, 99470, and 99458 carry no qualifying-day requirement, so a management code can still be billed for that month if the time and live-interaction requirements are met and separately documented.
Conclusion: Make Every 99454 Claim Defensible
The 2026 introduction of CPT 99445 converted the RPM device-supply decision from a binary 16-day pass/fail into a per-cycle day count with two billable tiers and a hard mutual-exclusivity rule. For cardiology practices billing 99454, the compliance question is whether the practice can prove, with timestamped transmission logs and a reconciled qualifying-day count, that 16 or more days of automatically transmitted data exist in the 30-day window. Multi-device patients, rolling billing periods that differ from calendar months, and growing OIG and DOJ scrutiny make manual tracking a material audit risk.
Rhythm360 tracks qualifying days against both the 99454 and 99445 thresholds, consolidates device data from all major OEMs into a single auditable record, and generates the billing documentation a MAC reviewer expects so every 99454 claim your practice submits is supported before it leaves the building.
Get A Rhythm360 RPM Workflow Walkthrough
.avif)