From Procedure Note to Paid Claim: A 2026 PCI Billing Workflow Guide (CPT 92920–92998)
Updated: Aug 23
A cath lab procedure note can be clinically perfect and still produce a denied or downcoded claim if the translation from documentation to CPT code breaks down anywhere along the way. That gap has gotten more consequential for 2026: CPT restructured the PCI code family, and a chargemaster or superbill still running last year's code set is a fast path to a denial. Our billing team at MedCloudMD built this guide around that translation process — not as another code dictionary, but as a workflow for turning a real PCI procedure note into a compliant, defensible 2026 claim.
Quick Answer: What Do CPT 92920–92998 Cover? This range covers percutaneous coronary intervention (PCI) and related coronary procedures — angioplasty, stenting, atherectomy, and chronic total occlusion (CTO) revascularization — plus adjunct services like intracoronary imaging and thrombectomy. For 2026, CPT restructured several PCI codes to fold typical additional-branch work into single-vessel base codes and introduced new codes for complex multi-lesion/bifurcation stenting and combined-approach CTO intervention. Confirm the current AMA CPT® descriptors and your specific code set before billing — this family saw genuine structural change for 2026, not just a minor update. |
What Changed in PCI Coding for 2026
Multiple coding sources describe a consistent structural shift: CPT revised the primary PCI base codes (the family generally including 92920, 92924, 92928, 92933, 92937, 92941, and 92943) so that typical additional-branch work within the same vessel is now included in the single base code, rather than requiring a separate branch add-on code. Alongside that restructuring, CPT introduced a new code for complex intracoronary stenting — covering two or more distinct lesions with two or more stents in one vessel, or a bifurcation lesion treated in both the main vessel and side branch — and a new code for CTO revascularization using combined antegrade and retrograde approaches.
Payer Alert Multiple industry sources report that legacy branch-vessel add-on codes were deleted for 2026 and folded into the revised base codes — but exact deleted code numbers vary across sources we reviewed, and this is exactly the kind of detail that changes fast after a CPT release. Before your practice bills a single 2026 claim in this family, confirm the current, final code set directly against the AMA CPT® 2026 codebook and your MAC's guidance, and purge any deleted codes from your EHR, chargemaster, and superbills. Billing a deleted code produces an automatic invalid-code denial, not a review — there's no partial credit for being close. |
The PCI Code Selection Path
Was coronary intervention actually performed, or only diagnostic angiography? → Which vessel(s) were treated? → What was done — angioplasty alone, stenting, atherectomy, or CTO revascularization? → Within that vessel, does the work meet the current base-code definition, or does it rise to the complex/multi-lesion code? → Was more than one vessel treated, and does documentation support each separately? → Does the procedure note support the code, not just the charge description? → Are any modifiers or payer-specific edits relevant?
Real-World Coding Scenarios
Scenario 1 — Angioplasty Without Stent
Balloon angioplasty is performed in one vessel with no stent placed. Coding path: this supports the base angioplasty code for that vessel — not a stent code, since none was placed. Billing risk: reflexively defaulting to a stent code because that's the more common procedure in the practice.
Scenario 2 — Coronary Stent Placement
A stent is placed in one lesion within one vessel. Coding path: the single-vessel stent base code applies; angioplasty performed as part of the same intervention in that vessel is not separately reported. Billing risk: unbundling by reporting both the angioplasty and stent codes for the same vessel in the same session.
Scenario 3 — Multivessel PCI
Stents are placed in two separate major coronary vessels in the same session. Coding path: each vessel is evaluated independently against the current code definitions and documentation — what's separately reportable depends on vessel count and current CPT/payer rules, not a fixed multiplier. Billing risk: assuming a second vessel automatically means a second full base code without confirming current guidance.
Scenario 4 — Complex Multi-Lesion Stenting
Two distinct lesions in the same vessel each receive a stent, or a bifurcation lesion is treated in both the main vessel and side branch. Coding path: this is the specific scenario the new 2026 complex-stenting code was created to capture — confirm the current descriptor and required documentation before using it. Billing risk: defaulting to the standard single-lesion stent code and undercoding genuinely complex work.
PCI Documentation Checklist
☐ Indication and diagnosis clearly stated
☐ Target vessel and lesion location specifically identified
☐ Lesion characteristics documented (e.g., bifurcation, CTO, multiple lesions)
☐ Procedure performed described precisely (angioplasty, stenting, atherectomy, CTO approach)
☐ Device/stent details recorded where relevant
☐ Pre- and post-procedure findings documented
☐ Complications, if any, noted
☐ Successful completion clearly stated
☐ Physician signature and final procedure report present
Diagnostic Catheterization + PCI: Same-Session Complexity
Whether a diagnostic angiogram is separately reportable alongside PCI in the same session depends on the specific clinical circumstances and current NCCI/payer guidance — it is not automatically billable just because both occurred. The pattern that tends to hold up under review: the diagnostic study was performed without a pre-existing plan to intervene, findings revealed a lesion warranting intervention, and the documentation explicitly connects the decision to proceed with PCI to those diagnostic findings. When the diagnostic study and the decision to intervene aren't clearly distinguished in the note, treat the diagnostic component as bundled into the PCI service.
Modifiers Relevant to PCI Claims
Modifier use always follows the documented procedure and current coding rules — never apply a modifier to work around a bundling edit or increase reimbursement.
How Medical Necessity Affects PCI Claims
The clinical record needs to connect diagnosis, symptoms, prior testing or imaging, and the specific intervention performed into one consistent story. Acute presentations (such as MI-related PCI) and elective interventions carry different documentation expectations — payer coverage policies for elective PCI in particular often expect evidence of ischemia or failed conservative management. A technically correct CPT code doesn't offset a chart that doesn't clearly support why the procedure was necessary.
PCI Reimbursement: Why It Varies
Actual payment depends on Medicare vs. Medicare Advantage vs. commercial vs. Medicaid status, facility vs. professional billing, contracted rates, geographic locality, place of service, and each payer's specific fee schedule and edits. We won't quote reimbursement figures here — published dollar estimates go stale fast and vary meaningfully by contract, so treat any number you see in an industry blog as a rough planning reference at best, not a guarantee.
Top PCI Denial Reasons
Denial Reason | Prevention |
Deleted 2025 code billed in 2026 | Purge outdated codes from EHR/chargemaster before Q1 claims go out |
Bundling/NCCI edit conflict | Check current edits before submission, especially diagnostic + PCI same-session claims |
Unsupported medical necessity | Confirm diagnosis-to-procedure linkage is explicit in the note |
Vessel misidentification | Cross-check vessel documentation against the billed code |
Incorrect modifier use | Validate modifier against actual documented circumstance |
Missing operative report detail | Require complete pre/post findings before coding |
Where PCI Practices Lose Revenue
• Missed separately-supportable services due to incomplete documentation
• Code selection driven by the charge description instead of the procedure note
• Failed or missing prior authorization on elective cases
• Denials worked individually without root-cause tracking
• Recurring claim-edit errors that never get fixed at the source
PCI Billing Workflow
Scheduling → Insurance Verification → Prior Authorization → Clinical Documentation → Charge Capture → Coding → Modifier Review → Claim Scrubbing → Submission → Payment Posting → Denial Management → AR Follow-Up → Reporting → Audit. Coding review — checking the procedure note against the billed code before submission — is the step most likely to catch a 2026 code-set error before it becomes a denial.
Pre-Submission PCI Claim Checklist
☐ Current 2026 CPT code confirmed against the AMA codebook
☐ No deleted 2025 codes present on the claim
☐ Documentation supports the specific procedure billed
☐ Diagnosis supports medical necessity
☐ Vessel(s) documented correctly and consistently
☐ Modifiers validated against documentation
☐ NCCI edits reviewed for same-session services
☐ Authorization confirmed where required
10 PCI Billing Mistakes We See Most Often
Mistake | Fix |
Billing a deleted 2025 code | Update chargemaster and superbills before Q1 claims |
Coding from the charge ticket instead of the procedure note | Code from the operative report every time |
Reporting angioplasty and stent codes for the same vessel | Stent codes include angioplasty in the same vessel |
Assuming diagnostic cath is always separately billable with PCI | Confirm the decision-to-intervene documentation supports it |
Applying modifiers automatically | Validate against the actual documented circumstance |
Repeating the same denial without root-cause review | Track denials by code and payer, not just claim-by-claim |
Medicare vs. Commercial PCI Billing
Area | Medicare | Commercial Payers |
Coding guidance | CMS/MAC guidance plus current CPT rules | May reference CPT but apply payer-specific medical policy |
Prior authorization | Varies by service and MAC | Often required for elective PCI — confirm per payer |
NCCI/bundling edits | CMS NCCI edits apply directly | Many commercial payers adopt similar logic, but verify |
When Should a Cardiology Practice Consider Outsourcing PCI Billing?
• Persistent coding denials tied to the 2026 code changes specifically
• Growing claim volume outpacing internal coding review capacity
• Aging AR on high-dollar PCI claims without clear root-cause tracking
• Difficulty keeping payer-specific PCI policy current across multiple contracts
How MedCloudMD Supports Cardiology Practices
Our billing specialists review PCI coding against the procedure note, track denial patterns by code and payer, and follow up on AR so preventable revenue doesn't sit unresolved. We don't guarantee reimbursement outcomes — what we can do is make sure your 2026 PCI claims reflect current coding rules and the actual documented procedure.
Frequently Asked Questions
What are CPT codes 92920–92998 used for?
Percutaneous coronary intervention (PCI) and related coronary procedures angioplasty, stenting, atherectomy, CTO revascularization, and adjunct services.
What changed in PCI CPT coding in 2026?
CPT restructured primary PCI base codes to include typical additional-branch work and introduced new codes for complex multi-lesion/bifurcation stenting and combined-approach CTO intervention.
Which PCI codes were deleted in 2026?
Multiple industry sources point to legacy branch-vessel add-on codes being deleted and folded into base codes — confirm the exact final list against the current AMA CPT® codebook before billing.
What documentation is required for PCI billing?
Clear indication, target vessel and lesion detail, procedure performed, device/stent detail where relevant, findings, and a signed final procedure report.
What are the most common PCI billing denials?
Deleted/outdated codes, bundling conflicts, unsupported medical necessity, vessel misidentification, and modifier errors.
How does Medicare handle PCI claims?
Through CMS/MAC guidance and NCCI edits alongside current CPT rules — requirements can still differ by MAC and service.
When should a cardiology practice consider outsourcing PCI billing?
When 2026 code-set confusion, denial volume, or aging AR outpace internal specialty coding capacity.
Disclaimer
This content is provided for educational and informational purposes only and should not be considered legal, coding, reimbursement, or medical advice. Billing regulations, CPT® coding, CMS policies, NCCI edits, and payer requirements may change over time and can vary by payer, contract, facility, and location. Healthcare providers should verify current coding guidelines and reimbursement policies with CMS, the AMA CPT® resources, the appropriate payer, applicable NCCI guidance, or qualified coding professionals before submitting claims. MedCloudMD provides professional medical billing and revenue cycle management services to support healthcare organizations but does not guarantee reimbursement outcomes.
Comments