CPT 99453/99454 RPM Billing Rules & Documentation 2026

CPT 99453 and 99454 Remote Patient Monitoring Billing Rules and Documentation: The 2026 Clinical Playbook

Merry AI · Thoughtfully curated clinical briefs.

CPT 99453 pays once per episode of care for remote patient monitoring (RPM) device setup and patient education. CPT 99454 pays once per 30-day period for supplying an FDA-defined medical device that automatically transmits physiologic data on at least 16 days. For 2026, CPT and the CMS Physician Fee Schedule add CPT 99445 for 2 to 15 days of data in a 30-day period. Both codes require an established patient relationship, documented consent, and a clinically justified order tied to an acute or chronic condition.

This playbook gives Practice Administrators and CMOs the 2026 statutory thresholds, documentation elements, audit defenses, and revenue math needed to run a compliant RPM program. For jurisdiction-specific AI documentation requirements, see the State AI Scribe Rules & Statutory Compliance Hub.

CPT 99453 is billed once per episode, not once per month

The setup code covers initial device configuration and patient education on device use. It is billable only once per episode of care. An episode begins when RPM starts and ends when the targeted treatment goals are met. A new episode, and a new 99453, requires a clinically distinct reason to restart monitoring. A lapsed device or a replacement unit does not qualify.

Clinical staff may perform setup under the billing practitioner's general supervision, so a medical assistant or nurse can educate the patient in clinic or by phone. The service is not billable until monitoring meets the minimum day threshold. Under the 2026 CPT revisions, that minimum aligns with the new 2-day floor, so confirm adoption with each commercial payer before you change billing logic.

Document these setup elements every time:

• Date of setup and the staff member who performed it.
• Device make, model, and FDA medical device status.
• Education topics covered, including measurement technique, transmission schedule, and alert escalation.
• Patient teach-back confirmation or a caregiver competency note.

CPT 99454 requires 16 or more days of automated transmission per 30 days

The device supply code reimburses the device, its connectivity, and daily recordings or programmed alerts. The 16-day minimum applies within each 30-day period, not each calendar month. Readings must be transmitted digitally and automatically. Patient-reported values entered by hand, typed into a portal, or read aloud over the phone do not count toward the threshold.

Only one practitioner may bill 99453 and 99454 for a given patient in a 30-day period, even when the patient uses several devices. When a cardiologist and a primary care physician both monitor the same patient, the practice that bills first holds the claim. The other practice receives a denial. Coordinate RPM ownership in referral workflows before enrollment.

Callout: Count transmission days per 30-day period, never per calendar month.

CPT 99445 captures 2 to 15 monitoring days starting in 2026

The CY2026 Physician Fee Schedule recognizes CPT 99445 for device supply when data transmit on 2 to 15 days in a 30-day period. This addresses the most common historical denial: patients who monitored on 12 or 14 days and produced no billable device claim. It also covers short-duration clinical needs such as post-discharge heart failure surveillance.

Treat 99445 and 99454 as mutually exclusive for the same 30-day period. Bill 99454 at 16 or more days and 99445 at 2 to 15 days. Bill neither below 2 days. Medicare Advantage and commercial adoption varies, so build payer-specific rules in your billing system rather than assuming parity with traditional Medicare.

CPT 99470 adds a 10-minute treatment management tier in 2026

RPM treatment management codes are separate from 99453 and 99454. CPT 99457 covers the first 20 minutes of clinical staff or practitioner time per calendar month, and 99458 covers each additional 20 minutes. Both require at least one real-time interactive communication with the patient or caregiver. New for 2026, CPT 99470 covers the first 10 minutes for practices that do not reach the 20-minute threshold.

Time-based codes demand contemporaneous logs that show date, duration, staff credential, and the clinical decisions that followed data review. Retrospective time estimates are the documentation pattern most frequently cited in RPM audit findings.

RPM eligibility requires an established patient, consent, and an FDA device

CMS reinstated the established patient requirement after the Public Health Emergency ended. Practices should complete a qualifying face-to-face or telehealth evaluation before enrolling a patient. Consent may be obtained at the time services begin. It must be documented and must disclose any cost-sharing obligations.

The device must meet the FDA definition of a medical device under section 201(h) of the Federal Food, Drug, and Cosmetic Act. FDA clearance or approval is not required, but consumer wellness wearables that fall outside the device definition do not qualify. Keep the device's regulatory documentation on file for each model you deploy.

RPM may be billed alongside Chronic Care Management (CCM), Principal Care Management (PCM), Transitional Care Management (TCM), and Behavioral Health Integration. It may not be billed with Remote Therapeutic Monitoring (CPT 98975 to 98981) for the same patient during the same period. Time counted toward one care management code cannot be counted toward another.

OIG found 43% of Medicare RPM enrollees lacked complete service components

The HHS Office of Inspector General's September 2024 report (OEI-02-23-00260) found that roughly 43% of Medicare RPM enrollees did not receive all three components of RPM: education and setup, device supply, and treatment management. OIG also flagged gaps in documentation of the condition being monitored. Expect 2026 targeted probe-and-educate reviews to focus on these patterns.

Auditors now test four questions:

• Is there a documented order linking the device to a specific diagnosis?
• Do transmission logs prove the day count billed for each 30-day period?
• Did a clinician act on the data, or was it only collected?
• Was RPM billed by more than one practitioner in overlapping periods?

Medical necessity documentation must name the diagnosis and the physiologic target

Every RPM order should specify the monitored parameter, the clinical threshold that triggers intervention, and the goal that ends the episode. A hypertension order coded to I10 (ICD-10-CM) should state the target blood pressure and the escalation threshold. A heart failure order coded to I50.9 (ICD-10-CM) should define the weight-gain alert, for example 2 pounds in 24 hours or 5 pounds in a week.

Use specific ICD-10-CM codes wherever the record supports them. I50.9 is acceptable when heart failure type is truly undocumented. Coding to type and acuity (for example, I50.22 for chronic systolic heart failure) strengthens the medical necessity chain and supports higher-complexity E/M levels at follow-up.

Clinical indicators, MDM thresholds, and audit defenses by condition

California SB 1120 requires licensed clinicians to make RPM medical necessity decisions

California SB 1120, the Physicians Make Decisions Act, took effect January 1, 2025. It prohibits health plans and disability insurers from using artificial intelligence or algorithms to deny, delay, or modify care based on medical necessity without review by a licensed physician or qualified health care professional. For RPM programs, payer utilization review of device authorization must rest on individualized clinical records, not automated scoring alone.

Practices should mirror this standard internally. Algorithmic alerts may flag readings, but a clinician must document the interpretation and the resulting decision. That human-attested decision record is your strongest defense when a payer challenges medical necessity. Review state-by-state variations in the State AI Scribe Rules & Statutory Compliance Hub.

CPT G2211 recovers $15,600+ annually from RPM-linked longitudinal care

RPM patients are, by definition, patients with ongoing condition management. Their follow-up office visits often qualify for HCPCS G2211, the visit complexity add-on for practitioners who serve as the continuing focal point for a patient's care or who provide ongoing care for a single serious or complex condition. Since CY2025, CMS allows G2211 with modifier 25 when the separately billed service is an Annual Wellness Visit, vaccine administration, or Medicare Part B preventive service.

Merry AI revenue modeling shows that consistent G2211 capture recovers $15,600 or more per full-time clinician per year. The gap is almost always documentation: notes fail to state the longitudinal relationship that justifies the add-on. Architecture details are in CPT G2211 Complexity Capture Architecture.

Callout: Every RPM follow-up visit is a G2211 capture opportunity. Document the relationship.

RPM documentation labor costs $48,000 per MA versus $648 for Merry AI Pro

A fully loaded medical assistant costs a practice approximately $48,000 per year once wages, benefits, payroll taxes, and training are included. Much of that labor goes to logging RPM time, reconciling transmission days, and drafting interactive communication notes. Merry AI Pro costs $648 per year ($54 per month, billed annually), which is 1.3% of that labor denominator.

Merry AI structures RPM encounter notes around the elements auditors test: the monitored parameter, the threshold crossed, the clinician's interpretation, and the action taken. Notes are drafted for clinician review and attestation, which preserves the human decision record that SB 1120-style standards require.

Browser overlay architecture deploys RPM documentation without EHR integration projects

Most RPM vendor platforms sit outside the EHR, so staff copy data between systems. A browser overlay works on top of any web-based EHR, so documentation lands in the chart without a multi-month API integration or interface fees. Compare the trade-offs in EHR Browser Overlay Architecture.

FHIR-based interoperability remains the long-term standard for structured device data. For practices that need compliant notes this quarter, overlay deployment removes IT dependency and keeps the attestation workflow inside the clinician's existing chart view.

A compliant 2026 RPM billing workflow follows seven checkpoints

1. Confirm the established patient relationship and document the qualifying visit date.
2. Write a condition-specific order with ICD-10-CM code, parameter, threshold, and episode goal.
3. Obtain and record consent, including cost-sharing disclosure.
4. Verify FDA device status and log setup and education for 99453.
5. Reconcile transmission days per 30-day period to select 99454, 99445, or no device code.
6. Log treatment management time contemporaneously with at least one interactive communication for 99457, 99458, or 99470.
7. Append G2211 to qualifying follow-up E/M visits when the longitudinal relationship is documented.

Frequently asked questions about CPT 99453 and 99454

Can CPT 99453 be billed more than once per patient?

Only when a new episode of care begins for a clinically distinct reason. Restarting the same monitoring after a lapse does not support a second 99453.

What happens if a patient transmits only 15 days?

Under 2026 rules, bill CPT 99445 for 2 to 15 days instead of 99454, provided the payer recognizes the code. Below 2 days, no device supply code is billable.

Do manually entered readings count toward 99454?

No. Data must be transmitted digitally and automatically from the device. Self-reported values do not count toward the day threshold.

Can RPM and CCM be billed in the same month?

Yes, RPM and CCM may be billed concurrently, provided the time counted toward each code is distinct and separately documented.

Can two practices bill RPM for one patient?

No. Only one practitioner may bill 99453 and 99454 per patient per 30-day period, regardless of how many devices are used.

Verify 2026 rates and code recognition with your Medicare Administrative Contractor and each commercial payer before you update charge masters. Fee schedule values and payer adoption of 99445 and 99470 vary by locality and contract.