CPT code 99454: Device supply, 16-day rule, 2026 rate

CPT code 99454 pays for the remote monitoring device itself, plus the daily readings or alerts it sends, across each 30-day period. One rule decides the claim. The device has to record or transmit data on at least 16 of those 30 days.

Months that fall short used to go unbilled. From 2026 they move to CPT code 99445 instead, which covers 2 to 15 days of data at roughly the same rate.

Medicare pays about $52 per 30-day period nationally for 99454, and an active panel bills it again every month. What follows is the rate, who may bill, the consent rule, and the denials worth heading off.

Found our content helpful?

Key takeaways

CPT code 99454 covers the supply of a remote monitoring device and its data transmission for each 30-day period.

The device must record or transmit data on at least 16 of the 30 days before the claim can go out.

The 2026 Medicare national rate sits at roughly $52 per 30-day period, and your locality rate will differ.

New for 2026, CPT code 99445 covers a period that captured only 2 to 15 days of device data.

Practice management software like Pabau pre-fills the claim from the patient record and submits it through our Claim.MD integration.

What CPT code 99454 actually pays for

CPT code 99454 pays for the device and the data, not for anyone’s time. The AMA-maintained descriptor reads “device supply with daily recordings or programmed alert transmissions, digitally stored and/or transmitted, each 30 days”. So the claim covers the equipment in the patient’s home and the stream of readings coming back from it.

That is why it can be billed again and again. As long as the patient keeps monitoring and the data keeps arriving, a new 30-day period starts and 99454 is billable once more. The clinician’s review time is paid separately, under the management codes further down this page.

The 16-day rule decides which code you bill

Four conditions have to be satisfied before a 99454 claim goes out, and the day count is the one practices trip over. Miss any of the other three and the claim is just as vulnerable in an audit.

• 16-day data minimum: The device must transmit or store data on at least 16 of the 30 days in the period. Days with no transmission are not counted.
• A 30-day period, not a calendar month: The period starts the day monitoring begins and runs 30 consecutive days. A period opening on January 10 closes February 8, not January 31.
• Documented patient consent: Written or verbal consent has to be recorded in the chart before RPM services start, never afterwards.
• A clinical order: An order from a physician or qualified healthcare professional initiating RPM must sit in the patient record before 99454 is billed.

What counts as a qualifying day

A qualifying day is any calendar day on which the device records or transmits at least one data point. A day the device failed to sync does not count. Neither does a day the patient left the cuff in a drawer, however good the reason.

That makes the day count something to watch during the period rather than after it. The chart below shows where each threshold lands.

Reaching day 28 with 13 days logged used to mean the period was written off. Now it means 99445 instead of 99454. The habit worth building is still the same. Check the count around day 20, while a call to the patient can still rescue the higher code.

Medicare pays about $52 per 30-day period

The 2026 national Medicare rate for CPT 99454 is roughly $52 per 30-day period under the CMS Physician Fee Schedule. Published lookups land between $47 and $52 depending on the source and the year cited, so treat $52 as the ceiling of the national range.

Your own number will differ. The Geographic Practice Cost Index adjusts every rate by locality, which lifts payment in Manhattan or San Francisco and trims it in rural counties. Run the fee schedule search for your locality before you model RPM revenue, and re-run it each January when the final rule lands.

Rates are approximate national Medicare figures and move with GPCI locality. Verify each one in the CMS Physician Fee Schedule before billing. Commercial payer coverage and rates for RPM are set by plan and contract.

Who can bill 99454, and who only supports it

Physicians, nurse practitioners and physician assistants can bill 99454, provided they have ordered the monitoring and hold an established relationship with the patient.

Per HHS telehealth guidance, the ordering clinician must already have treated the patient for the condition being monitored. Only one practitioner may bill RPM for that patient in a 30-day period.

Supervision and incident-to rules

Auxiliary staff can run the day-to-day device work under general supervision, which means the supervising physician does not have to be in the building.

Being reachable by phone or electronic means is enough. So a medical assistant can chase a patient whose cuff stopped syncing while the billing clinician keeps responsibility for the order.

Incident-to billing applies when that staff member delivers the service under supervision and the claim goes out under the physician’s NPI. The roles break down like this.

• Physicians (MD/DO): Bill directly under their own NPI.
• Nurse practitioners and physician assistants: Bill independently where state scope allows, or incident-to under a supervising physician.
• Clinical staff (MAs, RNs, care coordinators): Handle device logistics under general supervision, but cannot bill in their own right.
• Everyone else: Confirm your MAC’s policy, since several have published extra guidance on RPM provider eligibility.

The RPM family gained two codes in 2026

CPT code 99454 rarely travels alone. The American College of Physicians sets out how the codes work together across setup, device supply and clinical time. Bill only the device and you leave the management payment behind. Bill only the management codes and an auditor will ask what device produced the data.

99453 sets the patient up, 99454 keeps them going

CPT 99453 is the one-time setup code covering patient education and device onboarding. It is billed at the start of a program and cannot be repeated for the same patient.

Once setup is done, 99454 takes over and recurs every 30 days. Both codes can appear in the first period, with 99454 held back until 16 days of data are in.

99457 and 99458 pay for the clinician’s time

CPT 99457 covers the first 20 minutes of RPM management per calendar month, including at least one interactive conversation with the patient or caregiver. Each further 20 minutes is billed as 99458. Both need a qualified healthcare professional rather than auxiliary staff.

Worth knowing: the 16-day minimum does not reach these codes. A thin data month can still carry management time, provided the interactive contact happened.

Where 99445 and 99470 fit

The 2026 CPT set added two codes that soften the old thresholds. CPT 99445 covers device supply for a period holding 2 to 15 days of data, at roughly the 99454 rate. CPT 99470 pays for the first 10 to 19 minutes of management time, below the 20 minutes that 99457 demands.

Together they make short and low-intensity monitoring viable. A patient who only wears a device for a fortnight after discharge is now a billable episode rather than an awkward write-off.

Consent has to be on file before day one

CMS wants documented patient consent before any RPM service starts, device supply included. It has to be captured before the first 30-day period opens, not tidied up afterwards. A claim with no consent record behind it can be denied at submission or recouped years later at audit.

Verbal consent is acceptable if the clinician records the date, the time and a short note of what was discussed. Written consent gives you more to stand on when an auditor asks. Either way, the record needs to sit somewhere a colleague can find it in under a minute.

• What to document: Patient name, consent date, a description of the RPM service, the device type, and the clinician who took consent.
• Timing: Before the 30-day monitoring period begins, never after.
• Retention: Held in the medical record and produced on request.
• Re-consent: Not required for each new 30-day period, as long as the original consent covers ongoing monitoring.

How a 99454 claim moves from device to payer

A 99454 claim is assembled from three separate records: the order, the consent, and the device’s own transmission log. Knowing where each one comes from is what makes the difference between a claim that pays and one that bounces.

1. Day 1 — the period opens. The clinician’s order and the consent note are already in the chart, and the monitoring start date is recorded. That date, not the calendar, sets the end of the period.
2. Days 1 to 30 — the data accumulates. The device platform logs each day a reading arrives. This is the count an auditor will later ask to see.
3. Day 30 — the count is confirmed. Sixteen days or more means 99454. Between 2 and 15 means 99445. Fewer than 2 means no device claim at all.
4. Submission — the charge line is built. The code goes out with the period dates, the ordering provider’s NPI, and the diagnosis supporting medical necessity.
5. Remittance — the payer answers. An ERA posts the payment or the reason code, usually within two to four weeks for Medicare.

Run this check before you submit

Five questions, asked in order, catch nearly every preventable 99454 denial.

• How many qualifying days does the transmission log actually show?
• Is the consent note dated before the monitoring start date?
• Does the order name the condition being monitored?
• Do the period dates run 30 days from the start date rather than to month end?
• Has anyone else already billed RPM for this patient in this period?

Clearing all five is what turns a submission into a clean claim, and clean claims pay weeks sooner than reworked ones. Build the questions into the billing queue rather than leaving them to memory on a busy Friday.

The denials that come back most often

Five patterns account for the bulk of rejected 99454 claims. Read the denial codes your clearinghouse returns before reworking the claim, because the reason code tells you whether the problem is documentation or dates.

• Fewer than 16 qualifying days: The classic. From 2026 the answer is usually to bill 99445 rather than to appeal the 99454.
• Missing consent documentation: No evidence that consent was taken and recorded before monitoring began. Adding it later does not repair the claim.
• Wrong period dates: Calendar month dates used in place of the 30-day rolling window that starts on the monitoring date.
• No clinical order in the chart: Auditors look for the order that initiated monitoring, and they look for it first.
• Duplicate or overlapping billing: 99454 and 99091 submitted for the same patient and period, or a second practitioner billing RPM for the same 30 days.

Denials in this code rarely arrive one at a time. A team that gets the period dates wrong tends to get them wrong across the whole panel. Treat a single rejected claim as a sample, not an incident.

How Pabau keeps 99454 claims moving

One monitoring period is easy to track. Fifty of them, each with a separate start date, day count and consent record, is where billing teams lose their afternoons. That volume is the point at which a spreadsheet gives way to claims software for practices.

Pabau, our practice management software, keeps the claim beside the record it came from. The CPT code attached to the service lands on the charge line, and ICD-10 slots are seeded from the patient’s recorded problem list. Required fields are checked before the send button unlocks, so a claim missing an authorization number stays put.

From there, US claims reach Medicare and commercial payers through our Claim.MD integration. Eligibility is checked in advance, remittances post back against the invoice, and claim status is visible without a call to the payer. Practices billing elsewhere route through Healthcode in the UK or Tyro Health in Australia.

Send cleaner RPM claims from the patient record

Pabau pre-fills the claim from the encounter, checks that required fields are complete, and submits to Medicare and commercial payers through our Claim.MD integration. Consent and orders stay attached to the record, so an audit request takes minutes rather than days.

Book a demo

Conclusion

The 2026 code set made 99454 less of a cliff edge. A short monitoring month is now a different code rather than lost revenue, which takes some of the pressure off the day count. It does not take away the need to watch it.

What still decides the claim is the paperwork behind it. An order naming the condition, a consent note dated before day one, and period dates tied to the monitoring start will survive an audit. A panel tracked on a spreadsheet eventually will not.

Is your RPM program growing faster than the billing process behind it? Book a demo and see how Pabau assembles 99454 claims straight from the patient record.

Continue your research

Need to understand the clearinghouse behind your RPM claims? Our Claim.MD clearinghouse guide explains how electronic claims reach Medicare and commercial payers after submission.

Getting denials on RPM claims and not sure why? Denial codes in medical billing breaks down the CARC codes your clearinghouse returns and how to answer them.

Want to see how the 837P transaction carries an RPM claim? Our 837 file guide walks through the EDI format that takes your CPT 99454 claims to payers.

Reading the payer’s answer to a 99454 claim? Electronic remittance advice explains how to read an ERA and post it against the right invoice.

Enrolling a new monitoring patient this week? Insurance eligibility verification covers the checks worth running before the device leaves your office.

Frequently asked questions