CPT code 93296 is the technical component of remote interrogation device evaluation, covering single, dual, or multiple lead pacemaker systems, leadless pacemaker systems, and implantable defibrillator systems for up to 90 days. That work includes receiving transmissions, acquiring device data, technician review, technical support, and distributing results. Interpretation by a physician or qualified health care professional isn’t included.
Trouble starts when a practice treats CPT 93296 as a physician service. Professional interpretation belongs to 93294 for pacemakers and 93295 for ICD systems. Practices make two other errors: billing the technical claim when another entity furnished the work, and submitting a claim per transmission instead of one per 90-day monitoring period.
Before the claim goes out, your biller has to confirm four things: the device qualifies, the billing entity furnished the technical work, the monitoring period is documented and not already billed, and the record shows what the technician did. Miss one and the payer sends it back.
CPT 93296 quick facts
| Field | Detail |
|---|---|
| CPT code | 93296 |
| Service type | Remote interrogation device evaluation |
| Component | Technical component only |
| Monitoring period | Up to 90 days |
| Minimum period | 30 days; CPT says not to report 93296 below that |
| Covered devices | Single, dual, or multiple lead pacemakers, leadless pacemakers, and implantable defibrillator systems |
| Included work | Data acquisition, transmission receipt, technician review, technical support, and results distribution |
| Professional counterparts | 93294 for pacemaker and leadless pacemaker systems, 93295 for implantable defibrillator systems |
| Physician interpretation included | No |
| Routine TC modifier | No; already technical-component-only |
| Per-transmission billing | No; once per period |
AAPC’s CPT code 93296 description confirms the technical-component-only classification. Remote device interrogation splits into a professional component and a technical one, and the 93296 CPT code carries only the technical half of cardiac device monitoring.
What does CPT 93296 cover?
CPT 93296 covers the technical work behind remote device monitoring, from receiving the transmission to delivering the data to the interpreting physician or qualified health care professional (QHP). The technician performs that work, and no part of it includes clinical judgment.
| Included in 93296 | Not included in 93296 |
|---|---|
| Remote data acquisition | Physician analysis |
| Receipt of transmissions | QHP interpretation |
| Technician review | Final professional report |
| Technical support | Clinical decision-making |
| Distribution of results | Medication management |
| Device programming or reprogramming | |
| A separate E/M service |
Remote data acquisition and transmission receipt
Scheduled uploads and unscheduled alert transmissions both arrive during the same monitoring period. Your technician retrieves each one from the manufacturer’s platform and matches it to the right patient and device. Keeping the transmitter connected counts too. None of that turns a single transmission into its own CPT code 93296 claim.
Technician review and technical support
The technician’s review stays technical. That means confirming the transmission arrived complete, flagging missing data or connectivity gaps, noting technical alerts from the device, and organizing the output for the clinician who reads it. Clinical interpretation belongs to the physician or QHP.
Distribution of results
The technical workflow ends when the output reaches the interpreting clinician, and that step belongs to 93296. Sending the report doesn’t create the professional service. Whoever bills the interpretation still has to analyze the data and sign their own report before the professional code goes out.
Which devices qualify for CPT 93296?
CPT 93296 applies to qualifying pacemaker, leadless pacemaker, and implantable defibrillator systems. Implantable loop recorders and physiologic monitor systems transmit data remotely too, and that doesn’t put them under 93296.
Pacemaker systems
Single lead, dual lead, and multiple lead pacemakers all qualify, and leadless pacemaker systems do as well. Lead count doesn’t change the component. Anyone searching for a pacemaker remote monitoring CPT code needs two of them: 93294 is the physician interpretation, and 93296 is the technical work behind it.
Implantable defibrillator systems
ICDs qualify in single, dual, and multiple lead configurations. A CRT-D qualifies too, because a defibrillator with biventricular pacing is still an implantable defibrillator system. The ICD remote monitoring CPT code for interpretation is 93295, while a CRT-P without a defibrillator runs through 93294 as a multiple lead pacemaker.
Devices that don’t belong under 93296
Remote transmission is common to a lot of cardiac devices, and most of them sit outside 93296. Two deleted codes drive the confusion. CMS deleted 93299 effective January 1, 2020, replaced it with G2066, then deleted G2066 effective January 1, 2024.
No separate technical-only code exists for implantable loop recorders or physiologic monitors anymore. CPT 93297 and 93298 carry both components now, so a split between two entities gets reported with modifier 26 or TC on those codes, never with 93296.
| Device or service | Bill 93296? | Where it goes instead |
|---|---|---|
| Pacemaker, single, dual, or multiple lead | Yes | Technical component; 93294 for interpretation |
| Leadless pacemaker | Yes | Technical component; 93294 for interpretation |
| Implantable defibrillator, including CRT-D | Yes | Technical component; 93295 for interpretation |
| Implantable loop recorder or subcutaneous cardiac rhythm monitor | No | 93298, up to 30 days, both components |
| Implantable cardiovascular physiologic monitor | No | 93297, up to 30 days, both components |
| Wireless pulmonary artery pressure sensor | No | 93264, up to 30 days |
| External Holter monitor, up to 48 hours | No | 93224 to 93227 |
| Extended external monitor, 48 hours to 15 days | No | 93241 to 93248 |
| Mobile cardiac telemetry | No | 93228 and 93229 |
| Consumer wearable | No | No billable device evaluation code |
| Blood pressure, weight, or pulse oximetry device | No | Remote physiologic monitoring family |
CPT also carries a parenthetical against reporting 93296 with 93297, so a claim listing both is a coding error before the payer looks at it.
Practices comparing remote, in-person, and device-specific services can work through One O Seven RCM’s cardiology CPT codes 2026 guide for the wider code family.
CPT code 93296 vs. CPT 93294 and CPT 93295
No global code exists for remote device interrogation. You report the professional half and the technical half separately, even when one organization performs both. A cardiology practice doing everything in house still submits two line items instead of one.
CPT 93294 vs. CPT 93296 for pacemakers
| Question | 93294 | 93296 |
|---|---|---|
| Component | Professional | Technical |
| Device family | Pacemaker and leadless pacemaker | Pacemaker, leadless pacemaker, and ICD |
| Main work | Analysis, review, and professional report | Data acquisition, receipt, technician review, technical support, and distribution |
| Typical performer | Physician or qualified health care professional | Practice technical team, hospital, supplier, or qualified monitoring entity |
| Period | Up to 90 days | Up to 90 days |
A hospital device clinic that runs the monitoring platform and employs the technician bills 93296. The cardiologist who reads the transmissions and signs the report bills 93294 under their own enrollment. Neither entity bills the other’s half.
Can CPT 93294 and 93296 be billed together?
Yes. CPT 93294 and 93296 cover different halves of the same remote pacemaker service, so both are reportable when the physician interpretation and the technical work were furnished, documented, and billable by the reporting entity. One organization can report both when it performs both. Separate entities report their own portions.
CPT 93295 vs. CPT 93296 for ICDs
| Question | 93295 | 93296 |
|---|---|---|
| Component | Professional | Technical |
| Device family | Implantable defibrillator, including CRT-D | Pacemaker, leadless pacemaker, and ICD |
| Main work | Physician or QHP analysis, review, and report | Technical receipt, review, support, and distribution |
| Typical performer | Physician or qualified health care professional | Practice technical team, hospital, IDTF, or monitoring entity |
| Period | Up to 90 days | Up to 90 days |
Can CPT 93295 and 93296 be billed together?
Yes. CPT 93295 and 93296 split remote ICD interrogation into its professional and technical portions, and both are reportable when each service was furnished and documented. That holds whether one organization performs both portions or the interpretation and the technical work sit with different entities.
When the professional and technical portions sit with different organizations, someone has to confirm who owns which claim before either one goes out. Specialized medical billing services should verify the device family, service ownership, professional pairing, and monitoring period while the claim is still editable.
Don’t reverse the components
The reversals to watch for: 93294 isn’t the technical pacemaker code, and 93295 isn’t the technical ICD code. CPT 93296 contains no physician interpretation. A monitoring report a technician generated doesn’t become the professional report because a clinician glanced at it.
If you’re not sure whether your practice, the hospital, or your monitoring partner owns each component, One O Seven RCM can map the workflow before the next billing period closes.
How often can CPT 93296 be billed?
CPT code 93296 is reported once per 90-day monitoring period, no matter how many scheduled or unscheduled transmissions arrive during that window. Four claims per patient per calendar year isn’t automatic. The period start date, whether qualifying technical work happened, and whether an earlier period is still open all decide how many claims a patient generates.
The 90-day service period
The claim follows the period. A patient can send 12 scheduled uploads and 3 alert transmissions inside one 90-day window and still generate a single 93296 claim. Multiple transmissions don’t create multiple claims. CPT limits the code to once per 90 days, and CMS cardiac rhythm guidance says the same for 93293 through 93296.
Periods can’t overlap. Once a period opens, the next one starts after it closes, and a practice that restarts the clock early ends up with a duplicate on the second claim. A56602 supports LCD L34833, so check whether your own MAC publishes a version of the same rule.
Does a 30-day minimum apply?
Yes, and the source is CPT itself. The parenthetical under the code says not to report 93293 through 93296 when the monitoring period runs less than 30 days. A56602 restates that limit for the jurisdictions it covers.
Commercial payers can add conditions on top of it, so treat the 30-day floor as settled for Medicare and as a question for everyone else.
A full 90 days isn’t required. Day 91 isn’t a magic billing date, and a patient’s death or insurance change doesn’t by itself authorize an early claim.
What happens when no transmission occurs?
A patient sitting in the monitoring program isn’t a billable service. If no qualifying technical work happened during the period, there’s nothing to bill, and A53018 states it directly for ICD monitoring: when no interrogation service was provided within a 90-day period, the service shouldn’t be billed for that period. Check the transmission log before the claim goes out.
Tracking one period from open to claim
CPT 93296 billing guidelines come down to one tracked interval per patient, per device, with a single claim at the end of it.
[IMAGE: 90-day monitoring period timeline]
The graphic shows how the period is tracked, not a universal date-of-service rule.
Who can bill CPT 93296?
The entity that furnishes the technical service bills 93296, and it has to be enrolled to bill it. Reviewing results later doesn’t create ownership of the technical claim. A53018 puts it plainly: when a service center or a physician other than the interpreting one performs the technical portion, that work is billed with 93296.
When the cardiology practice performs the technical work
Ownership tracks the workflow. Paying for the manufacturer’s portal doesn’t furnish the technical service if no technician in the practice touches the data. Look for transmission receipt, platform access, technician review, technical support, results distribution, documentation, and period tracking sitting inside the practice.
When a hospital or monitoring entity performs the work
A53018 adds a hard limit for the hospital setting: if the interrogation is performed in the hospital, a physician can’t bill for the technical component. The hospital owns that claim. Your cardiologist still reports the professional code when the professional requirements are met, and no one bills the same technical work twice.
Contract language doesn’t override enrollment. A vendor agreement can say whatever the parties want, and Medicare still applies its own enrollment, reassignment, purchased-test, and payer rules to whoever submits the claim.
When an IDTF is involved
Remote monitoring vendors often land in independent diagnostic testing facility (IDTF) territory. CMS billing and coding guidance for IDTFs states that transtelephonic and electronic monitoring services, including pacemaker monitoring and cardiac event detection, should be classified as IDTFs and must meet all IDTF requirements, including a supervisory physician who performs general supervision.
Approved enrollment has limits. An IDTF lists the specific codes it intends to perform on Attachment 2 of the CMS-855B, and only the codes on that list get considered for payment. Confirm 93296 is on it before you assume the vendor can bill. The Medicare Claims Processing Manual carries the IDTF coverage and payment rules in Chapter 35.
| Situation | Likely billing entity | Verify first |
|---|---|---|
| Practice performs the technical workflow | Practice may bill 93296 | Enrollment, documentation, and payer rules |
| Hospital performs the technical workflow | Hospital may own the technical claim | Setting and payer policy; a physician can’t bill the technical component in the hospital |
| IDTF performs the technical workflow | IDTF may bill 93296 | Enrollment and the approved code list on Attachment 2 |
| Vendor supplies software only | Not automatically the billing entity | Contract terms against the work furnished |
| Physician only interprets results | Don’t bill 93296 | Report 93294 or 93295 instead |
Before you assign claim ownership, write down who performs each part of the remote monitoring workflow. One O Seven RCM’s cardiology medical billing services team maps that at onboarding, ahead of the first monitoring period.
Does CPT 93296 require a modifier?
No, not routinely. The code is technical-component-only, so modifier TC adds nothing and modifier 26 has no professional half to split off. The CPT 93296 modifier question usually comes from split-billing habits built around global codes like 93000, where the component split does matter. Use another modifier only when a current edit and your documentation support it.
Should modifier TC be added?
No. Appending TC to flag the service as technical restates what the code already says. Split-billing advice written for codes that carry both components doesn’t transfer here. If your clearinghouse template adds TC automatically, fix the template before the next batch goes out.
Should modifier 26 be added?
No. Modifier 26 doesn’t turn 93296 into physician interpretation, because interpretation lives in a different code. Send the professional service to 93294 for pacemaker and leadless pacemaker systems, or 93295 for implantable defibrillator systems. Neither code needs a modifier to identify which half it covers.
Can modifier 59 or an X modifier be used?
Sometimes, and never by default. Before anyone appends 59, confirm an NCCI edit exists for the pair, check the modifier indicator on that edit, and confirm the two services were distinct with documentation behind them. When a specific X modifier fits the situation, use it instead of 59.
Medicare NCCI PTP edits publish quarterly, effective January 1, April 1, July 1, and October 1, so an edit that cleared last quarter can change. Modifiers 76 and 77 don’t help here either. Repeat-procedure modifiers won’t unlock a second 93296 claim inside a period that only supports one.
| Modifier | Routine with 93296? | What to do |
|---|---|---|
| TC | No | The code already carries the technical work |
| 26 | No | Report 93294 or 93295 for the professional service |
| 59 | Not routine | Verify a current NCCI edit and the documentation first |
| XE, XP, XS, XU | Not routine | Use only when one of them fits the documented facts |
| 25 | Not on 93296 | Goes on a separately identifiable E/M when requirements are met |
| 76, 77 | No | Won’t create a second claim inside one monitoring period |
A focused medical billing audit catches recurring component and modifier errors before they repeat across every patient in the next monitoring cycle. One O Seven RCM can review one claim cycle and show you where component ownership or modifier logic is creating avoidable risk.
Date of service, place of service, and supervision for CPT code 93296
What date of service should be reported?
Four dates live inside one CPT 93296 claim: the period start, the transmission dates, the technical review date, and the claim date of service itself. No CMS rule names one of them as the universal answer. Pick one convention, document it, and verify it against your MAC or payer policy.
Day 1, day 90, day 91, the last transmission, and the report date all show up in practice, and none of them is a national standard. Consistency matters more than which one you choose, because a mixed convention across a device population is what triggers overlap and duplicate reviews.
Which place of service applies?
The patient’s home isn’t automatically the place of service just because the data starts there. CMS ICD monitoring guidance, a contractor article from National Government Services, says remote services should be reported with the place of service where the physician or service center is located, not where the patient sits.
| Where the technical work happens | POS direction to verify |
|---|---|
| Physician office | Office POS may apply |
| Hospital outpatient department | Hospital outpatient setting may apply |
| IDTF or service center | The service center’s location and its enrollment control the answer |
| Patient transmits from home | Don’t default to a patient-home POS |
| Professional and technical split across entities | Each entity reports its own qualifying service |
Don’t drop a POS number into the template until you’ve confirmed the billing entity and checked the payer. A53018 binds National Government Services jurisdictions, so treat it as Medicare contractor guidance and look for your own MAC’s version.
What supervision is required?
Supervision depends on the setting, and A53018 sets a direct supervision requirement for the arrangements it covers. The same article requires the physician billing the professional service to personally review and analyze the data, generate a report, and sign it. Check your own contractor before applying either rule.
CPT 93296 documentation requirements
Documentation for CPT code 93296 has to show six things: the patient, the device, the monitoring period, the transmissions received, the technical work performed, and where the results went. When 93294 or 93295 is billed too, the professional interpretation sits in the record as its own document.
- Patient identity and device details
- Monitoring period start and end dates
- Transmission log covering the period
- Technician review and technical findings
- Proof the results reached the interpreting clinician
- The technical billing entity, named
Medical necessity rides on the diagnosis. A56602 lists the ICD-10 codes that support 93296 in its jurisdiction and notes that Z95.810 applies only when the service is scheduled device monitoring.
Patient and device identification
Start with the patient and the device. Capture the patient’s name and identifier, the manufacturer, the model, the device category, the lead configuration, and the ordering or treating clinician. Add the implant date when your records have it. Treat the list as an audit-readiness standard, since not every payer requires every field.
A53018 also requires a copy of the physician’s order in the record, because the service has to be prescribed by a physician or a qualified non-physician practitioner.
Monitoring-period evidence
Your transmission log does most of the work here. Record the period start and end, the dates of scheduled and unscheduled transmissions, any connectivity interruptions, and what your team did about missed transmissions. What the record has to prove is that qualifying technical work happened inside the period, not that someone watched the device daily.
Technical work record
Technician notes should show the receipt of each transmission, the review itself, the technical findings or how the data got organized, any connectivity support, and any escalation your team made. Name the entity and the personnel who did it. A 93296 CPT code claim with no named technical actor is hard to defend.
Separate professional report
When 93294 or 93295 is billed alongside, the professional record needs independent analysis, review, clinical interpretation, a formal report, a signature, and a date. A53018 is blunt about this: when a service center performs the technical portion, the interpreting physician generates and signs their own report instead of countersigning the technician’s review.
| Record element | Present? |
|---|---|
| Correct patient identified | Yes / No |
| Correct device family confirmed | Yes / No |
| Physician order on file | Yes / No |
| Supporting diagnosis on the covered list | Yes / No |
| Monitoring period recorded | Yes / No |
| Transmission evidence retained | Yes / No |
| Technician review documented | Yes / No |
| Technical support documented where applicable | Yes / No |
| Results distributed to the interpreting clinician | Yes / No |
| Technical billing entity identified | Yes / No |
| Separate professional report retained | Yes / No |
| Signature and date present | Yes / No |
A pre-submission review costs less than correcting the same documentation gap across an entire device population.
CPT 93296 reimbursement in 2026
CPT 93296 reimbursement 2026 depends on the payer, the locality, the billing entity, the setting, and which conversion factor applies to the clinician. As of the July 2026 CMS release, Medicare publishes separate national payment files for qualifying APM participants and everyone else, so a single unlabeled Medicare rate for this code is incomplete.
Why the 2026 rate moved
CMS revalued the technical inputs behind this code in the CY 2026 final rule, accepting a cardiovascular technician as the labor input and updating the equipment code. Boston Scientific’s CY 2026 final rule summary puts the result at a 59% increase in office-based practice expense RVUs and a 63% payment increase, from $19 to $32.
Confirm the current figure against the file before you publish it anywhere. The July 2026 national payment file, PFREV26C, was posted May 21, 2026, and the matching relative value file, RVU26C, took effect July 1, 2026.
The 2026 Medicare rate table
| Payment field | Value |
|---|---|
| Release | July 2026 |
| National payment file | PFREV26C, posted May 21, 2026 |
| Relative value file | RVU26C, effective July 1, 2026 |
| Non-QP conversion factor | $33.4009 |
| QP conversion factor | $33.5675 |
| Non-QP national amount | [extract from PFREV26C non-QP file] |
| QP national amount | [extract from PFREV26C QP file] |
| Total RVU, status indicator, PC/TC indicator | [extract from RVU26C] |
Pull the CPT code 93296 row from the CMS July 2026 payment file rather than a secondary site. Never publish a bare dollar figure. Every rate needs the payer, the release, the setting, the QP category, and whether it’s national or local attached to it.
Why the actual payment differs
CPT 93296 reimbursement 2026 at the national level is a planning figure. Geographic practice cost indices adjust it by locality, and QP status picks which conversion factor applies. Commercial contracts, Medicare Advantage methodology, sequestration, claim edits, deductibles, and coinsurance all move the final deposit.
Setting matters too. When a hospital outpatient department furnishes the technical service, payment typically runs through the outpatient prospective payment system, and the physician fee schedule amount won’t match what lands. Run your own locality through the CMS fee schedule lookup before you quote a number to a physician.
Which services can and cannot be billed with CPT 93296?
Code pairs that represent separate work
CPT code 93296 pairs cleanly with 93294 and with 93295. Each pair splits one remote interrogation into its professional and technical halves, and both halves are reportable when the reporting entity furnished, documented, and owns the work it’s billing. Neither pairing is an NCCI conflict.
Where the real conflicts start
In-person interrogation is the one to watch. CPT carries a parenthetical against reporting 93296 with 93288 or 93289, and A53018 says in-person interrogation during the same 90-day remote period is included in the remote service and shouldn’t be billed separately.
One exception matters. A service center can report 93296 during a period in which a physician or QHP performs an in-person interrogation, because the two entities aren’t billing the same work. That exception doesn’t extend to a practice billing both halves itself.
RPM is the newest overlap question. Remote physiologic monitoring codes cover different devices and different data, so concurrent billing isn’t automatically valid or automatically barred. Confirm the devices are separate, the data is separate, and both services meet medical necessity on their own.
| Combination | What to do |
|---|---|
| Second 93296 inside one period | Treat as a duplicate unless a payer rule supports it |
| 93296 with in-person interrogation (93288, 93289) | CPT bars the pairing; check whether the service-center exception applies |
| 93296 with programming | Programming may be separately reportable when performed and documented |
| 93296 with EKG rhythm strips (93040 to 93042) | A53018 treats these as included in the evaluation |
| 93296 with 93297 | CPT bars the pairing outright |
| 93296 with general RPM | Confirm separate devices, separate data, and separate medical necessity |
| Practice and vendor both billing 93296 | Investigate duplicate technical ownership before either claim goes out |
| Implant or replacement encounter | A53018 says these services shouldn’t be billed when implanting or replacing the device |
How to check NCCI without guessing
Pull the current quarter’s file every time. The Medicare NCCI PTP edits for Q3 2026 took effect July 1, 2026 and were posted June 1, 2026, and a new set lands every quarter. Search both column directions, read the modifier indicator, check the effective date, and only then decide whether documentation proves a distinct service.
Don’t publish an MUE value for this code without opening the current Medicare MUE file. CMS doesn’t assign a published MUE to every CPT code, and some values stay confidential. CPT 93296 billing guidelines that quote a firm unit limit without a source are guessing.
Common CPT 93296 denials and how to prevent them
Most 93296 claim denial patterns trace back to one of four things: the period, the device, the entity, or the record. Work the matrix below by root cause instead of claim by claim, because the same gap usually repeats across every patient on the same monitoring schedule.
| Denial trigger | What went wrong | Prevention | Correction |
|---|---|---|---|
| Duplicate claim | Another 93296 was already billed inside the active period | Central period tracker across every device | Confirm claim ownership and void the true duplicate |
| Overlapping billing period | A new period opened before the previous one closed | Patient-device calendar | Correct the dates only when the record supports it |
| Wrong device family | 93296 used for a loop recorder or a physiologic monitor | Verify the implanted device before charge entry | Replace with the correct code family where supported |
| Wrong billing entity | The practice billed work another entity furnished | Written ownership map for each device program | Coordinate with the service center or the payer |
| No qualifying transmission | The patient was enrolled but no technical service occurred | Transmission audit before the batch releases | Don’t rebill without support |
| Diagnosis mismatch | The submitted ICD-10 code isn’t on the payer’s covered list | Covered diagnosis list loaded per payer | Correct the diagnosis when the record supports it |
| Unsupported modifier | TC, 26, or 59 added by template | CPT 93296 modifier rules built into the scrubber | Remove or replace only when documentation justifies it |
| Missing documentation | Technician review or results distribution absent from the record | Claim-readiness checklist | Submit supporting documentation if it exists |
| Missing professional report | 93294 or 93295 billed without an independent interpretation | Separate report workflow with a signature step | Obtain the report only if it was completed timely |
| Incorrect place of service | The patient’s home used by default | Entity-location validation at setup | Correct the POS according to payer guidance |
| Payer-specific denial | Frequency or authorization rule never checked | Payer-specific edits loaded per plan | Correct, appeal, or write off based on the evidence |
| Underpayment | Claim paid below the expected allowance | Contract comparison at posting | Pursue reconsideration or appeal |
Two different problems produce the same duplicate rejection. A biller submitting one claim per transmission triggers it, and so does a vendor that billed the same period from its own enrollment. Check both before resubmitting, because the second scenario needs a phone call, not a claim edit.
Work the queue in this order: appeal deadline first, then dollar value, then how many patients the same error touched, then whether the root cause repeats, then how likely recovery is. A corrected claim beats an appeal when the error is factual and the window is still open.
One CPT code 93296 claim denial is a correction task. The same denial across a device population is an RCM system failure. One O Seven RCM’s claim denial management services separate technical, coding, documentation, and payer-policy failures before choosing between a corrected claim and an appeal.
One O Seven RCM can trace the denial back to the workflow that created it.
How One O Seven RCM protects CPT 93296 revenue
Remote cardiac monitoring billing breaks in the handoffs. Medical billing for cardiologists gets complicated fast when the technical and professional halves sit in different organizations.
Effective cardiology revenue cycle management connects device verification, period tracking, technical documentation, claim submission, and payment reconciliation in one controlled process.
Before the monitoring period opens
Eligibility verification comes first, then the device category, the payer’s coverage position, and any authorization requirement. Ownership gets settled here too: which entity furnishes the technical work, which clinician carries the professional service, and whether both are enrolled to bill what they’re about to bill.
During the monitoring period
Period tracking runs the whole 90 days. The tracker holds the start and end dates, transmission activity, missing transmissions, technical documentation, service-center responsibility, and professional-report completion. Your team also watches for period overlap early, which is where duplicate claims come from.
Before the claim goes out
Claim scrubbing catches what the workflow missed. Check the CPT code, the professional pairing, the billing entity, the place of service, the modifier logic, the current NCCI edits, the claim date, and the payer’s own requirements. A complete record backs all of it.
After the payer responds
Payment posting is where underpayment recovery starts. Compare the allowed amount against the contract, resolve rejections, and hand denials to a denial management workflow that appeals only what the record supports. AR follow-up keeps everything unpaid moving, and root causes go back to the practice.
One O Seven RCM service pricing
| Service | One O Seven RCM price |
|---|---|
| Full medical billing | 3.0% of payer collections |
| Provider credentialing | $107 per insurance |
One O Seven RCM charges 3.0% of payer collections for full medical billing. The fee applies to money collected from payers, not to billed charges. Provider credentialing runs $107 per insurance when enrollment support is part of the engagement.
That percentage is One O Seven RCM’s service fee. What Medicare pays for 93296 is a separate number from a separate source.
See whether the problem in your 93296 revenue cycle is code selection, period tracking, claim ownership, or payer adjudication before you change the clinical workflow.
[BUTTON: Get a Free 93296 Billing Review]
CPT code 93296 FAQs
What does CPT 93296 mean?
CPT 93296 is the technical component of remote interrogation for pacemaker, leadless pacemaker, and implantable defibrillator systems, covering a monitoring period of up to 90 days. Physician interpretation isn’t part of it.
Is 93296 a professional or technical code?
Technical only. The code carries data acquisition, transmission receipt, technician review, technical support, and results distribution. For interpretation, 93294 is the pacemaker remote monitoring CPT code and 93295 is the ICD remote monitoring CPT code.
How often can CPT 93296 be billed?
Once per qualifying 90-day monitoring period, no matter how many transmissions arrive. CPT also bars reporting the code when the period runs shorter than 30 days. Some payers add their own frequency conditions on top.
Can CPT 93294 and 93296 be billed together?
Yes. CPT 93294 and 93296 cover the professional and technical halves of remote pacemaker interrogation. Both are reportable when each service was furnished and documented, whether one organization performs both or two entities split them.
Can CPT 93295 and 93296 be billed together?
Yes. CPT 93295 and 93296 split remote ICD interrogation into its professional and technical portions. Report both when each portion was furnished and documented by the entity billing it. Neither pairing is an NCCI conflict.
Does CPT 93296 require modifier TC?
No. The code is technical-component-only, so TC restates what it already says. Modifier 26 doesn’t apply either, because there’s no professional half inside 93296 to split off. Check any other CPT 93296 modifier against a current edit before you append it.
Does 93296 include physician interpretation?
No. A technician performs and documents the work 93296 covers. When a physician or qualified health care professional analyzes the data and signs a report, that service goes to 93294 or 93295 instead.
Can 93296 be used for an implantable loop recorder?
No. Loop recorders and subcutaneous cardiac rhythm monitors report under 93298 for periods of up to 30 days. CMS deleted the old technical-only codes 93299 and G2066, so 93298 now carries both components.
Can 93296 be billed with RPM?
Concurrent billing isn’t automatically valid or automatically prohibited. The devices, the data, and the medical necessity have to be separate, each service needs its own documentation, and current payer edits have to allow the pairing.
What is the 2026 Medicare reimbursement for CPT 93296?
CPT 93296 reimbursement 2026 comes from the July 2026 national payment file, and Medicare publishes separate amounts for qualifying APM participants and everyone else. Geographic adjustment moves the number again, so check your own locality.
Protect every eligible remote monitoring claim
The clinical team, the technical team, and the billing team all touch one monitoring period, and they don’t always agree on when it started.
Settle which entity owns the technical claim, then put the period and the record on one calendar everyone reads from. What remains is following the money until the account closes.
One O Seven RCM connects those records before the claim goes out and stays on the account until it’s paid.
[BUTTON: Get My Billing Review]