RPM CPT 99453 & 99454 Audit Documentation Checklist

Remote Patient Monitoring CPT 99453 and 99454 Audit Documentation Criteria Checklist (2026)

Merry AI · Thoughtfully curated clinical briefs.

Clinically reviewed by Dr. Marcus Vance, MD (Medical Informatics Advisor) · Coding review by Kaif R. (Clinical Informatics Specialist) · Sources: CY 2026 CMS PFS, NCCI Policy Manual.

CPT 99453 and 99454 survive audit only when the chart proves six elements. These are an established patient relationship, documented consent, a qualifying FDA-defined medical device, automatic digital transmission of physiologic data, the required number of data days within a 30-day period, and a single billing practitioner for that period. If any element is missing, the claim is exposed to recoupment, regardless of the clinical value of the monitoring.

This playbook gives Practice Administrators and CMOs a line-by-line documentation checklist, a comparison table of thresholds and audit defenses, and a staffing cost model. It reflects the CY 2026 Medicare Physician Fee Schedule (PFS), which added CPT 99445 for 2 to 15 days of device data and CPT 99470 for the first 10 minutes of treatment management. Always confirm local coverage details with your Medicare Administrative Contractor (MAC).

CPT 99453 pays once per episode for setup and patient education

CPT 99453 covers the initial setup of the monitoring device and the patient education needed to use it. It is reportable once per episode of care, not once per device and not once per month. An episode of care begins when RPM services start and ends when the targeted treatment goals are attained.

The setup must be documented as an actual encounter. It is not a billing event the vendor triggers when a device ships. Clinical staff (auxiliary personnel under general supervision) may perform the education, but the billing practitioner remains accountable for the record.

Under the CY 2026 framework, 99453 should be reported only after the monitoring meets the minimum day threshold of the device supply code that pairs with it. That pairing is CPT 99445 for 2 to 15 days or CPT 99454 for 16 or more days. If a patient never transmits qualifying data, the setup code should not be billed.

CPT 99453 documentation checklist

• Date and duration of setup: when the device was issued and when education occurred.
• Staff member performing education: name and credential, plus the supervising billing practitioner.
• Device identification: type, manufacturer, model, and serial or unique device identifier.
• Education content delivered: how to take readings, transmission confirmation, troubleshooting, and escalation instructions.
• Teach-back or return demonstration: evidence that the patient can operate the device independently.
• Episode start date: recorded explicitly so a duplicate 99453 cannot be generated later.

CPT 99454 requires 16 days of automatically transmitted physiologic data

CPT 99454 reimburses the device supply with daily recordings or programmed alert transmission each 30 days. It requires at least 16 days of data within the 30-day period. For patients with 2 to 15 days of data, the CY 2026 PFS recognizes CPT 99445 instead. Practices must never round partial months up to 99454.

The device must meet the FDA definition of a medical device under section 201(h) of the Federal Food, Drug, and Cosmetic Act. The data must be physiologic, such as blood pressure, weight, pulse oximetry, or glucose. It must also be digitally uploaded. Values a patient types into a portal, reads aloud by phone, or writes in a paper log do not count toward billable days.

Only one practitioner may bill device supply per patient per 30-day period, even when the patient uses multiple devices. CMS also prohibits billing RPM and Remote Therapeutic Monitoring (RTM) for the same patient during the same period. RPM may be billed alongside Chronic Care Management when time and services are not counted twice.

CPT 99454 documentation checklist

• Transmission log with timestamps: each qualifying day is shown individually, not as a monthly summary.
• 30-day period boundaries: start and end dates match the claim date of service.
• Day count reconciliation: 16 or more days support 99454, and 2 to 15 days support 99445.
• FDA device attestation: 510(k), De Novo, or other device classification on file.
• Automatic upload confirmation: vendor documentation that readings transmit without manual entry.
• Single-biller verification: a note that no other practitioner bills RPM this period.

Audit trigger: device supply billed without day-level transmission evidence in the chart.

Medical necessity must link RPM to a documented chronic or acute condition

Medicare covers RPM for both chronic and acute conditions, but the ordering note must state why physiologic monitoring will change management. A diagnosis such as I10 (ICD-10-CM) essential hypertension is a starting point, not a justification. The note should record the clinical question RPM answers, such as titration of an antihypertensive regimen against home readings.

An established patient relationship is required. CMS reinstated this requirement after the COVID-19 public health emergency. The ordering practitioner should have a documented prior evaluation, either in person or through a qualifying telehealth visit, before RPM begins.

Consent may be obtained at the time of service and by auxiliary staff. It must still appear in the record. The consent note should explain cost sharing, confirm that only one practitioner can bill RPM, and record whether the patient agreed verbally or in writing.

Comparison table: RPM clinical indicators, thresholds, and audit defenses

Federal oversight targets RPM claims missing the full service set

The HHS Office of Inspector General (OIG) reported in 2024 that a large share of Medicare RPM enrollees did not receive all components of the service: education and setup, device supply, and treatment management. OIG recommended stronger safeguards. MACs and Recovery Audit Contractors use these findings to select claims for review.

The highest-risk pattern is device supply billed month after month with no corresponding treatment management (CPT 99470, 99457, or 99458) or clinical action. Auditors read this as a device rental program, not a clinical service. Every billing period should show that a clinician reviewed the data and either acted on it or documented why no change was needed.

State law adds a second compliance layer when RPM data or AI tools influence clinical decisions. Review the State AI Scribe Rules & Statutory Compliance Hub for consent and human-review requirements. These include California SB 1120, which requires that licensed clinicians, not algorithms, make medical necessity determinations in utilization review.

Compliance rule: every billed 30-day period needs a documented clinician review.

Ambient documentation cuts RPM audit labor to 1.3% of MA cost

RPM documentation is labor-intensive because each patient generates enrollment, consent, education, and monthly review notes. A fully loaded medical assistant costs approximately $48,000 per year. Practices often assign a large share of that role to RPM paperwork and transmission reconciliation.

Merry AI Pro costs $648 per year ($54 per month, billed annually). That is about 1.3% of the $48,000 fully loaded MA denominator. Merry AI captures the 99453 education conversation, consent language, and interactive communication with the patient during the encounter. It then produces structured note sections that map to the checklist above.

Deployment does not require an EHR integration project. The EHR Browser Overlay Architecture places generated documentation directly into existing chart fields. This keeps the audit trail inside the legal medical record rather than in a separate vendor system.

G2211 capture adds $15,600+ annually for longitudinal RPM patients

RPM patients are, by definition, under ongoing management of a serious or complex condition. That makes many of their office visits candidates for HCPCS add-on code G2211. When a clinician consistently documents the longitudinal relationship, a single full-time clinician can recover $15,600+ in annual revenue. This assumes roughly 1,000 qualifying visits per year at the approximate national rate.

G2211 and RPM are separate services with separate documentation. The visit note must stand on its own and show that the practitioner is the continuing focal point for the condition, independent of any device data. The CPT G2211 Complexity Capture Architecture details the phrasing auditors expect, including modifier 25 limitations.

Monthly pre-bill audit should verify six items before claim release

1. Confirm the established relationship: check that a prior qualifying visit is on file.
2. Confirm consent is documented: timestamped, with cost-sharing disclosure.
3. Reconcile the transmission day count: assign 99445 or 99454 from the actual log.
4. Block duplicate setup codes: allow 99453 only once per documented episode.
5. Verify the clinician data review: require a note showing action or rationale for no change.
6. Verify single-biller and RTM exclusion: confirm no concurrent RPM or RTM claims.

Practices that run this six-point check before claim submission turn RPM from an audit liability into a defensible, recurring clinical service. Assign ownership to one billing lead and keep a signed monthly attestation. When an Additional Documentation Request arrives, the evidence package is then already assembled.

Frequently asked questions about RPM CPT 99453 and 99454 audit documentation

Can CPT 99453 be billed more than once per patient?

No. CPT 99453 is reportable once per episode of care, regardless of how many devices are issued. A new episode begins only when a prior episode ended because treatment goals were met and a new clinical indication justifies restarting monitoring. Document the episode start and stop dates explicitly.

How many days of data are required for CPT 99454?

CPT 99454 requires at least 16 days of automatically transmitted physiologic data within a 30-day period. For 2026, CMS recognizes CPT 99445 for 2 to 15 days of data. Audit files must show transmission timestamps for each qualifying day, not a monthly summary statement or vendor dashboard screenshot.

Does patient self-reported data qualify for CPT 99454?

No. CMS requires data to be digitally and automatically uploaded from an FDA-defined medical device. Readings a patient types into a portal, reads over the phone, or writes in a log do not qualify. Self-reported values may support clinical decisions but cannot count toward billable days.

Can two practices bill CPT 99454 for the same patient?

No. Medicare pays only one practitioner for RPM device supply per patient per 30-day period, even if multiple devices are used. Practices should confirm at enrollment that no specialist, hospital program, or vendor is already billing RPM, and document that verification in the consent record.

Can RPM codes and CPT G2211 be billed together?

Yes, when separately supported. RPM codes cover device supply and monitoring, while G2211 is an add-on to an office or outpatient E/M visit reflecting longitudinal care of a serious or complex condition. The visit note must independently document the ongoing relationship and the condition being managed.