CPT Codes 99453 and 99454 Billed Together in 2026

Last updated: June 29, 2026

CPT codes 99453 and 99454 may be billed together during the initial 30-day episode of care when the patient completes at least 16 days of device data transmission. CPT 99453 is reported once per episode for device setup and patient education, while CPT 99454 covers device supply with ongoing transmission. After the first month, CPT codes 99454, 99457, and 99458 (plus new 2026 codes) repeat on a monthly basis.

Key Takeaways for 99453 and 99454

• CPT 99453 covers one-time device setup and patient education, while CPT 99454 covers 30-day device supply and transmission, so both can be billed together in the initial month when requirements are met.
• Medicare requires a minimum of 16 days of data transmission within the 30-day billing period for CPT 99454 to be payable alongside 99453.
• Commercial payers may add rules such as prior authorization or different transmission thresholds, so written coverage determinations should be obtained before enrollment.
• Accurate documentation, including physician orders, patient consent, device setup records, and transmission logs, is essential to prevent denials for both codes.
• Cardiology practices can streamline first-month RPM compliance and reduce denials with a centralized platform; contact Rhythm360 to see how their solution automates billing workflows.

How 99453 and 99454 Work Together in Month One

CPT 99453 and CPT 99454 serve distinct but complementary functions within an RPM episode. Their descriptions, billing frequency, and interdependencies form the basis of compliant first-month revenue capture.

• CPT 99453 — Remote monitoring of a physiologic parameter(s); initial; setup and patient education on use of equipment. Reported once per episode of care, regardless of device type or monitoring duration.
• CPT 99454 — Device(s) supply with daily recording(s) or programmed alert(s) transmission, each 30 days. Requires a minimum of 16 days of data transmission within the 30-day billing period to satisfy CMS physician fee schedule requirements.

CPT 99453 functions as a one-time setup code, and CPT 99454 functions as a recurring supply-and-transmission code, so they overlap naturally in month one. Billing both in the same claim period is permissible and represents the expected pattern for a properly initiated RPM program.

Practices that lack a centralized platform to track transmission days, automate documentation, and flag incomplete months before claim submission often leave this revenue uncaptured or face denials. See how Rhythm360's automated compliance tracking eliminates first-month billing errors for cardiology teams.

2026 Medicare Rules and Requirements for 99453 and 99454

Now that the basic relationship between 99453 and 99454 is clear, the specific Medicare rules for 2026 show when and how these codes can be combined. The table below summarizes the operative 2026 Medicare requirements for each code and their interaction during the initial episode of care, drawn from CMS fee schedule guidance and Telehealth.HHS.gov RPM policy resources.

A physician or other qualified healthcare professional must order RPM services. The ordering clinician does not need to perform setup personally.

Commercial Payer Rules That Affect 99453 and 99454

Medicare sets the floor for RPM billing policy, and commercial payers often add their own requirements. The table below compares key policy dimensions as of 2026.

Revenue-cycle staff should obtain written coverage determinations from each commercial payer before launching RPM enrollment. Payer policies for RPM codes continue to evolve, and a plan that covered both codes together in 2025 may have updated its medical policy for 2026.

Cardiology First-Month Workflow for 99453 and 99454

The sequence below illustrates a compliant first-month RPM episode for a heart failure patient newly enrolled in remote physiological monitoring.

1. Day 1 — Physician order and enrollment: The cardiologist documents a written order for RPM in the EHR. The patient is enrolled and assigned an FDA-cleared weight scale and blood pressure cuff. CPT 99453 is triggered at this point.
2. Days 1–30 — Data transmission: The patient transmits daily physiologic readings. The platform tracks each transmission day automatically. The 16-day threshold must be reached within this window for 99454 to be billable.
3. Day 16 — Threshold confirmed: The platform flags that the 99454 transmission requirement has been satisfied. Revenue-cycle staff receive notification that both 99453 and 99454 are eligible for submission.
4. Day 30 — Claim submission: Both codes are submitted on the same claim with supporting documentation: the physician order, patient education record, and a transmission log confirming at least 16 days.
5. Month 2 onward: Only 99454 recurs. CPT 99453 is not billed again for this patient episode. CPT 99457 (remote physiologic monitoring treatment management, first 20 minutes) may be added when clinical staff time thresholds are met.

For CIED patients, this workflow intersects with device-specific remote monitoring codes such as 93295–93299. A vendor-neutral platform that aggregates data from Medtronic, Boston Scientific, Abbott, and Biotronik into a single dashboard removes the manual transmission-day counting that causes most first-month billing errors.

Documentation Checklist for 99453 and 99454 Claims

Every RPM claim for 99453 and 99454 should include the following documentation, consistent with ACP RPM documentation standards and HHS Telehealth best-practice guides:

• Written physician or NPP order for RPM services, dated before enrollment
• Patient consent for RPM, documented in the medical record
• Record of device setup and patient education (supports 99453)
• FDA device clearance confirmation or device description on file
• Transmission log showing date-stamped readings for each of the 16 or more days (supports 99454)
• Identification of the ordering and billing provider with NPI
• Diagnosis code(s) linking the monitored condition to the RPM order

Common Denial Reasons and Prevention Strategies

Claim denials for 99453 and 99454 cluster around a predictable set of errors. Addressing each proactively reduces rework and protects cash flow, especially when denial patterns repeat across large patient panels.

• Fewer than 16 transmission days: This issue represents the most frequent denial trigger for 99454. Automated day-counting within the monitoring platform, with alerts when a patient falls behind, prevents this entirely.
• 99453 billed more than once per episode: Payers reject duplicate setup codes. Flag 99453 as a one-time code in the billing system at enrollment.
• Missing or undated physician order: The order must precede the service date on the claim. Retroactive orders are not accepted.
• Non-covered device: Commercial payers may deny claims for devices not on their approved list. Verify device eligibility before patient enrollment.
• Incorrect place of service or modifier: RPM services are typically billed under place of service 11 (office) or 02 (telehealth), depending on payer policy. Confirm the correct code per plan.
• Lack of documented patient consent: Several payers treat absent consent documentation as a basis for denial. Consent should be captured and stored in the patient record at enrollment.

Strong documentation practices directly reduce these denial categories. Practices managing high volumes of CIED and HF patients benefit from a platform that surfaces incomplete transmission counts and missing documentation before the billing window closes. Learn how Rhythm360's pre-submission alerts catch documentation gaps before they become denials.

Strategic RPM Planning for Cardiology Programs

Accurate first-month billing of 99453 and 99454 supports compliance and also establishes the financial foundation for a sustainable RPM program. Practices that capture both codes correctly in month one recover setup costs quickly and position 99454 as a recurring monthly revenue stream.

Cardiology practices that manage mixed-device populations face an additional layer of complexity because CIED remote monitoring codes (93295–93299) run on device-specific schedules that do not align with the 30-day RPM calendar. This misalignment forces staff to reconcile two separate billing tracks manually, which increases the risk of missed charges and duplicate submissions.

A vendor-neutral platform solves this problem by normalizing data from all major OEMs, tracking transmission days automatically, and generating audit-ready documentation for both RPM and CIED codes. This approach reduces two parallel workflows to a single, unified process. The operational efficiency gained, including fewer manual steps, fewer denials, and faster claim cycles, compounds over time as the enrolled patient population grows.

Practices that have implemented this model report up to a 300% increase in RPM-related revenue capture and an 80% reduction in critical alert response times, based on internal Rhythm360 customer outcomes. These results highlight both the billing and clinical value of centralized data management. Discover how Rhythm360 delivers measurable ROI for cardiology RPM programs.

FAQ on Billing 99453 and 99454 Together

Can 99453 be billed every month as long as the patient is enrolled in RPM?

No. As noted earlier, 99453 is billed only once per episode for initial setup and education, and it does not recur monthly. After the first billing period, CPT codes 99454, 99457, and 99458 (plus new 2026 codes) repeat on a monthly basis.

What counts as a "transmission day" for the 16-day requirement under CPT 99454?

A transmission day is a calendar day on which the patient's monitoring device successfully transmits physiologic data to the provider's platform. The 16 days do not need to be consecutive, but all 16 must fall within the same 30-day billing period. Practices should use a platform that logs each transmission with a date and time stamp to produce an auditable record for payer review.

Does billing 99453 and 99454 together affect eligibility for 99457 in the same month?

No. CPT 99457 covers the clinical staff time spent on remote physiologic monitoring treatment management, with a minimum of 20 minutes per calendar month, and functions as a separate, additive code. It may be billed in the same month as 99453 and 99454 when the time threshold is met and the service is documented. CPT 99458 may be added for each additional 20-minute increment beyond the first.

Do commercial payers follow the same 16-day rule as Medicare for CPT 99454?

Commercial payer policies on the transmission threshold vary. Some plans require a higher threshold of 20 or more days, and others impose prior authorization requirements that Medicare does not. Revenue-cycle staff should obtain a written coverage determination from each commercial payer and document it in the billing policy file before enrolling patients.

How does RPM billing for 99453 and 99454 interact with CIED remote monitoring codes in cardiology?

CIED remote monitoring is billed under a separate code set (93295–93299) tied to device-specific interrogation schedules rather than the 30-day RPM calendar. A patient with a pacemaker or ICD may be enrolled in both CIED monitoring and RPM simultaneously, but the two billing tracks must be managed independently. Practices should confirm that their monitoring platform and billing system can distinguish between the two service types to avoid duplicate submissions or bundling errors.

Conclusion: Using 99453 and 99454 Together Confidently

CPT codes 99453 and 99454 can be billed together during the first 30 days of an RPM episode when the 16-day transmission threshold is met and documentation is complete. After month one, the recurring codes discussed earlier continue on a monthly schedule.

For cardiology practices that manage CIED and heart failure populations, the main challenge lies in consistent execution across hundreds of patients with devices from multiple manufacturers. A vendor-neutral platform that automates transmission tracking, surfaces incomplete documentation before claim submission, and integrates with existing EHR workflows turns billing compliance into a repeatable process.

Rhythm360 is built for this environment, aggregating data from all major OEM portals into a single, audit-ready dashboard that supports compliant billing for both RPM and CIED monitoring codes.