Cardiac Telemetry Monitoring: CPT Coding & Compliance

Last updated: July 14, 2026

Key Takeaways for 2026 Cardiac Telemetry Billing

• CPT codes 93228 and 93229 cover MCOT professional and technical components. These codes must match the actual device type and monitoring duration to prevent denials.
• Accurate documentation of clinical indication, symptom frequency, prior monitoring results, and specific ICD-10 codes is mandatory for compliant MCOT and remote device billing.
• Remote interrogation codes (93294–93298) have strict frequency limits, with pacemakers billed quarterly, ICDs billed quarterly, and ILRs subject to a 10-day minimum monitoring period.
• Common audit triggers include unspecified diagnoses like R07.9, mismatched CPT–ICD-10 pairings, missing interpretation notes, and overlapping monitoring periods.
• Contact Rhythm360 to automate documentation capture and support 2026 CPT compliance across all cardiac telemetry claims.

2026 Cardiac Telemetry CPT Code Reference Table

The following table consolidates the primary cardiac telemetry CPT codes for 2026. Review device type, billing duration, and payer notes here, then confirm that your selected code matches both the device and the actual monitoring period before you submit a claim.

What Is the CPT Code for Telemetry Monitoring?

The primary ambulatory cardiac telemetry codes are 93228 for the professional component and 93229 for the technical component. The correct code depends on the device category, monitoring duration, and the entity performing each service component. The following checklist reflects 2026 compliance requirements and walks you through the selection process step by step.

2026 Compliance Checklist — Selecting the Correct Telemetry Code

1. Confirm the device type: MCOT (93228/93229), extended Holter ≤7 days (93241–93244), or extended Holter 7–15 days (93245–93248). Device type determines the correct code family.
2. After you identify the code family, verify that the actual wear duration matches that family’s duration range. Billing a 30-day monitoring code for a 3-day recording is a compliance violation regardless of device type.
3. With code and duration aligned, document the clinical indication and symptom frequency in the ordering note so the record clearly supports medical necessity.
4. Next, confirm that the billing entity meets supervision and contractual requirements for the technical component, because eligibility to bill 93229 depends on these arrangements.
5. Finally, pair each claim with a specific ICD-10 code that supports the documented indication, and avoid unspecified diagnoses such as R07.9, which trigger audit review.

The following red-flag warnings illustrate common failures to follow the checklist above and signal immediate audit risk when they appear in a claim.

Red-Flag Warnings

• Billing 93229 without a corresponding 93228 interpretation note on file.
• Selecting a code based on the ordered duration instead of the actual recorded duration.
• Using a single unspecified chest pain diagnosis (R07.9) to support MCOT claims, which ranks among the top triggers for RAC reviews.

Payer-Specific Example: Medicare requires that the monitoring code match the device actually used. A claim for 93229 supported only by documentation of a standard Holter recorder will be denied on audit, even when the monitoring duration appears correct.

Can CPT 93295 and 93296 Be Billed Together?

CPT 93295, which covers ICD professional interpretation, and 93296, which covers the remote interrogation technical component, function as complementary codes rather than mutually exclusive options. In addition, 93294 and 93295 have no NCCI mutually exclusive edits and may be billed together when clinically appropriate. To bill these codes correctly and avoid frequency and documentation errors that cause denials, verify each requirement below before you submit a claim.

2026 Compliance Checklist — Billing 93295 with 93296

1. Confirm that the implanted device is an ICD or CRT-D, not a pacemaker, because pacemakers use 93294 for the professional component.
2. Verify that the monitoring period meets the minimum 30-day monitoring requirement before you submit 93295.
3. Confirm that billing frequency does not exceed a quarterly schedule. ICDs are billed quarterly, and applying a monthly cycle produces denials for excessive frequency.
4. Ensure that the entity billing 93296 has a qualifying contractual arrangement with the monitoring service and meets CMS incident-to and supervision requirements.
5. Document device type, manufacturer, monitoring period dates, programmed parameters, and actionable findings in the interpretation note so the record clearly supports 93295.

The following red-flag warnings highlight frequent missteps that violate the checklist above and invite payer scrutiny.

Red-Flag Warnings

• Billing both 93294 and 93295 for the same patient in the same period when the clinical record does not justify both codes.
• Submitting 93296 without a qualifying contractual arrangement for the technical component.
• Omitting the physician interpretation note required to support 93295 reimbursement.

Payer-Specific Example: 2026 CPT guidelines mandate explicit documentation of physician interpretation and report when 93296 is paired with I48.91 (Unspecified atrial fibrillation), or auditors may recoup payment.

What Documentation Is Required for MCOT 93228/93229?

MCOT claims require a defined set of documentation elements in the medical record before submission. A single missing element can justify denial or recoupment during audit.

2026 Compliance Checklist — MCOT Documentation

1. Record the clinical indication for MCOT in the ordering note so medical necessity is clear.
2. Document the timing and duration of the patient’s chief complaint, and specify symptom frequency, such as symptoms occurring less frequently than every 48 hours.
3. Include results of any prior cardiac monitoring, such as Holter monitoring, to support the decision to escalate to MCOT.
4. State the rationale for suspecting arrhythmia and describe how results may influence the treatment plan.
5. Confirm that the actual monitoring duration is recorded and matches the billed code period.
6. Assign up to four specific ICD-10 diagnosis codes and avoid unspecified codes that weaken the medical necessity argument.
7. Retain the physician interpretation note that addresses findings and any clinical actions taken.

Red-Flag Warnings

• Ordering notes that state only “rule out arrhythmia” without symptom frequency or prior monitoring results.
• EHR copy-paste errors that carry forward incorrect procedure-diagnosis pairings from prior visits.
• Interpretation notes that list findings but do not connect those findings to a clinical action or a documented decision to maintain the current plan.

Payer-Specific Example: Payer policies may mandate additional evidence beyond minimum documentation elements. Each payer’s specific policy must be verified before submission, because requirements often extend beyond the baseline CMS standard.

Inpatient vs. Ambulatory Telemetry Billing Differences

The billing pathway for cardiac telemetry monitoring changes significantly based on the care setting. Ambulatory codes such as 93228, 93229, and 93241–93248 apply to outpatient and wearable monitoring, while inpatient telemetry is bundled into facility DRG payments and is not separately billable under these CPT codes.

2026 Compliance Checklist — Setting-Specific Billing

1. Confirm the patient’s care setting before you select a code family, because inpatient telemetry is not separately reimbursable under 93228 or 93229.
2. For ambulatory MCOT, verify that the patient was not simultaneously admitted as an inpatient during the monitoring period, since an admission affects claim eligibility.
3. For remote device interrogation codes 93294–93298, confirm that these codes apply regardless of setting when the interrogation occurs remotely and meets monitoring period requirements.
4. Document the place of service accurately on the claim form, because mismatches between place of service and CPT code trigger automated edits.
5. Verify that overlapping service periods do not exist, since two monitoring codes covering the same calendar dates for the same patient will be denied.

Red-Flag Warnings

• Submitting 93229 for a monitoring period that overlaps with an inpatient admission.
• Billing ambulatory telemetry codes for monitoring initiated during an observation stay without confirming payer policy on observation-status billing.
• Allowing overlapping monitoring periods for the same patient under different code families, even though the selected code must match the actual device used and monitoring duration.

Payer-Specific Example: Medicare does not separately reimburse continuous telemetry monitoring provided during an inpatient stay under 93228 or 93229. Those services fall within the facility’s DRG payment, and separate billing creates a compliance violation.

Common Telemetry Coding Errors That Trigger Audits

Recovery Audit Contractor (RAC) reviews of cardiac monitoring claims repeatedly identify the same documentation and coding failures. Recognizing these patterns allows your team to correct them before claims reach payers.

2026 Compliance Checklist — Audit-Risk Reduction

1. Pair every cardiac monitoring CPT code with a specific, clinically supported ICD-10 diagnosis, because incorrect CPT–ICD-10 pairing ranks among the top triggers for RAC reviews.
2. Audit EHR templates for copy-paste errors that carry forward mismatched procedure-diagnosis combinations from prior visits.
3. Confirm billing frequency against device type, using the pacemaker and ILR rules described in the reference table, and apply the same discipline to ICDs billed quarterly.
4. Ensure that 2026 RPM documentation includes data transmission frequency, device classification, reporting intervals, and a separate interpretation and report when billed independently.
5. Verify that 93297 and 93298 are not applied to pacemakers, ICDs, or loop recorders, because these codes apply specifically to implantable hemodynamic monitors such as CardioMEMS.

The following three errors represent the most frequently observed violations in 2026 RAC audits, ranked by recoupment volume.

Red-Flag Warnings

• Using R07.9 (Chest pain, unspecified) as the primary diagnosis for any remote cardiac monitoring claim, which remains the single most common audit trigger across payers.
• Applying monthly billing cycles to pacemaker or ICD remote monitoring, which produces denials for excessive frequency and often leads to retroactive recoupment of earlier claims billed at the same interval.
• Submitting 93297 or 93298 for a pacemaker or ICD patient, even though these codes do not apply to those device categories and signal a misunderstanding of device-specific code families.

Payer-Specific Example: Using I48.91 (Unspecified atrial fibrillation) with 93296 without a physician interpretation and report results in denial and potential recoupment under 2026 CMS audit protocols.

Decision Workflow for Selecting the Correct 2026 Telemetry Code

Use the following logic as a step-by-step workflow to determine the appropriate code path before claim submission. Move through each question in order until you reach the scenario that matches your patient’s situation, and then follow that path to identify the correct CPT code family and any frequency limits.

• Is the patient admitted inpatient? If yes, telemetry is bundled in the DRG, and you should not bill 93228 or 93229.
• Is the patient ambulatory with a wearable MCOT device? If yes, proceed to 93228 for the professional component and 93229 for the technical component for a 30-day period.
• Is the monitoring duration ≤7 days with a continuous external recorder? If yes, use the 93241–93244 family.
• Is the monitoring duration 7–15 days? If yes, use the 93245–93248 family.
• Does the patient have an implanted pacemaker monitored remotely? If yes, use 93294 for the professional component plus 93296 for the technical component, observing the quarterly limit described earlier.
• Does the patient have an implanted ICD or CRT-D monitored remotely? If yes, use 93295 for the professional component plus 93296 for the technical component on a quarterly schedule, not 93294.
• Does the patient have an ILR or ICM? If yes, use 93297 for the professional component while observing the 10-day minimum and monthly frequency cap, and confirm payer policy on the technical component code, which has historically included G2066 for some payers.
• Do any two monitoring periods overlap for the same patient? If yes, resolve the overlap before submission, because overlapping claims will be denied.

How Centralized Cardiac Data Platforms Support 2026 Compliance

Practices managing patients with devices from multiple manufacturers such as Medtronic, Boston Scientific, Abbott, and Biotronik face a structural documentation problem. Each OEM portal captures data in a proprietary format, and manual reconciliation into a compliant billing record introduces the same errors that trigger audits, including mismatched durations, missing interpretation notes, and copy-paste diagnosis errors.

Eliminating this fragmentation requires a centralized system that normalizes data from all manufacturers into a single, audit-ready record at the point of ingestion. Rhythm360 is a vendor-neutral, HIPAA-compliant platform that ingests and normalizes data from all major device manufacturers into a single dashboard, addressing the documentation gaps described above automatically.

The platform’s AI-powered data ingestion achieves greater than 99.9% transmissibility through redundant data feeds, computer vision, and AI-powered extrapolation, which keeps the documentation record complete even when an OEM server experiences downtime. Practices using Rhythm360 have reduced critical alert response times by up to 80% and increased revenue capture by as much as 300% through optimized CPT code documentation.

Rhythm360 also provides bi-directional EHR integration with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and other major systems. This integration removes manual transcription between the monitoring platform and the billing system, which is the primary source of copy-paste errors that generate audit exposure.

2026 Audit-Risk Documentation Checklist

The following elements are most frequently requested by RAC auditors and Medicare Administrative Contractors (MACs) when they review cardiac telemetry claims. Use this checklist as a pre-submission verification tool, and confirm that every required element appears in the record before you submit a claim, because each missing item represents a potential denial or recoupment risk.

Practices that automate the capture of these elements, rather than relying on manual workflows across fragmented OEM portals, close the documentation gaps that produce denials. Rhythm360’s automated reporting generates audit-ready records that address each of these elements at the point of data ingestion, not retroactively at the point of audit. Practices that follow this approach achieve the revenue and response-time improvements described earlier.

Frequently Asked Questions

What is the difference between CPT 93228 and 93229, and can both be billed by the same practice?

CPT 93228 covers the physician’s professional review and interpretation of MCOT data, while 93229 covers the technical support component, including infrastructure, connection, and recording services. Both codes apply to a 30-day monitoring period. Whether a single practice can bill both depends on its contractual arrangement with any monitoring service and whether it meets CMS incident-to and supervision requirements for the technical component. In many cases, the professional component 93228 is billed by the interpreting physician’s practice, while the technical component 93229 is billed by the monitoring center or a contracted service partner. Practices should confirm their eligibility for each component with their MAC before submitting both on the same claim.

How does Rhythm360 help practices avoid the most common 2026 telemetry billing denials?

The most common denial triggers in 2026 include mismatched CPT–ICD-10 pairings, missing physician interpretation notes, incorrect monitoring durations, and copy-paste errors from EHR templates. Rhythm360 addresses these issues at the source by automatically capturing device type, manufacturer, monitoring period dates, transmission frequency, and clinical findings from all connected OEM data streams into a single, normalized record. Because the platform integrates bi-directionally with major EHR systems including Epic, Cerner, and Athenahealth, documentation flows directly into the billing record without manual transcription, which eliminates the copy-paste errors that generate audit exposure. The result is a complete, audit-ready documentation set for each billable event before the claim is submitted.

What are the 2026 billing frequency rules for remote cardiac device monitoring?

Billing frequency rules vary by device type and are strictly enforced by Medicare and most commercial payers. Pacemakers (CPT 93294) may be billed no more than once every 90 days. ICDs and CRT-D devices billed under CPT 93295 follow a quarterly schedule. Implantable loop recorders and cardiac monitors billed under CPT 93297 require a minimum of 10 days of monitoring and are reported no more than once every 30 days, and each period requires a substantive clinical interpretation note. Applying a monthly billing cycle to pacemakers or ICDs, a common error in high-volume practices, produces denials for excessive frequency and creates audit exposure for prior claims submitted at the same interval.

Can CPT 99091 be used alongside cardiac telemetry monitoring codes?

CPT 99091 covers physician or qualified healthcare professional collection and interpretation of digitally transmitted physiologic data and requires at least 30 minutes per patient per 30-day period. Practices can use 99091 alongside device setup code 99453 and data transmission code 99454 to create an alternative RPM billing pathway for cardiac monitoring data. However, 99091 cannot be billed in the same month as 99457 or 99458 for the same patient, so practices must choose the pathway based on whether the primary activity involves physician data interpretation or interactive clinical staff management. Documentation for 99091 must include the date, duration, and specific description of data reviewed, along with clinical reasoning that connects findings to a care plan action.

What makes a cardiac telemetry monitoring platform “vendor-neutral,” and why does it matter for compliance?

A vendor-neutral platform ingests and normalizes data from devices manufactured by multiple OEMs, such as Medtronic, Boston Scientific, Abbott, and Biotronik, without separate logins to each manufacturer’s proprietary portal. This approach matters for compliance because fragmented data retrieval across multiple portals often produces incomplete documentation. Monitoring period dates may differ between portals, interpretation notes may not link to the correct device record, and transmission frequency data may be missing entirely. A centralized, vendor-neutral system like Rhythm360 captures all required documentation elements from a single interface, ensuring that the record supporting each CPT code claim remains complete and consistent regardless of which manufacturer’s device the patient carries.