CPT code 93296 – Remote interrogation of implanted cardiac devices

Key takeaways

CPT Code 93296 is the technical component code for remote interrogation of pacemaker, leadless pacemaker, and implantable defibrillator systems.

It covers remote data acquisition, receipt of transmissions, technician review, technical support, and distribution of results, over a period of up to 90 days.

The physician work is billed separately: 93294 is the professional component for pacemaker systems, and 93295 is the professional component for implantable defibrillator systems.

Modifier 26 does not apply to 93296, because a separate professional component code already exists for each device family.

Medicare pays 93296 once per device per 90-day period and requires general supervision of the technical service by a physician.

CPT Code 93296: Definition and official descriptor

CPT Code 93296 is the technical component code for remote interrogation of implanted cardiac devices, as defined by the American Medical Association’s CPT code set. It pays the entity that runs the monitoring service and collects the transmissions. No physician analysis, review, or report is bundled into it.

The official AMA descriptor for CPT Code 93296 reads as follows, set out here on its own punctuation:

• Interrogation device evaluation(s) (remote), up to 90 days;
• single, dual, or multiple lead pacemaker system, leadless pacemaker system, or implantable defibrillator system,
• remote data acquisition(s), receipt of transmissions and technician review, technical support and distribution of results.

Two details in that descriptor decide whether the claim pays. First, the code covers a monitoring period of up to 90 days, not a single transmission event. Second, every element it names is technical, from acquiring the data through to distributing the results.

Physician work lives in a different code. For a pacemaker or leadless pacemaker system, the professional component is 93294. For an implantable defibrillator system, it is 93295. A device clinic that owns the monitoring platform and employs the reading physician bills two codes, not one.

Which devices does CPT Code 93296 cover?

CPT Code 93296 applies to a defined list of implanted cardiac devices. Stretching it to cover any implanted cardiac monitor is the fastest route to a denial. The monitor codes sit in a separate family, on a shorter period.

Every eligible device must hold FDA clearance for remote monitoring transmission. Manufacturer platforms include Medtronic’s CareLink, Abbott’s Merlin.net, Boston Scientific’s LATITUDE, and Biotronik’s Home Monitoring. Some devices are implanted without the manufacturer’s remote monitoring service ever being activated. There is then no monitoring service to bill, and the 93296 claim is denied.

How 93296 differs from related cardiac device codes

The 93290s family trips up experienced coders because it splits one service into two codes. One code carries the professional component, the other carries the technical component, and 93296 is always the technical one.

93296 is the only technical code in the pacemaker and defibrillator group, so it partners with two different professional codes. Pair it with 93294 for a pacemaker and with 93295 for a defibrillator. Billing 93294 against a defibrillator transmission is a device mismatch, and it is easy to avoid. Confirm the implanted device first, then read the codes and the period off the grid below.

Why modifiers -26 and -TC do not apply

CPT Code 93296 is already a component code, so it does not split any further. The AMA published a separate professional code for each device family, which removes the reason a practice would append a component modifier at all.

Medtronic’s device monitoring procedure code guide states the rule directly. The -26 modifier is not applicable when there is a separate professional component code, as with CPT 93294 and 93295.

The confusion has a traceable source. In-person device evaluation codes such as 93288 and 93289 are configured as global codes. Modifier -26 is appended to those when the evaluation happens in a facility and the physician reports the professional component separately. Remote monitoring works the other way around, because the split is already built into the code set.

Hospital outpatient device clinics split the bill across two claim forms. The hospital reports 93296 on a UB-04 as the facility charge. The reading physician reports 93294 or 93295 on a CMS-1500. Neither claim carries a component modifier.

Documentation requirements for the technical claim

Documentation for remote cardiac device monitoring splits across the same two claims as the codes. The technical record supports 93296. The interpretive note supports 93294 or 93295. A payer auditing the technical claim is looking for proof the monitoring service ran, not for a physician’s opinion.

• Device identification: device type, manufacturer, model number, and serial number recorded against the patient
• Transmission record: the date each transmission was received and the 90-day monitoring period it falls inside
• Technician review: evidence that a trained technician screened the transmission and triaged the data
• Data elements captured: battery voltage and longevity estimate, lead impedance values, sensing and pacing thresholds, therapy delivery history, arrhythmia episode log, and stored electrograms
• Technical support and distribution: the record showing results were prepared and sent on to the reading physician
• Supervision record: the name of the physician supervising the technical service for that monitoring period

The professional claim needs a note of its own. The reading physician records the interpretation, the clinical decision, and any programming recommendation, including “no change indicated” where that is the finding. That note supports 93294 or 93295. It does not support 93296.

Documentation checklists built into the billing system stop an incomplete note reaching the payer. Thin documentation remains one of the top denial drivers for this code family. A practice that wants cleaner claims management starts by fixing the note, not the claim form.

Medicare coverage criteria for CPT Code 93296

Medicare coverage for remote defibrillator surveillance is set out in CMS Article A53018, Surveillance of Implantable or Wearable Cardioverter Defibrillators. It confirms that 93295 and 93296 are 90-day services, reportable once per period however many interrogations are performed. Coverage is not automatic.

• Eligible beneficiaries: Medicare Part B patients with a device named in the descriptor, meaning a pacemaker, leadless pacemaker, or implantable defibrillator system
• Device clearance: the implanted model must be FDA-cleared for remote transmission, which does not hold for every model from a covered manufacturer
• Active enrollment: the patient must be enrolled in a manufacturer remote monitoring service such as CareLink, LATITUDE, Merlin.net, or Home Monitoring
• No same-day face-to-face pairing: A53018 states that a provider may not bill a remote service and a face-to-face service on the same day
• Not billable at implant: these services are not reported when a device is being implanted or replaced
• Commercial payer variation: private insurers set their own criteria, frequency limits, and prior authorization rules, so never apply Medicare policy to a commercial claim unverified

MAC jurisdiction decides which version of the policy applies to your claims. Novitas Solutions, CGS Administrators, Palmetto GBA, NGS, and WPS each administer their own region. Confirm your MAC assignment and check for jurisdiction-specific articles before submitting.

Strong insurance eligibility verification workflows catch inactive coverage and unenrolled patients before a claim leaves the practice. That single check prevents a meaningful share of 93296 denials at source.

Reimbursement rates and the RVU profile

Medicare payment for CPT Code 93296 comes from the Medicare Physician Fee Schedule (MPFS) and is updated each January 1. Rates vary by geographic practice cost index, so the national amount is a starting point rather than a guaranteed local payment.

Because 93296 carries no physician work, its payment is built from practice expense and malpractice relative value units. Those cover the monitoring equipment, the technician’s time, and the office overhead behind the service. The work RVUs sit on the professional code instead.

CMS updates the conversion factor annually, so quoting a dollar rate in a reference article risks misstating the current year. Use the FastRVU RVU lookup tool or the official CMS MPFS search to retrieve the current national rate for your locality. The RVU components stay stable between major descriptor revisions, while the dollar rate moves each year.

Billing frequency rules and the 90-day monitoring period

CPT Code 93296 is billable once per 90-day period per device under Medicare. The window opens with the first day of the monitoring period, not with the first transmission or the date a physician read the data.

• One billable event per 90 days: however many transmissions arrive inside the window, only one 93296 is payable per device per period
• Device replacement: a replacement or upgrade opens a fresh 90-day period for the new device, and each device is tracked independently
• No global period: 93296 carries a global period indicator of “XXX” under the MPFS, meaning the concept does not apply. It is not a surgical code
• Same-day face-to-face services: A53018 states that a provider may not bill a remote service and a face-to-face service on the same day
• NCCI edits: edits are refreshed quarterly, so verify the current status of any pair you intend to submit together
• Commercial payer variation: some payers apply 30-day or calendar-quarter limits that differ from the Medicare rule, so check each policy separately

Tracking 90-day windows across a large device panel by hand is error-prone. A practice that connects its billing calendar to the monitoring platform catches duplicate periods before the claim is built. That removes most frequency-violation denials.

Place of service coding on a 93296 claim

Place of service on a 93296 claim follows the technical service rather than the reading physician. The question to answer is where the monitoring equipment and the technicians sit. The professional claim answers a different question, and mixing the two produces avoidable denials.

• POS 11 (Office): the practice owns the monitoring platform and its technicians screen transmissions at an office workstation. This is the common physician-office arrangement
• POS 22 (On campus outpatient hospital): a hospital device clinic runs the monitoring service and reports the technical charge on its own facility claim. The reading physician bills 93294 or 93295 separately
• POS 21 (Inpatient hospital): monitoring performed during an admission is generally bundled into the inpatient payment. Do not submit 93296 with POS 21 without documentation supporting a separate service
• POS 02 and POS 10 (telehealth): not applicable here, because Medicare treats remote interrogation as a diagnostic test rather than a telehealth encounter

A frequent error is a hospital-based arrangement billed as though it were an office service. Where the hospital owns the monitoring platform, the technical charge belongs on the hospital’s claim. The physician practice then bills only the professional code, and facility versus non-facility pricing follows from that split.

Supervision rules for the technical component

Medicare treats cardiac device monitoring as a diagnostic service, which brings physician supervision requirements with it. Those requirements attach to the technical component of the electronic analysis, so they attach to 93296.

General supervision, not direct supervision

Remote interrogation services require general supervision. The service is furnished under the physician’s overall direction and control, but the physician does not need to be present while it is performed. Training the technician and maintaining the equipment stay the physician’s responsibility.

Direct supervision is the stricter standard, and it applies to in-person cardiac device evaluations performed at an office place of service. Applying it to remote monitoring overstates what Medicare asks for. It also holds up claims that were payable all along.

Who can supervise the service?

Medicare’s diagnostic testing rules state that the supervisor must be a physician. A nurse practitioner or physician assistant cannot supervise the technical service, except in states where the law and scope of practice permit it. Confirm your state’s position before assigning supervision to an NPP.

Incident-to and shared-visit questions belong to the professional claim instead of this one. Where a technician screens a transmission and a physician then interprets it, that interpretation is what 93294 or 93295 pays for. The physician must perform the review personally and sign the note.

Practices managing supervision across several providers benefit from a workflow that flags a note before its claim is released. The device, the period, the place of service, and the supervising physician all need confirming up front.

Common reasons CPT Code 93296 claims are denied

Most CPT Code 93296 denials trace back to a short list of causes. Each one has a root cause and a practical fix.

• Component modifier appended: a claim carrying 93296-26 or 93296-TC. Fix: strip the modifier, and add 93294 or 93295 where a physician also read the transmission
• Frequency exceeded: a second 93296 inside the same 90-day window for the same device. Fix: keep a device-level billing calendar and run a pre-submission frequency check
• Professional code mismatched to the device: 93294 billed against a defibrillator transmission, or 93295 against a pacemaker. Fix: confirm the implanted device before selecting the professional code
• Wrong code family: 93296 billed for a loop recorder or an implantable cardiovascular monitor. Fix: route those to 93298 and 93297, which run on 30-day periods
• Wrong place of service: an office POS on a claim for monitoring that the hospital owns and staffs. Fix: map the platform’s owner to the correct claim form and place of service
• Missing technical documentation: the chart shows transmissions arrived but records no technician review or distribution of results. Fix: the two-template approach described above
• Device not enrolled: the implanted model is not active on a manufacturer remote monitoring platform. Fix: verify enrollment at implant and flag unenrolled patients in the scheduling system
• Same-day face-to-face service: a remote service and an in-person service billed on the same date, which A53018 prohibits. Fix: check the device clinic calendar before the claim is released

Practice management software like Pabau integrates with Claim.MD, our US clearinghouse partner, to run eligibility verification and claim scrubbing before submission. Several of the triggers above surface while the claim is still being built rather than weeks later as a rejection.

Billing staff can map denial reason codes against the triggers above. That mapping becomes an appeals library for this code family. The AAPC Codify CPT lookup carries the parenthetical notes and cross-code guidance for the 93290s family.

How Pabau supports cardiac device monitoring billing

A device clinic billing 93296 has to track two separate facts at once. It needs to know which devices sit inside an open 90-day window, and whether each technical claim has a matching professional claim. That tracking usually lives in a spreadsheet parked beside the monitoring platform, and the spreadsheet is where frequency-exceeded denials begin.

Pabau keeps the billing record in the same system as the patient record. Device details, transmission dates, and the supervising physician sit on the patient’s chart, so the claim is built from what the practice already documented. Staff never re-key device details from a monitoring portal into a billing screen.

The Claim.MD connection then runs eligibility checks and claim scrubbing before the claim is released. Errors that would otherwise return weeks later as a denial surface while the claim is still on screen. That shortens the time from transmission to payment, and it keeps appeal work off the billing team’s desk.

Reduce 93296 denials before they happen

Pabau connects to Claim.MD to scrub cardiac device monitoring claims as they are built. Catch frequency violations, component modifier errors, and missing documentation before the claim reaches the payer.

Book a demo

Conclusion

CPT Code 93296 pays for the monitoring service, not for the medicine. Once a billing team holds on to that distinction, most of the code’s denial profile dissolves. The modifier questions stop, pairing with 93294 or 93295 becomes routine, and the 90-day calendar is all that is left to manage.

The trade-off worth remembering is that two correct claims are still two claims. A device clinic that reports 93296 and never reports the matching professional code leaves the physician’s work unpaid. Audit a quarter of submitted lines and check that both halves went out for every monitoring period.

Pabau’s claims management software, connected to the Claim.MD clearinghouse, runs eligibility and scrubbing checks before submission. Book a demo to see how a cardiac device clinic runs that workflow from transmission through to payment.

Continue your research

Need to understand the full billing workflow before the claim is built? What is medical billing covers the end-to-end process from service delivery to payment posting.

Handling electronic claims and remittance for cardiac services? Electronic remittance advice explains how 835 ERA files map denial reason codes back to specific claim lines.

Want to reduce the administrative burden of device clinic billing? Best medical billing software in the US reviews the platforms that handle high-volume specialty billing workflows.

Managing revenue across a multi-provider cardiac practice? Superbill documentation explains how superbills capture CPT codes, modifiers, and diagnosis codes before submission.

Frequently asked questions