Most pacemaker claims that get denied were never clinically wrong. They failed because a code did not match the operative report, a device check was reported as a programming service, a remote-monitoring line was submitted before the 30-day window closed, or a generator change was unbundled from the removal it already includes. Pacemaker work spans surgery, device clinic follow-up and remote monitoring and each of those runs on different codes, different documentation and different payer rules. Treating them as one billing problem is where revenue leaks.

This Pacemaker Billing Guide walks through how the codes are structured, what documentation each service needs, how Medicare and commercial payers differ and where claims break down. The goal is practical: fewer preventable denials and cleaner first-pass claims for implantation, generator replacement, lead procedures, interrogation, programming and remote monitoring.

One rule sits under everything that follows. No CPT code, diagnosis, or modifier is payable on its own. Payment depends on the exact service performed, the provider type, the place of service, the payer, the date of service and whether the documentation supports what was billed. Verify current AMA CPT descriptors and payer policy before submitting, because code descriptions and coverage rules change.

What is pacemaker billing?

Pacemaker billing is the process of coding, documenting, submitting and collecting payment for cardiac pacemaker services. It covers the surgical placement or revision of a pacemaker system, removal of the device or leads and the ongoing evaluation of the device through in-person checks and remote monitoring. Each of these is a separate billable event with its own coding logic.

A pacemaker system has two main parts: a pulse generator (the battery and circuitry) and one or more leads (the electrodes that connect the generator to the heart). Coding a pacemaker service starts with knowing exactly which parts were placed, replaced, removed, or evaluated, whether the system is single chamber, dual chamber, or leadless and whether the approach was transvenous or transcatheter. A claim that does not reflect those specifics is a denial waiting to happen.

Pacemaker services that may require separate billing

The services below are distinct. Do not assume they share a code family, a global period, or a coverage rule.

Pacemaker CPT coding

CPT selection follows the service actually performed, documented in the operative note or the device report. The families below are current under the AMA CPT code set; confirm descriptors against the current edition before use and never choose a code because the procedure name looks similar.

Implantation of a new or replacement system

For a permanent pacemaker placed with transvenous leads, the system codes are 33206 (atrial lead, single chamber), 33207 (ventricular lead, single chamber) and 33208 (atrial and ventricular leads, dual chamber). These codes include placement of the leads and the generator as a complete system, so the leads are not reported separately when a full new system is placed. Radiologic guidance such as fluoroscopy used during the implant is bundled and not separately billable under National Correct Coding Initiative (NCCI) rules.

Medicare assigns pacemaker implantation a 90-day global surgical period, which means routine postoperative care within that window is already paid for in the procedure.

Generator (pulse generator) replacement

When only the battery and circuitry are exchanged and the existing leads stay in place, the generator-change codes are 33227 (single-lead system), 33228 (dual-lead system) and 33229 (multiple-lead system). These already include removal of the old generator. Reporting the generator-removal code 33233 in addition to a 33227 to 33229 code is unbundling and will trigger an edit. Distinguish this clearly from a full new system implant (33206 to 33208), which is a different service with different documentation.

Lead and revision procedures

Lead work does not share a single code with generator changes. Repositioning, repair, replacement and extraction each map to their own codes and the approach matters (transvenous versus a more invasive approach). Transvenous electrode removal, for example, is reported with codes in the 33234 to 33235 range depending on how many leads are removed and lead extraction is a more involved service than a simple removal. The operative report has to state what was done to each lead. Vague documentation is one of the most common reasons revision claims are downcoded or denied.

Removal

Removal coding depends on what came out. Generator-only removal (33233) is different from lead removal or extraction and both differ from a generator change where a new device is placed in the same session. The record must identify each component removed and the technique used. When a removal is driven by a device complication or infection, the diagnosis coding and the operative detail carry the medical necessity.

Leadless pacemakers

A leadless pacemaker placed in the right ventricle by transcatheter approach is reported with 33274 (insertion or replacement) and 33275 (removal). These codes bundle imaging guidance and any device evaluation performed during the procedure, so those are not separately reported. Newer pacing approaches, including conduction system pacing, can involve additional or add-on codes, so verify current AMA guidance for those cases rather than forcing them into the standard transvenous family.

Pacemaker device interrogation, programming and monitoring

This is where interchangeable-looking services cause the most coding errors. Interrogation, programming and remote monitoring are separate services with separate codes.

Interrogation retrieves and evaluates the data stored in the device without changing its settings. The in-person interrogation code for a pacemaker is 93288.

Programming device evaluation goes further: the provider tests and adjusts device parameters with iterative measurements. Pacemaker programming evaluations are reported with 93279 (single lead or leadless), 93280 (dual lead) and 93281 (multiple lead). Reporting a programming code when only an interrogation was documented, or the reverse, is a documentation mismatch that payers catch on review.

Peri-procedural evaluation around a separate surgery, procedure, or test is reported with 93286 when the device is checked and reprogrammed before or after that event.

Transtelephonic monitoring (TTM) of a pacemaker rhythm strip over a period of up to 90 days is reported with 93293.

Remote interrogation over a period of up to 90 days uses 93294 for the professional component (the physician or qualified professional’s interim analysis, review and report) and 93296 for the technical component (remote data acquisition, technician review and distribution of results). A practical frequency rule applies here: the up-to-90-day remote codes should not be reported if the monitoring period is less than 30 days. Reporting them too early, or more than once per defined period, produces frequency denials.

Because these services carry professional and technical components, the modifier and place-of-service details matter as much as the base code. Device clinic workflows that map each documented activity to the correct code prevent a large share of avoidable denials, which is one reason many practices route electrophysiology and device billing through coders who work in this area daily.

Pacemaker ICD-10-CM coding

The diagnosis code has to reflect the reason for the encounter as documented, following the ICD-10-CM Official Guidelines. Selecting a diagnosis to improve payment is never appropriate.

For a device follow-up encounter, the status code Z95.0 (presence of a cardiac pacemaker) is not the right primary code, because it carries an Excludes1 note against the device-management category. When the device is being checked or evaluated, the encounter is reported with a Z45.01x code, such as Z45.010 (checking and testing of the pacemaker pulse generator or battery) or Z45.018 (adjustment and management of another part of the pacemaker). Z95.0 describes a patient who simply has the device, with no attention directed to it during that visit.

For implantation, the supporting diagnosis is the rhythm disorder that justifies the device, documented by the treating provider. Categories recognized under Medicare’s national policy include documented, non-reversible symptomatic bradycardia from sinus node dysfunction and second- or third-degree atrioventricular block, among others. A diagnosis code that establishes the indication does not by itself guarantee coverage; it has to be supported by the record and paired with correct claim construction.

When a device causes a problem, complication coding from the mechanical-complication categories (the T82 range) may apply, sequenced according to the guidelines. Unsupported diagnoses, missing specificity and incorrect sequencing are frequent, correctable denial causes. Aligning diagnosis and procedure is core to accurate cardiology medical coding.

Pacemaker medical necessity

Medical necessity means the service is supported by the patient’s documented clinical circumstances under the applicable coverage policy. A payable claim needs both a correct code and a record that shows why the service was reasonable and necessary.

For single- and dual-chamber permanent pacemakers, Medicare coverage runs through National Coverage Determination (NCD) 20.8.3. Under the CMS billing and coding articles tied to that NCD, implantation reported with 33206, 33207, or 33208 must carry a covered indication and the KX modifier is appended to attest that the NCD criteria are met. Per CMS Transmittal R3204CP, Medicare Administrative Contractors (MACs) return these pacemaker claims as unprocessable when the KX modifier is absent. Notably, the NCD does not address generator replacement, so 33227 to 33229 and 33233 are handled under MAC and local policy and general medical necessity rather than NCD 20.8.3.

Commercial payers apply their own medical policies, which can define covered indications, documentation and frequency differently from Medicare. A service that Medicare covers under NCD criteria may be evaluated against a separate commercial policy, so medical necessity should be checked against the specific payer and plan before the claim goes out.

Pacemaker documentation requirements

Documentation is what connects the code to the payment. What is required varies by service, payer and contractor, but the record generally has to support the CPT selected, the diagnosis, the medical necessity and any modifier.

For surgical services, the operative report should identify the indication, the type of system (single, dual, or leadless), the generator and lead details including model and serial numbers and exactly what was placed, replaced, revised, or removed. For a generator change, the record should show the old device removed and the new one placed. For lead work, it should describe the work on each lead.

For device clinic services, the report should show the date of service, the provider, the device type, the interrogation findings or the programming parameters adjusted and the clinical reason for the evaluation. Remote-monitoring documentation should support the monitoring period and the review performed. Authentication and a valid signature are required where policy calls for them.

Draw a clean line between two ideas: documentation that clinically supports a service and documentation a specific payer or coverage policy requires for that service. Both matter and a claim can be clinically sound yet still fail a payer’s documentation rule.

Pacemaker prior authorization

Prior authorization requirements depend on the payer and the specific service and they are not universal. Traditional (fee-for-service) Medicare’s nationwide prior authorization program for hospital outpatient department services covers a defined list of categories (such as blepharoplasty, vein ablation, cervical fusion with disc removal, implanted spinal neurostimulators and facet joint interventions) and pacemaker implantation is not on that list. So traditional Medicare generally does not require prior authorization for a pacemaker implant.

Medicare Advantage plans and commercial payers frequently do require prior authorization for device procedures and some also apply it to remote monitoring or specific device services. Common authorization-related problems include a missing authorization, an authorization for a different procedure or provider, an expired authorization, a location mismatch, or an approval that does not match the level of service billed.

Keep two things separate. Obtaining authorization confirms the payer agreed to consider the service; it does not by itself prove medical necessity. The record still has to support the service at adjudication. Verifying benefits and securing authorization ahead of the procedure is part of front-end cardiology medical billing and prevents denials that are otherwise hard to overturn after the fact.

Eligibility and coverage

Eligibility verification confirms that coverage is active and that the demographic and payer information is correct. It does not, on its own, confirm that a particular pacemaker service is covered. Coverage depends on the plan’s benefits, medical policy, network status and any frequency or coverage limits.

Recurring eligibility and coverage issues include inactive coverage on the date of service, incorrect insurance information, coordination-of-benefits problems, out-of-network status, non-covered services and submission to the wrong payer. Device-monitoring services carry their own coverage and frequency considerations that a basic eligibility check will not surface, which is why front-end verification and coverage review are separate steps.

Global surgery considerations

Pacemaker implantation carries a 90-day global surgical period under Medicare, so routine follow-up related to the procedure within that window is included in the implant payment and is not separately billable. Not every pacemaker-related service shares that treatment and device clinic services follow their own rules rather than the surgical global period.

Global-period modifiers exist for the situations the package does not cover: an unrelated evaluation and management (E/M) service during the global period, a significant and separately identifiable E/M on the same day as a procedure, staged or related procedures, an unplanned return to the operating room and unrelated procedures during the global period. Each has specific criteria and documentation. Applying them without support is a compliance problem, not a workaround. Confirm current Medicare global-period rules for the specific code before relying on them.

NCCI and bundling

The National Correct Coding Initiative defines which services are bundled and which can be reported together. Several pacemaker relationships come up often: imaging guidance is bundled into the implant and leadless codes, the generator-change codes include removal of the old generator and device evaluation performed during a leadless procedure is included in that procedure.

When two services are genuinely separate and the documentation supports it, a modifier such as 59 may allow separate reporting, but a modifier should never be added just to clear an edit. NCCI edits also do not apply identically across every payer, so commercial edit sets and policies should be checked rather than assumed to mirror Medicare.

Pacemaker modifiers

Modifiers describe circumstances; they are not tools to force payment. Each must be supported by the actual service, current coding guidance, the documentation and the payer’s rules.

• Modifier 25: a significant, separately identifiable E/M service by the same provider on the same day as a procedure or other service. Common when a distinct evaluation happens alongside a device service.
• Modifier 26: the professional component of a service that has both a professional and a technical component, relevant to device-evaluation interpretation and to imaging.
• Modifier 59: a distinct procedural service, used to separate services that would otherwise bundle, only when the record supports the distinction.
• Modifier 76: a repeat procedure or service by the same provider.
• Modifier 77: a repeat procedure by a different provider.
• Modifier 91: a repeat clinical diagnostic laboratory test, which generally does not apply to device procedures and should not be used to report repeated device evaluations.

Adding any of these does not guarantee reimbursement and an unsupported modifier is itself a frequent denial trigger.

Professional versus facility pacemaker billing

A physician claim and a facility claim for the same encounter are not the same workflow. The professional claim (typically on the 1500 claim form) reports the provider’s work. The facility claim (typically on the UB-04) reports the hospital or ambulatory surgery center’s resources and it follows a different payment methodology, such as the outpatient prospective payment system for hospital outpatient services.

Device-evaluation services often split into a professional component and a technical component and the place of service determines how the practice expense is handled. Reimbursement for the same in-office device service can differ from the facility setting because of that practice-expense difference. Coding responsibilities and documentation expectations differ between the two claims and reconciling them is part of end-to-end revenue cycle management.

Common pacemaker billing and coding errors

Common pacemaker claim denials

Pacemaker claim rejection vs denial vs underpayment

These statuses call for different responses. Payer portals, clearinghouses and remittance systems may describe them with different language, so read the specific message rather than assuming.

A rejection often needs only a data fix, while a denial needs a root-cause review before any resubmission. Sending the same claim again without addressing the reason usually produces the same denial.

Pacemaker claim denial workflow

A structured process keeps denials from recurring:

1. Identify the denial and capture the claim.
2. Read the denial code and message.
3. Review the original claim as submitted.
4. Review the CPT and HCPCS coding against the record.
5. Review the ICD-10-CM coding and sequencing.
6. Review the medical record and the procedure or device documentation.
7. Verify authorization.
8. Verify eligibility and coverage.
9. Check the applicable payer policy.
10. Identify the root cause.
11. Decide whether a corrected claim or an appeal is appropriate.
12. Correct the coding or claim data when appropriate.
13. Gather the supporting documentation.
14. Submit the corrected claim or appeal by the payer’s method and deadline.
15. Track the response.
16. Post the payment or adjustment accurately.
17. Record the root cause so the pattern can be fixed upstream.

Resubmitting without resolving the denial reason wastes the filing window and often burns an appeal level.

How to handle a denied pacemaker claim

Work the denial in order: read it carefully, identify the exact reason, review the claim, check the CPT and HCPCS coding, check the ICD-10-CM coding, review the documentation, verify authorization, verify coverage and check payer policy. Then decide whether the fix is a corrected claim or an appeal, submit the right one, track the outcome and update the denial log. Whether correction or appeal is correct depends entirely on the denial reason, which is why the root-cause step comes before the response.

How to appeal a pacemaker claim denial

An appeal answers the payer’s stated reason; it is not a resubmission of the same record. Read the denial reason, decide whether it is correctable and review the payer’s policy. Compare the claim against the documentation, verify the CPT, HCPCS and ICD-10-CM coding and identify the medical necessity support in the record. Gather the relevant records, write a concise argument that ties the denial reason to the documentation and the applicable policy, attach the supporting material and submit by the payer’s required method and within its deadline. Track the appeal to resolution.

Appeal deadlines and levels vary by payer and by denial type, so there is no single universal deadline. Structured denial management keeps appeals moving and feeds the outcomes back into prevention.

Documentation that may support a pacemaker appeal

Depending on the denial, relevant documents can include the claim and remittance advice or EOB, the medical records, the procedure report, device documentation, physician notes, diagnostic information, authorization and referral details, the coding rationale, the applicable payer policy and the medical necessity documentation. Not every appeal needs every document; match the packet to the specific objection.

Medicare pacemaker billing considerations

Medicare coverage for single- and dual-chamber permanent pacemakers is governed by NCD 20.8.3 and the associated CMS billing and coding articles, which list the covered indications and require the KX modifier on implant claims (33206 to 33208) to attest that the criteria are met. MACs treat these claims as unprocessable without the KX modifier. Generator replacement is outside the NCD, so those services fall to MAC and local coverage policy and general medical necessity.

Beyond coverage, Medicare billing brings NCCI edits, global-period rules, defined modifier requirements, place-of-service rules and the professional-versus-facility payment split described above. Local Coverage Determinations and MAC billing articles can add contractor-specific detail, so requirements can vary by jurisdiction. Verify the current CMS and MAC guidance for the date of service rather than assuming a single national rule applies everywhere.

Commercial payer considerations

Commercial payer requirements often differ from Medicare and vary by insurer and plan. Differences can appear in prior authorization, referral requirements, medical policies, network participation, timely filing windows, corrected-claim and appeal deadlines, documentation expectations, device-monitoring coverage, frequency limits and provider enrollment. Do not assume a commercial plan follows Medicare’s NCD or edit set. Check the specific policy for the payer and plan on the date of service and confirm any payer-specific rule against its current official policy.

Medicare vs commercial insurance

Commercial requirements vary widely, so treat this table as a starting point and confirm the details against each payer’s current policy.

Pacemaker billing workflow

A clean revenue cycle for pacemaker services moves through predictable stages: procedure planning, eligibility verification, coverage review, prior authorization when required, documentation, coding, claim validation, claim submission, adjudication, ERA or EOB review, payment posting, denial and accounts-receivable follow-up, correction or appeal and root-cause analysis. Each stage has a failure mode and catching a problem early (an eligibility gap before the procedure, a coding mismatch before submission) is far cheaper than reworking a denial after the fact. Coordinated claims submission and tracking keeps rejections from turning into denials downstream.

Reimbursement considerations

Pacemaker reimbursement is shaped by many factors and no code is payable by name alone. Payment depends on CPT and HCPCS selection, diagnosis coding, medical necessity, payer policy, place of service, the professional-versus-facility split, modifier application, global-period rules, NCCI edits, documentation, authorization, network participation, frequency limits, claim accuracy and the contractual rate. Physician services price through the Medicare Physician Fee Schedule using relative value units, while hospital outpatient services price through the outpatient prospective payment system and commercial payment follows the contract. Because these variables interact, the same service can pay differently across settings and payers and accurate payment posting against contracted rates is what surfaces underpayments instead of letting them slip through.

Frequency and monitoring considerations

Device-evaluation frequency is a common denial source. In-person interrogation (93288) is reported per encounter, while the remote codes (93294 and 93296) and transtelephonic monitoring (93293) are defined over periods of up to 90 days. The remote up-to-90-day codes should not be reported when the monitoring period is under 30 days and they should not be duplicated within the same defined period. Same-day and overlapping-service situations need attention so that a remote period and an in-person check are not reported in a way that conflicts. Payer and Medicare frequency limits vary, so verify the current rule before assuming a specific interval is allowed.

Place of service

Place of service has to reflect where the service was actually performed and it affects payment, edits and the professional-versus-facility split. Pacemaker-related services occur across settings: the office, the hospital outpatient department and the inpatient setting, among others. The place of service is never selected to influence reimbursement; it is reported accurately and the claim is built to match.

Credentialing and provider enrollment

Even a perfectly coded, well-documented pacemaker claim will deny if the billing provider is not properly enrolled. The NPI, taxonomy, Medicare and commercial enrollment, network participation and whether the service is billed under a group or individual identifier all affect processing. Credentialing gaps produce denials that look like coding problems but are not, so enrollment and network status should be confirmed before claims go out.

Realistic pacemaker billing scenarios

The examples below are hypothetical and illustrative. They are not real patient cases and they do not replace current official coding guidance.

Example 1: Implantation documentation mismatch. A dual-chamber system is placed, but the operative note only clearly describes one lead. The claim for 33208 risks a downcode or denial because the record does not support two leads. Review the operative report against the code and query the provider when lead documentation is incomplete before billing.

Example 2: Generator replacement. A pulse generator is exchanged with the leads left in place and the claim is submitted as 33208. The service was actually a generator change (33228 for a dual-lead system). Confirm from the note whether any leads were placed; when only the generator changed, use the generator-change family.

Example 3: Device interrogation. An in-person device check retrieves data but adjusts no parameters, yet the claim reports a programming evaluation (93280). The record supports interrogation (93288), not programming. Match the code to the documented activity.

Example 4: Remote monitoring. A remote pacemaker line is billed 20 days after monitoring began. The up-to-90-day code should not be reported before the 30-day mark. Track the monitoring period start date and hold the claim until the period requirement is met.

Example 5: Medical necessity denial. A Medicare implant claim is denied for medical necessity because the KX modifier was omitted and the covered indication is not clearly documented. Confirm the indication in the record and append KX when the NCD criteria are met, then appeal with the supporting documentation if the service qualified.

Example 6: Prior authorization mismatch. A commercial plan authorized a single-chamber implant, but a dual-chamber system was placed and the claim denies. Confirm that the authorization matches the service actually performed and pursue an updated authorization or an appeal with clinical support.

Example 7: Modifier issue. An office E/M is billed on the same day as a device service without modifier 25 and the E/M denies as bundled. When a significant, separately identifiable E/M occurred and is documented, apply modifier 25; when it did not, do not report a separate E/M.

Example 8: NCCI or bundling issue. A generator change (33228) is billed with generator removal (33233) and the removal denies. The removal is bundled into the generator change. Drop the removal line and bill the generator-change code alone.

Example 9: Duplicate claim. A device service is resubmitted because payment was slow and it denies as a duplicate. Correcting a claim and duplicating one are different actions: use the corrected-claim process with the proper frequency indicator rather than resubmitting an identical claim.

Example 10: Incomplete procedure documentation. A lead revision is billed, but the note does not describe the specific work on the lead. The claim denies for insufficient documentation. Review the operative detail and query the provider so the record supports the revision before billing.

How to analyze pacemaker denial trends

One-off denials get worked; recurring denials get prevented. Log each pacemaker denial with the denial reason, payer, CPT and HCPCS code, ICD-10-CM code, provider, facility, location, procedure or device-service type, date of service, dollar amount, authorization status, appeal outcome, correction made and time to resolution.

Patterns in that log point to specific fixes. A cluster of medical necessity denials from one payer suggests a documentation or coverage-policy gap. Repeated modifier denials point to a coding-workflow issue. Frequent authorization denials indicate a front-end process problem. Remote-monitoring frequency denials suggest date-tracking needs to tighten. The value of the log is that it converts scattered denials into a prioritized list of root causes and training needs.

Pacemaker billing metrics

Useful metrics include the pacemaker denial rate, denied claim volume, denied dollar value, top denial reasons, payer-specific denial rate, coding-related denials, authorization-related denials, medical necessity denials, documentation denials, device-monitoring denials, appeal overturn rate, days to resolution, recurring denial categories and accounts-receivable aging for pacemaker claims.

A basic denial rate is:

Denial rate = denied claims ÷ applicable adjudicated claims × 100

Organizations define the denominator differently (some use total claims submitted, others use adjudicated claims in a period), so the denominator should be stated clearly whenever the metric is reported and comparisons should use the same definition.

How professional cardiology billing services can help

Pacemaker billing gets hard where surgery, device clinic follow-up and remote monitoring meet, because each runs on different codes, documentation and payer rules. Practices with high device volume often face the same pressure points: matching codes to operative and device reports, tracking remote-monitoring periods, keeping authorizations aligned to the exact service and working denials before filing windows close.

Specialized support can help with pacemaker coding review, claim submission, eligibility verification, prior authorization, denial management, accounts-receivable follow-up, appeals, payment posting, coding audits, payer-rule monitoring and denial-trend analysis. A team focused on cardiovascular care is better positioned to catch a generator-change miscode or a remote-monitoring frequency error before the claim goes out rather than after it comes back. Cardiology Billing Services works only in this specialty and can review pacemaker and device workflows end to end; a billing consultation is the starting point for a practice that wants a closer look at its device revenue cycle.

Frequently asked questions

What is pacemaker billing? Pacemaker billing is the coding, documentation, submission and collection of payment for pacemaker services, including implantation, generator replacement, lead procedures, removal, in-person interrogation and programming and remote monitoring. Each service has its own codes and rules.

What CPT codes are used for pacemaker procedures? Common families include 33206, 33207 and 33208 for system implantation, 33227 to 33229 for generator replacement, 33233 for generator removal, 33234 to 33235 for transvenous lead removal and 33274 to 33275 for leadless devices. Confirm current AMA CPT descriptors before use.

How is pacemaker implantation billed? Report the system code that matches the leads placed (atrial, ventricular, or both), from the operative note. The leads and generator are included in the system code, imaging guidance is bundled and Medicare applies a 90-day global period. On Medicare claims, the KX modifier attests that NCD 20.8.3 criteria are met.

How is pacemaker generator replacement billed? Use 33227, 33228, or 33229 based on whether the system is single, dual, or multiple lead. These codes already include removal of the old generator, so the removal code 33233 is not reported separately with them.

How are pacemaker interrogation services billed? In-person interrogation of a pacemaker is reported with 93288. The record must show the device data was evaluated. Interrogation is separate from programming, which involves adjusting device parameters.

What is the difference between pacemaker interrogation and programming? Interrogation retrieves and evaluates stored device data without changing settings. Programming (93279 to 93281) tests and adjusts device parameters with iterative measurements. The code has to match what the documentation shows.

How is remote pacemaker monitoring billed? Remote interrogation over a period of up to 90 days uses 93294 for the professional component and 93296 for the technical component. These should not be reported if the monitoring period is under 30 days and not more than once per defined period.

Can incorrect ICD-10-CM coding cause a pacemaker claim denial? Yes. Using a status code such as Z95.0 for a device-management visit, missing specificity, or incorrect sequencing can cause denials. Device-check encounters use the Z45.01x codes and the diagnosis has to reflect the documentation.

Can modifier errors cause pacemaker billing denials? Yes. A missing KX on a Medicare implant, or an unsupported 25 or 59, is a frequent denial cause. Modifiers describe circumstances and must be supported by the record; they do not force payment.

What documentation is needed for pacemaker billing? For procedures, the operative report should identify the indication, system type, device and lead details and the work performed. For device services, the report should show the date, provider, device type, findings or parameters and the reason for the evaluation, with a valid signature. Exact requirements vary by payer.

Does pacemaker implantation require prior authorization? Not universally. Traditional Medicare generally does not require prior authorization for pacemaker implantation, since it is not on the CMS hospital outpatient prior authorization list. Many Medicare Advantage and commercial plans do require it, so verify the specific payer.

How does Medicare handle pacemaker billing? Medicare covers single- and dual-chamber permanent pacemakers under NCD 20.8.3, requires the KX modifier on covered implant claims and applies NCCI edits, global-period rules and place-of-service rules. Generator replacement falls under MAC and local policy. MAC-specific guidance can vary by jurisdiction.

Do commercial insurers use the same pacemaker billing rules as Medicare? Not necessarily. Commercial payers apply their own medical policies, authorization rules, frequency limits and deadlines, which can differ from Medicare and from each other. Check the specific payer and plan policy for the date of service.

What are common pacemaker billing denials? Frequent categories include medical necessity, incorrect CPT or ICD-10-CM, modifier errors, NCCI and bundling, missing documentation, prior authorization, eligibility, frequency limits, duplicate claims, timely filing, global-period issues, provider enrollment and place of service.

How can cardiology practices reduce pacemaker claim denials? Verify eligibility and authorization before the procedure, code from the operative and device reports, apply modifiers only when supported, follow bundling and frequency rules, submit clean claims and track denials by root cause so recurring patterns get fixed upstream.

Key takeaways

• Pacemaker services span surgery, device clinic checks and remote monitoring, each with its own codes and rules.
• System implants (33206 to 33208) include the leads and generator; generator changes (33227 to 33229) already include removal.
• Interrogation, programming and remote monitoring are not interchangeable and remote codes carry frequency rules.
• Diagnosis coding follows the guidelines; device-management visits use Z45.01x, not the Z95.0 status code.
• Medicare covers implants under NCD 20.8.3 with the KX modifier; generator changes fall to local policy.
• Prior authorization is not universal and commercial rules vary by payer and plan.
• Track denials by root cause to convert one-off rework into prevention.

Accurate pacemaker billing comes down to matching the claim to what the record shows, honoring the coverage policy that applies to the payer and date of service and building a denial log that feeds prevention. This Pacemaker Billing Guide covers the structure, but the current AMA CPT descriptors, ICD-10-CM guidelines and CMS and payer policies are the authorities to verify before every submission.

SEO deliverables

SEO title: Pacemaker Billing Guide: CPT Codes, Coding & Denials

Meta description: A practical Pacemaker Billing Guide covering CPT codes, ICD-10-CM, documentation, prior authorization, Medicare rules, denials and reimbursement for cardiology billing teams.

URL slug: /pacemaker-billing-guide/

Primary keyword: Pacemaker Billing Guide

Secondary keywords: pacemaker billing, pacemaker coding, pacemaker CPT codes, pacemaker generator replacement billing, pacemaker interrogation billing, pacemaker programming billing, pacemaker remote monitoring billing, pacemaker implantation billing, pacemaker claim denials, pacemaker prior authorization, pacemaker Medicare billing, cardiac device billing, pacemaker documentation requirements, pacemaker reimbursement, pacemaker denial management

Search intent: Primary, informational. Secondary, commercial investigation (evaluating specialized cardiology billing support). Tertiary, service intent (practices seeking pacemaker and device billing help).

Internal linking recommendations

Authoritative external sources

• CMS, National Coverage Determination 20.8.3 (Cardiac Pacemakers) and associated Billing and Coding Articles (for example A54958, A54929). Medicare Coverage Database. Establishes covered indications, the 33206 to 33208 code list, KX attestation and covered diagnoses. Used to verify Medicare coverage and coding rules.
• CMS, Transmittal R3204CP (Medicare Claims Processing). Documents the KX modifier requirement for covered pacemaker implants and that MACs return claims as unprocessable without it, effective for dates of service on or after August 13, 2013.
• CMS, Prior Authorization for Certain Hospital Outpatient Department (OPD) Services. CMS.gov, list current through 2025 to 2026. Confirms the eight categories requiring OPD prior authorization and that pacemakers are not among them.
• AMA, CPT 2026 code set. Source for current CPT code numbers and descriptors for pacemaker procedures (33206 to 33275) and device evaluation and monitoring services (93279 to 93296). Descriptors were paraphrased; verify against the current edition.
• CMS and NCHS, ICD-10-CM 2026 (effective October 1, 2025). Source for Z95.0, Z45.010 and Z45.018, including the Excludes1 relationship that governs device-management coding.
• CMS, National Correct Coding Initiative (NCCI) Policy Manual and edits. Basis for bundling of imaging guidance and the inclusion of generator removal within generator-replacement codes.
• CMS, Medicare Physician Fee Schedule and Outpatient Prospective Payment System. Basis for the professional-versus-facility payment split and the 90-day global period referenced in the reimbursement discussion. No specific payment amounts were stated.