CPT 93297 Billing Guide: 2026 Rules, Modifiers and Reimbursement

CPT 93297 reports remote interrogation of an implantable cardiovascular physiologic monitor system covering a period of up to 30 days. The service includes analysis of one or more recorded physiologic cardiovascular data elements from all internal and external sensors, along with clinical review and a report by a physician or other qualified health care professional.

That definition does the work. You don’t pick this code because a patient has an implanted cardiac device, and you don’t pick it because data arrived remotely or because the patient has heart failure. Those facts describe the patient, not the service.

93297 at a Glance

Field	Answer
Service	Remote interrogation device evaluation
System	Implantable cardiovascular physiologic monitor
Data	Physiologic cardiovascular data
Provider work	Analysis, review, and report
Reporting period	Up to 30 days
Reporting limits	Once per 30 days, and not reported when the monitoring period is under 10 days
Billing structure	Global, professional, or technical, based on who performed each component

Key Takeaways

• Code selection starts with the implanted monitoring system and the data type it records, not with the diagnosis.
• The subcutaneous cardiac rhythm monitor family is a separate service, not the technical half of this one.
• G2066 was deleted effective January 1, 2024, so it isn’t a current code on 2026 claims.
• The right modifier depends on who performed each component, not on where the work happened.

If you came here asking what CPT code 93297 is used for, that’s the short version. Everything below builds on it: code selection, modifiers 26 and TC, documentation, 2026 payment, and the denials that show up when one of those slips. This guide comes from the billing team at One O Seven RCM.

What Does CPT 93297 Report?

Four phrases in the descriptor carry the whole code. Miss one and you’re guessing. Break CPT code 93297 into its parts and you can usually tell within a minute whether a service qualifies or belongs to a different family entirely.

The 93297 CPT code description splits into four elements, and each one maps to something your documentation has to prove.

93297 descriptor element	What it means for billing
Remote	The evaluation happens without an in-person interrogation
Implantable system	The record must identify the specific implanted monitoring system
Physiologic data	The data type recorded has to match the code you pick
Analysis and report	The record must show provider review, not just data receipt

The Implantable Monitoring System

Start with the implanted system. Your record needs to name an implantable cardiovascular physiologic monitor system, not a category. Phrases like “implanted cardiac device,” “heart monitor,” “remote cardiac device,” and “cardiac telemetry” each span several code families, so none of them establish this code on their own.

Remote device interrogation is one branch of a much larger cardiac device and cardiology coding family. If your team codes across that whole range, our cardiology CPT code guide maps it out.

The Physiologic Data Being Reviewed

Data type drives the code. What counts here is one or more recorded physiologic cardiovascular data elements collected through internal sensors and external sensors. Rhythm-only recordings, pacemaker battery and lead readings, external ECG tracings, and general remote monitoring data all sit somewhere else.

One exception matters. CPT sends physiologic cardiovascular data derived from an implantable defibrillator to this code, so the device housing the sensor doesn’t settle the question by itself. The code comparison further down handles that split in full.

The Physician or QHP Work

Three things have to happen: clinical analysis, review, and a signed report by a physician or other qualified health care professional (QHP). Opening a portal isn’t the service. Acknowledging an alert isn’t either.

Your billing record has to show that somebody evaluated the data and reached a conclusion. If the note says a transmission was received and stops there, no professional service has been documented.

What “Up to 30 Days” Means

“Up to 30 days” describes the monitoring period the service covers. It isn’t a submission instruction. And it isn’t a promise that every payer treats the claim date the same way.

CPT does put limits around that period, including a minimum length and a cap on how often the code can be reported. Frequency, date of service, and overlapping cycles get their own section later.

The official descriptor and its instructions live in the licensed current CPT edition, and that edition controls. The AMA CPT coding resources page is where to confirm the current language.

What CPT 93297 Covers and What It Does Not Cover

Boundaries cause more denials than definitions do. Most miscoding on this service isn’t a typo or a transposed digit. It’s a correct-looking claim built from the wrong starting fact.

Work Included in the Service

• Remote evaluation of the qualifying implanted system
• Analysis of recorded physiologic cardiovascular data
• Review of information from internal and external sensors
• Clinical assessment by the physician or QHP
• A completed, signed report
• Technical work, when one entity legitimately bills the global service

That last item has conditions attached. Who actually performed each component decides it, and that question gets worked out in the modifier section.

When Remote Cardiac Monitoring Isn’t This Code

Don’t choose this code only because:

• A device is implanted
• Data arrived remotely
• A cardiologist reviewed the information
• The patient has heart failure
• A monitoring platform generated a report

Every one of those can be true while the correct code sits somewhere else. Code selection depends on the system, the data, the service performed, and who performed each component.

93297 does not automatically apply to:Implantable loop recordersPacemakersICD systemsExternal ECG monitorsGeneral remote patient monitoringWireless pulmonary artery pressure monitoringEach of these has its own code family, reporting period, and billing structure.

ICD systems carry one wrinkle worth knowing. CPT routes physiologic cardiovascular data derived from a defibrillator to this code, while rhythm and device function data from the same defibrillator belongs to the ICD family.

Common online error: 93298 isn’t the technical half of this service. The two codes describe different implanted monitoring systems and different data categories, and each carries its own component structure. Plenty of ranking pages get this backward, and a few get it backward in both directions.

Which Monitoring Systems and Data Qualify for CPT Code 93297?

How do you know whether 93297 applies?Work through five checks in order. Identify the implanted system from the implant record, not from a portal nickname. Pin down the data type that system actually records. Confirm the evaluation happened remotely. Verify that a provider analyzed the data and produced a report. Last, establish who performed the professional work and who performed the technical work. Skip a step and you’ll usually land in the wrong code family.

Step 1: Start With the Implanted System

Pull six things before anyone touches a charge screen: device name, manufacturer, model, implant record, monitoring-system category, and clinical purpose. A shortened device name in a portal or on a schedule isn’t enough to code from.

Here’s what that looks like in practice. A biller opens a note that reads “remote cardiac monitor reviewed,” and that’s the whole entry. Nothing in that phrase separates a physiologic monitor from a rhythm monitor, a pacemaker, an ICD, a pressure sensor, or a general remote monitoring device. Send it back.

Step 2: Identify the Data Being Evaluated

Five questions settle the code family:

• Is the system collecting physiologic cardiovascular data?
• Is it collecting heart-rhythm data only?
• Is it reporting pacemaker or defibrillator device function?
• Is it measuring wireless pulmonary artery pressure?
• Is the data coming from a general connected remote monitoring device?

Whichever answer comes back yes points you to a different code family. One question, one fork in the road.

Step 3: Confirm the Work Performed

Check that the record supports data receipt, analysis, clinical review, a clinical report, and real provider involvement. You’re not auditing the documentation yet. You’re confirming a billable service happened at all before the code goes on the claim.

Step 4: Confirm Who Owns Each Component

Ask who receives and organizes the data, who provides technical support, who reviews the data clinically, who signs the report, and which entity submits each piece of the claim. Don’t assign a component modifier yet. Establish the facts first.

Device type, component ownership, and cardiology-specific code families have to be reviewed together, because getting one right and the other two wrong still produces a bad claim. Our cardiology medical billing page covers how those pieces connect across a cardiology workflow.

Decision flow, in order: identify the system, identify the data, confirm the remote service, confirm the analysis and report, confirm component ownership.

CPT 93297 vs 93298, 93264, 93290, 93294, 93295, 93296 and 99454

CPT 93297 and 93298 describe different implanted systems. Physiologic cardiovascular data from an implantable cardiovascular physiologic monitor belongs to 93297. Heart-rhythm data from a subcutaneous cardiac rhythm monitor maps to 93298. CPT code 93296 sits in the pacemaker and ICD family, and 99454 belongs to general remote patient monitoring.

Cardiac Monitoring Code Comparison

Every descriptor and reporting rule below traces to the current licensed CPT edition, and that edition controls if anything here reads differently in your book.

Code	System or data	Service type	Reporting period	Key distinction
93297	Implantable cardiovascular physiologic monitor, physiologic cardiovascular data	Remote interrogation	Up to 30 days, once per 30 days	Not reported when the monitoring period runs under 10 days
93298	Subcutaneous cardiac rhythm monitor, heart-rhythm data	Remote interrogation	Up to 30 days	A separate service, not the technical half of the physiologic monitor code
93264	Wireless pulmonary artery pressure sensor	Remote monitoring	Up to 30 days, at least weekly downloads	Not reported when the monitoring period runs under 30 days
93290	Implantable cardiovascular physiologic monitor	In-person interrogation	Per patient encounter	The in-person counterpart in the same device family
93294	Pacemaker or leadless pacemaker system	Remote professional review and report	Up to 90 days	Pacemaker family
93295	Implantable defibrillator system	Remote professional review and report	Up to 90 days	ICD family
93296	Pacemaker or ICD remote data acquisition and technical work	Remote technical service	Up to 90 days	Pairs with the applicable pacemaker or ICD professional service
99454	General remote monitoring device supply and data transmission	General RPM	16 to 30 days in a 30-day period	Not a substitute for implantable cardiac interrogation

Two minimums are worth memorizing, because they run in opposite directions. The 30-day device codes carry a 10-day floor. The pressure sensor code carries a 30-day floor, and the 90-day pacemaker and defibrillator codes carry a 30-day floor of their own.

The Most Common Code Selection Errors

Treating the rhythm-monitor code as a technical code. Both codes carry their own global, professional, and technical structures now. Neither one is half of the other.

Assigning the physiologic-monitor code to every loop recorder. Loop recorder and insertable cardiac monitor services generally belong to the subcutaneous rhythm-monitor family, because they capture rhythm data.

Using the physiologic-monitor code for pacemaker or defibrillator function data. Battery status, lead impedance, and device function readings point to the 93294 through 93296 range instead. The exception runs the other way: physiologic cardiovascular data derived from a defibrillator does come back to the physiologic-monitor code.

Calling every remote service RPM. General remote physiologic monitoring runs on its own code set, which changed for 2026 and now includes 99445 for 2 to 15 days of data and 99470 for the first 10 minutes of treatment management. Those codes aren’t interchangeable with implantable cardiac interrogation. CMS RPM guidance lays out the separate framework.

Coding from the diagnosis. Heart failure explains why a patient is being monitored. It never selects the procedure code by itself, and a pressure sensor implanted for heart failure points to 93264, not to a device interrogation code.

What Changed After CMS Deleted G2066?

CMS deleted G2066 effective January 1, 2024. The technical practice expense for remote interrogation moved into CPT 93297 and 93298. Current claims may report the global service, or split it into separate professional and technical components, depending on which entity performed the work.

Period	Technical reporting structure
Before 2020	The older 93299 structure
2020 to 2023	G2066 reported the technical component
January 1, 2024 onward	Technical component built into the two device codes

Before 2020

93299 carried the technical reporting for these remote interrogation services until it was deleted effective January 1, 2020. That single fact explains a lot of the confusion still floating around online. Older articles, vendor PDFs, and payer manuals written before 2020 still name it.

From 2020 Through 2023

CMS created G2066 to fill the gap 93299 left, and it reported the technical portion of qualifying remote interrogation services for four years. The code was contractor priced the entire time, which is part of why payment moved around so much.

That four-year window matters operationally. Charge rules, order sets, and vendor interface mappings built between 2020 and 2023 still carry the old code, and nobody flags it until claims start coming back.

January 1, 2024 and Later

CMS deleted the G-code and accepted direct practice-expense inputs for both device codes instead. What you get now is a normal component structure: global reporting when one entity does everything, or split reporting when two entities divide the work. CMS documented the same shift on the hospital outpatient side in MLN Matters MM13568, which confirms both device codes were designated as having a technical component under the fee schedule.

Picture a device clinic whose billing system still appends the retired technical code automatically, because the remote monitoring workflow hasn’t been touched since 2023. The claims look complete. They just carry a code that stopped existing.

The fix is workflow, not appeals. Update the charge rules, review payer mappings, audit the standing order sets, check vendor interface mappings, retrain the billing staff, and pull every claim submitted since January 1, 2024 for review.

The HRS 2024 PFS update confirms both halves of that change: the deletion, and the direct practice-expense inputs that replaced it. That structural change is exactly why the service can now be billed globally or divided between two entities.

How to Bill CPT 93297 Globally or With Modifier 26 or TC

CPT code 93297 doesn’t always need a modifier. Report the global service, with no modifier 26 and no modifier TC, when the same billing entity performs both the professional and technical portions. Append modifier 26 when you’re billing only the physician or QHP analysis and report. Append modifier TC when you’re billing only the technical portion.

Global Billing Without a Component Modifier

Global billing applies when one entity legitimately furnishes both portions of the service. Confirm that before you default to it. Sharing a building doesn’t make the physician and the technical team the same billing entity.

A cardiology practice that receives and processes the remote data through its own workflow, supplies the technical support, and has its own physician complete the analysis and report is billing globally. That’s a real scenario, not a template. Plenty of practices look like that on paper and don’t hold up once you trace the data flow.

Modifier 26 for the Professional Component

Modifier 26 identifies the professional portion when a different entity performs the technical work. The professional record should show clinical analysis, review, findings, a report, and provider authentication.

Modifier TC for the Technical Component

Modifier TC identifies the technical portion when the billing entity furnishes remote data acquisition, receipt of transmissions, technical processing, technician review, technical support, and distribution of results, but not the clinical analysis and report.

Careful here. Having a platform in the workflow doesn’t automatically make the platform vendor the billing entity. Whoever bills TC has to actually furnish that component and meet the applicable billing requirements.

Decide Who Bills Before the Claim Is Created

Does 93297 need a modifier? No modifier means the global service. Modifier 26 means the professional component only. Modifier TC means the technical component only. Which one applies depends entirely on who performed each portion of the work, not on where the work happened or who owns the equipment.

Who performs the work (93297)	How to report it
One entity performs both portions	Global service, no component modifier
Practice performs the professional work only	Modifier 26
Separate entity performs the technical work only	Modifier TC

Five things to settle before charge entry:

1. Identify the technical entity.
2. Identify the interpreting provider.
3. Confirm contractual ownership of each component.
4. Check payer enrollment for both entities.
5. Confirm that two entities aren’t billing the same component.

One warning worth repeating in staff training: modifiers 59, XE, XP, XS, XU, 76, and 77 aren’t substitutes for 26 or TC. They answer a different question, and the bundling section later covers when any of them actually applies.

The ACC component billing update confirms the structure that replaced G2066: global reporting, modifier 26 for the professional service, or modifier TC for the technical service.

When the monitoring vendor, the device clinic, and the billing team each assume somebody else owns a component, duplicate and incorrect claims follow. One O Seven RCM can map that workflow before the claims go out, through cardiology revenue cycle management. Full-service billing is priced at 3% of payer collections.

How Often Can You Bill CPT 93297?

CPT 93297 covers a remote interrogation period of up to 30 days, and CPT instructs that it’s reported only once per 30 days. It also isn’t reported when the monitoring period runs under 10 days. Build non-overlapping cycles, and confirm the date-of-service method your payer accepts before the claim goes out.

How often can 93297 be billed?

Common assumption	Reality
Billable every calendar month	Only when the service and the documentation support it
Always billed on day 31	No universal payer rule; check the payer’s claim policy
Any transmission count qualifies	CPT sets a 10-day floor on the monitoring period
Two entities can never both bill	They can, for different components in the same period
Cycles can run back to back freely	The same component shouldn’t be reported twice

Understanding the “Up to 30 Days” Reporting Period

Four terms get used interchangeably in device clinics, and they don’t mean the same thing. Sorting them out prevents most frequency arguments before they start.

Term	What it means
Reporting period	The span of service the code represents
Frequency restriction	How often the payer permits reporting
Date of service	The date placed on the claim
Claim-submission date	The date your team sends it

“Up to 30 days” describes the service period. It doesn’t tell your billing team which claim date every payer will accept, and treating the 93297 CPT code as an automatic monthly charge is how overlapping cycles start.

Preventing Overlapping Monitoring Periods

Keep one tracking record per patient, and keep it where both the device clinic and billing can see it. Six fields do the work: previous period start date, previous period end date, previous billed date, professional component owner, technical component owner, and next eligible billing date.

Here’s the distinction that matters. A claim from the physician and a claim from the monitoring entity can both be correct when they represent different components of the same period. Two claims for the same component in the same period is a duplicate, no matter who submitted them.

Choosing the Date of Service

Medicare does address this. Under Medicare guidance, the date of service for the interpretation is the date the interpretation occurs or the end of the monitoring period, whichever falls later, and the technical component is billable at the end of the monitoring period.

Commercial payers don’t always follow that. Report completion date, end of monitoring period, payer-specified claim date, and internal charge-entry date are four different dates, and only one of them belongs on the claim.

CPT 93297 Documentation Requirements for a Defensible Claim

Documentation for CPT code 93297 should identify the qualifying implanted system, the monitoring period, the physiologic data reviewed, the provider’s analysis, and the completed signed report. When separate entities handle the professional and technical portions, the record should also show which entity performed which part. The short version: device, dates, data, analysis, findings, report, signature, and component ownership.

The 93297 CPT code description already tells you what the record has to prove. Analysis, review, and report are written into the descriptor itself, so a record that shows none of them doesn’t support the code.

Recommended claim-support checklist

Identify the Monitoring System and Service Period

• Device or system type
• Manufacturer and model, when available
• Clinical reason for monitoring
• Monitoring-period start date
• Monitoring-period end date
• Confirmation that the service was remote
• Previous billed monitoring period

A note reading “remote cardiac monitor reviewed” fails every one of these. It doesn’t establish the code family, and it won’t survive a records request.

Document the Data Reviewed

The record should name the physiologic cardiovascular data reviewed, the relevant sensor information, any trends or notable changes, the comparison against prior readings, and any alerts or abnormal values considered.

No rule requires an abnormal finding. A documented decision to continue the existing plan can be perfectly appropriate, as long as the record shows the data was actually reviewed.

Record the Provider’s Analysis and Findings

Your report should answer four questions: What did the provider find? Did the findings change clinical management? Was further testing or follow-up needed? What was communicated or ordered?

“Data reviewed.” “Continue monitoring.” “No changes.” Those phrases can appear in a report. They just can’t be the report.

Authenticate the Report and Record Component Ownership

Include the provider name, credentials, signature or approved electronic authentication, and report completion date, with a clear link to both the patient and the reporting period. A consistent report title helps your own workflow, though no payer mandates a specific one.

The billing record should also show which entity received the data, which performed technical processing, which physician or QHP analyzed it, which prepared or distributed the report, what each entity billed, and which modifier was applied. Skip that and you get the classic failure: both parties assume the other one billed the technical portion, and nobody does.

Record element	Why it matters
Exact system	Supports correct code selection
Monitoring dates	Prevents overlapping cycles
Data reviewed	Shows a qualifying service occurred
Provider analysis	Supports the professional work
Clinical conclusion	Shows the result of the review
Signed report	Authenticates the service
Component ownership	Supports global, 26, or TC billing

One thing worth separating clearly: a raw transmission, a platform summary, technical processing, and a provider’s authenticated report are four different artifacts. An auto-generated device report isn’t a physician or QHP report, and treating them as equivalent is what turns a paid claim into a recoupment two years later.

If these elements are missing across several monitoring cycles, a cardiac billing audit can show whether the problem starts in the clinical report, charge entry, modifier selection, or the claim workflow itself.

CPT 93297 Reimbursement in 2026

Medicare reimbursement for the 93297 CPT code depends on three things: whether the claim reports the global, professional, or technical service, whether the billing clinician is a qualifying APM participant, and which geographic locality applies. Commercial payment follows the contract instead. Pull the current CMS payment file and your local fee schedule rather than trusting one undated national estimate.

2026 Medicare payment factors

Payment factor	2026 figure
Non-QP conversion factor	$33.4009
Qualifying APM participant conversion factor	$33.5675
Current CMS national payment file	July 2026, PFREV26C
Current CMS RVU file	July 2026, RVU26C

Payment source reviewed: July 2026 CMS release.

The conversion factor isn’t the payment amount. It’s one input, applied to work RVUs, practice-expense RVUs, and malpractice RVUs, then adjusted by geographic practice cost indices and filtered through component modifier, facility status, and QP status.

Reporting method	Modifier	Total RVUs	Non-QP national	QP national
Global service	none	1.82	$60.79	$61.09
Professional component	26	0.73	$24.38	$24.50
Technical component	TC	1.09	$36.41	$36.59

Those are national, non-facility amounts at a geographic index of 1.0, calculated from the CY 2026 total RVUs and the applicable conversion factor. Confirm them against PFREV26C before quoting a figure to a client or a payer.

National Medicare Amounts vs Local Payment

A national amount is a benchmark, not a prediction. Medicare applies geographic adjustment to each RVU component through the GPCI calculation, so the same code pays differently in two localities within the same state. Run your own locality through the CMS PFS lookup tool before you build a fee schedule around a national number.

Global, Modifier 26, and Modifier TC Payment

Each reporting method carries its own value. The components reconcile cleanly here, 0.73 plus 1.09 equals the 1.82 global, but that reconciliation only holds within the same file, status indicator, and setting.

One asymmetry catches practices out. Only the professional component carries a facility payment. Bill the global service or the technical component from a facility setting and there’s no facility rate to pay it against.

QP and Non-QP Conversion Factors

Two factors exist for the first time in 2026. The higher one applies to clinicians who qualify as Advanced APM participants under the Quality Payment Program. The standard factor applies to everyone else. Nobody picks the more favorable one; qualification determines it. The CMS 2026 PFS final rule sets both.

Commercial Payer Reimbursement

Check six things against every commercial remit: the contracted fee schedule, the payer’s global and component rules, any applicable modifier reduction, place of service, payer-specific policy, and the amount actually paid. Full file downloads are available through the CMS July 2026 payment file and the CMS July 2026 RVU file.

NCCI and Bundling Rules for CPT 93297

Don’t reach for modifier 59 or an X modifier the moment a second service lands beside CPT 93297. Check two things first, in this order. CPT blocks several specific pairings outright, and where CPT is silent, the current CMS procedure-to-procedure edit for that exact code pair decides whether a modifier is permitted at all.

Pairings CPT blocks directly: 93264, 93290, 93298, 99091, and 99454. The pacemaker and ICD technical code carries the same instruction from the other direction. Payer edits sit on top of these; they don’t replace them.

Check the Exact PTP Code Pair

1. Identify both codes on the claim.
2. Search the current practitioner or outpatient PTP file for that pair.
3. Check the modifier indicator on the edit.
4. Confirm the record supports a genuinely distinct service.

Your claim scrubber runs on whatever edit file it last ingested. CMS refreshes PTP edits quarterly, so the scrubber is a safety net, not the source of truth. Pull the current CMS PTP edits yourself when a pair looks unfamiliar.

In-Person and Remote Services

CPT settles part of this outright: the in-person physiologic monitor interrogation isn’t reported alongside the remote service. All interrogations during a remote monitoring period, in person or not, are treated as part of that period.

Programming is a different service. A programming evaluation performed during a remote monitoring period isn’t swallowed by the interrogation code, and that distinction is worth training your device clinic on directly.

Separate E/M Services

Remote monitoring doesn’t block a separately necessary evaluation and management service. Four conditions have to hold: the E/M is medically necessary, its documentation stands on its own, any required modifier is supported, and no work already counted in the device service gets counted twice. Nobody should be appending modifier 25 by reflex.

Implantable Monitoring vs General RPM

93298 and 99454 belong to different frameworks, and CPT resolves the overlap by instruction rather than by judgment. Neither device interrogation code is reported with the general RPM device supply code, or with the collection and interpretation of physiologic data code.

Where a genuinely separate device monitors a genuinely separate condition, the analysis shifts to whether each service independently meets its own requirements and whether the payer permits the combination. Same device, same data, two codes is the version that fails.

NCCI edits address correct coding. They don’t establish medical necessity, coverage, or prior authorization. CMS is explicit that this isn’t a medical-review or prior-authorization program, and that private insurers may implement the methodology differently. The 2026 Medicare NCCI manual and the CMS NCCI modifier guidance cover both points.

Question	Action
Does CPT block the pair?	Check the parenthetical first
Is there a PTP edit?	Search the current quarterly file
Does the edit allow a modifier?	Review its indicator
Is the service distinct?	Confirm separate documentation
Is it covered?	Check payer policy separately

Common CPT 93297 Denials and How to Correct Them

Denial problem	Likely root cause	First corrective action	Prevention
Wrong code family	Device or data type never verified	Review the implant and device records	Add a device-level field to the coding workflow
Duplicate service	Overlapping period or duplicated component	Compare prior claims and component ownership	Maintain a patient-level cycle tracker
Modifier denial	Incorrect global, 26, or TC reporting	Confirm who performed each component	Assign ownership before charge entry
Documentation denial	Missing analysis or unsigned report	Obtain the complete clinical report	Standardize the report workflow
Bundling denial	Code pair never verified	Check the CPT parenthetical, then the current PTP file	Add a quarterly edit review
Noncoverage	Payer policy criteria not met	Review the applicable policy	Verify coverage before billing
Underpayment	Wrong component or wrong contract rate	Compare the remit against the fee schedule	Run payment variance reports

Wrong Monitoring System or Code Family

A claim can be complete, clean, and still wrong. Every field passes the scrubber because nothing on the claim is malformed. The service family behind it just doesn’t match the device.

Four confusions produce most of these: physiologic monitoring billed as rhythm monitoring, pacemaker device data billed as physiologic monitoring, pressure sensor monitoring billed as a device interrogation, and general RPM billed as implantable interrogation. Billing 93298 for a physiologic monitor patient sits in the same bucket.

Incorrect Global, 26, or TC Reporting

Three versions show up repeatedly. The practice bills globally while a separate entity actually furnished the technical portion. Both entities report the same technical component. Or the professional claim goes out with no component modifier at all.

All three trace back to the same gap: nobody established component ownership before charge entry.

Overlapping Monitoring Periods

Overlap rarely starts in the coding. It starts in manual spreadsheets, separate vendor and practice trackers, calendar-month assumptions, delayed report signatures, and charges entered before the previous period closed.

Picture a device clinic tracking cycles in one spreadsheet while the vendor portal tracks its own. A report gets signed six days late, the charge posts to the month it was signed, and the next cycle starts on schedule. Two claims now share five days.

Missing or Weak Provider Report

Not every thin report gets denied. But five variations are worth flagging in an internal audit: no report, an unsigned report, a report dated outside the documented period, a platform summary with no clinical analysis, and a report that never identifies the monitored system.

Coverage, Medical Necessity, and Underpayment

A paid claim isn’t automatically an accurately paid claim. Compare the allowed amount against the contracted amount, then check the modifier, place of service, QP status, patient responsibility, and every adjustment code on the remit. Underpayments don’t announce themselves.

When the same denial appears across several monitoring cycles, cardiac claim denial management should go after the root cause rather than resubmitting claims one at a time.

If your team keeps correcting the same cardiac monitoring denial, the problem is almost always upstream of the claim. One O Seven RCM can review the code choice, monitoring period, modifier, documentation, and payer response as one connected workflow.

CPT 93297 Pre-Submission Checklist for Billing Teams

Before the Monitoring Period Closes

Clinical and device check	Confirm
Correct implanted system identified	Yes or no
Data type matches the intended code	Yes or no
Monitoring period documented	Yes or no
Qualifying data received and reviewed	Yes or no
Provider report completed	Yes or no
Report signed and dated	Yes or no

Before the Claim Is Submitted

Billing check	Confirm
Correct code family selected	Yes or no
Global, 26, or TC ownership confirmed	Yes or no
Previous monitoring period reviewed	Yes or no
No duplicate component claim found	Yes or no
Current NCCI edits checked	Yes or no
Payer coverage policy checked	Yes or no
Fee schedule loaded correctly	Yes or no

One line to add at the top of that second list: confirm the service doesn’t actually belong to the rhythm-monitor, pressure-sensor, pacemaker, or defibrillator family. Catching a family error here costs a minute. Catching it after the remit costs a corrected claim and a refund.

Connected medical billing services keep device identification, component ownership, charge entry, submission, payment posting, and denial follow-up inside one accountable workflow instead of four disconnected ones.

After the Remittance Arrives

Reconcile seven data points against every payment: billed code, applied modifier, allowed amount, contracted amount, patient responsibility, adjustment codes, and any prior payment covering the same period. A paid claim is not automatically an accurately paid claim, and variance shows up in the gap between allowed and contracted.

Task	Recommended owner
Device identification	Clinical or device team
Monitoring dates	Device clinic or assigned tracker
Analysis and report	Physician or qualified professional
Component ownership	Billing manager
Code and modifier review	Coder
Claim submission	Billing team
Payment variance review	Payment posting or AR team

Credentialing doesn’t determine which CPT code applies. An inactive or incorrect payer enrollment will still block payment on an otherwise perfect claim.

If your team runs on separate spreadsheets, vendor portals, and manual charge reminders, One O Seven RCM can map the full monitoring-to-payment workflow and show you where it’s breaking.

Frequently Asked Questions About Remote Physiologic Monitoring

How often can 93297 be billed?

The service covers a monitoring period of up to 30 days and is reported only once per 30 days. CPT also instructs against reporting it when the period runs under 10 days. Monitoring cycles shouldn’t duplicate the same component, and the payer’s date-of-service and frequency requirements should be confirmed before submission.

Does 93297 need modifier 26 or TC?

Not always. Report the global service with no component modifier when one entity performs both the professional and technical portions. Append modifier 26 when billing only the clinical analysis and report. Append modifier TC when billing only the technical portion. Confirm actual service ownership before choosing.

What is the difference between CPT 93297 and 93298?

CPT 93297 covers an implantable cardiovascular physiologic monitor and the physiologic cardiovascular data it records. 93298 covers a subcutaneous cardiac rhythm monitor and heart-rhythm data. They’re separate services describing different implanted systems, not the professional and technical halves of one service. Each carries its own component structure.

What replaced G2066?

Nothing replaced it as a standalone code. CMS deleted G2066 effective January 1, 2024, and moved the technical practice expense into the two remote interrogation device codes instead. Reporting now runs global, modifier 26, or modifier TC, depending on which entity performed which portion of the work.

What does the 93298 CPT code description cover?

CPT 93298 describes remote interrogation device evaluation of a subcutaneous cardiac rhythm monitor system for up to 30 days, including analysis of recorded heart rhythm data, with analysis, review, and report by a physician or other qualified health care professional.

Is CPT 93298 the technical component of 93297?

No. Each code describes a different implanted monitoring system and a different data category, and each carries its own global, professional, and technical reporting structure. CPT also instructs that the two codes aren’t reported together.

Can the code be billed with general RPM?

CPT answers this one directly and the answer is no. The remote interrogation device codes aren’t reported alongside the general RPM device supply code or the physiologic data collection and interpretation code. Where a separate device monitors a separate condition, verify that each service independently meets its own requirements and that the payer permits it.

Remote cardiac monitoring claims usually break at the handoff between the device team, the interpreting provider, and billing. Nobody drops the ball on purpose. The workflow just has three owners and no single point of accountability. One O Seven RCM connects those steps through one revenue cycle, priced at 3% of payer collections. If your recent claims show modifier, documentation, frequency, denial, or payment problems, the next step is a focused review through cardiac monitoring RCM support.