CPT code 26040 – Percutaneous palmar fasciotomy

Key takeaways

CPT code 26040 reports a percutaneous (needle) palmar fasciotomy for Dupuytren’s contracture, so the operative note must document the needle approach.

Report it once per hand per session, however many cords are released, with modifier 50 or RT and LT when both hands are treated.

M72.0 (palmar fascial fibromatosis) is the standard diagnosis pairing, and it has no laterality, so the note and modifier carry the hand.

Under the 2026 Medicare fee schedule, the work RVU is 3.37 and the total is 9.24 in both settings, with a 90-day global period.

Pabau pre-fills the claim from the patient record, checks required fields before it’s sent and submits US claims through Claim.MD.

CPT code 26040 covers the needle release of a Dupuytren’s cord

CPT code 26040 reports a percutaneous palmar fasciotomy, where the surgeon divides a Dupuytren’s cord with a needle through the skin. Under AMA’s CPT Assistant guidance, it is reported only once per hand per session, and each cord release is not reported separately.

Three details decide whether the claim holds up. The note names the needle approach, M72.0 sits on the claim, and post-op visits stay inside the 90-day global period.

Because no tissue is removed, this is a fasciotomy rather than a fasciectomy. That single distinction drives most of the code choices further down the page.

What the surgeon does, and what the note has to show

Knowing the technique helps you read an operative note quickly. The surgeon passes a hypodermic needle through the skin. The bevel then perforates and divides the contracted cord at several points along its length.

• Anesthesia: Local, usually a lidocaine field or digital block.
• Setting: Usually the office or a minor procedure room rather than a hospital OR.
• Target tissue: The diseased cord, not the whole palmar fascia.
• Skin: Needle punctures only, with no incision and no sutures.
• Endpoint: Less flexion at the MCP or PIP joint, confirmed by passive extension at the end.

A note that describes an incision, soft tissue retraction or direct visualization of the cord describes an open approach. Query the surgeon or code 26045, never 26040.

26040 vs 26045 comes down to the incision

CPT 26045 is the open, partial palmar fasciotomy. The surgeon makes a skin incision and divides the fascia under direct vision. The two codes aren’t interchangeable, so the approach in the note settles it.

Scan the note for “needle” or “percutaneous” first. If it describes a scalpel incision and wound closure instead, 26045 applies. Billing 26045 for a needle release is upcoding, and billing 26040 for an open release is undercoding. Both show up on audit.

A removed cord means fasciectomy, not 26040

CPT 26040 divides the cord, while the fasciectomy codes remove it. CPT 26121 is a palmar fasciectomy, palm only, with or without Z-plasty, other local tissue rearrangement or skin grafting. CPT 26123 is a partial palmar fasciectomy with release of a single digit, PIP joint included.

If the note says the cord was “excised” anywhere, 26040 is the wrong code. Payers compare the billed code with the note’s wording, and excision language on a fasciotomy claim is a known mismatch pattern.

Neighboring codes split on approach and on what happens to the cord

Most coding errors on Dupuytren’s claims come from picking the wrong neighbor. The table below matches the note’s wording to the code it supports.

Collagenase treatment is coded separately as 20527 for the injection, with 26341 for the later cord manipulation. Two other hand codes look similar but treat different tissue. CPT 26055 is a tendon sheath incision for trigger finger, and 26060 is a percutaneous tenotomy of a single digit.

M72.0 is the diagnosis that supports 26040

M72.0, palmar fascial fibromatosis (Dupuytren), is the standard ICD-10-CM pairing for CPT 26040. The code carries no laterality, so record which hand was treated in the note and add RT or LT on the claim line.

The diagnosis must be active and documented at the date of service. A chart note with the contracture angle at the MCP or PIP joint backs up medical necessity, and auditors often ask for it. The CMS ICD-10 coding resources carry the current code set.

Medicare pays the same 9.24 RVUs in either setting

CMS sets 26040’s rate through the Medicare Physician Fee Schedule. Under the 2026 schedule, the work RVU is 3.37 and the total is 9.24, identical in the office and the facility.

If you need a refresher on what an RVU is, the three components below add up to that total.

The payment figure multiplies 9.24 by the 2026 conversion factor of $33.4009, before geographic adjustment. FastRVU’s 26040 page shows the breakdown, and the CMS fee schedule lookup gives your locality’s rate. Commercial contracts usually pay a percentage of Medicare, so check yours each January when rates reset.

The 90-day global period bundles routine follow-up

CMS assigns 26040 a 90-day global surgery period. The payment already covers routine post-op care for 90 days after the procedure. Billing a separate E/M visit in that window without a recognized exception is a bundling error.

Bundled, not billed separately:

• Routine post-op office visits within 90 days
• Dressing changes and wound checks
• Splinting applied at the time of the procedure

Separately billable, with documentation:

• An E/M visit for a new, unrelated problem, with modifier 24
• A planned, staged or more extensive procedure in the global period, such as a later fasciectomy, with modifier 58
• An unrelated procedure by the same surgeon in the global period, with modifier 79

A repeat needle release on the same hand isn’t a new unit per digit. The once-per-hand rule still applies, and modifier 58 only fits a return that was planned, staged or more extensive.

Modifiers on 26040 are about hands, not fingers

Because 26040 is a per-hand code, the modifier questions are mostly about laterality and bilateral work. Get those right and most modifier denials disappear.

Several cords on one hand still mean one unit of 26040

Dupuytren’s often affects more than one digit. Even so, releasing two or three cords on the same hand in one session is still a single 26040. CPT Assistant is explicit that each cord release isn’t reported separately.

Here’s how that looks on a claim. A surgeon releases cords to the right ring and small fingers in the office, then treats a cord in the left palm. Code it as one line of 26040-50, or two lines with RT and LT, depending on the payer. Each line carries M72.0 and one unit.

The note should still name every digit, cord location and the correction achieved. That detail supports medical necessity, even though it doesn’t add units. See the denial codes reference for the CARC codes that come back on hand surgery claims.

Prior authorization depends on the plan, not on Medicare

Traditional Medicare doesn’t routinely require prior authorization for 26040. Medicare Advantage and commercial plans often do, and their criteria differ enough to check each plan before you schedule.

Commercial policies commonly look for the evidence below. Treat it as a starting point and confirm each plan’s policy before you submit.

• A measured flexion contracture, often 30 degrees or more at the MCP joint, or any PIP contracture that limits function
• Notes on functional limitation, such as trouble placing the hand flat
• Clinical photographs of the cord and contracture, where the plan asks for them
• A plan naming the percutaneous approach and the digits to be treated

Check your MAC’s local coverage determinations and billing articles as well, since they can add criteria. Build a prior-auth check into your insurance eligibility verification step for every Dupuytren’s case on a Medicare Advantage or commercial plan.

Documentation that supports a 26040 claim

Weak documentation causes most audit findings on 26040. The operative note should contain each element below to support both the code and medical necessity.

• Approach: The word “percutaneous” or “needle” in the procedure description.
• Digits and cords: Each digit treated and the cord location, such as “pretendinous cord, right ring finger.”
• Before: The measured flexion angle at the MCP and PIP joints.
• After: The passive extension achieved once the cord was released.
• Anesthesia: Local anesthesia, consistent with a needle procedure.
• Changes of plan: Any finding that changed the approach, coded to match.

A note that mentions an “incision” and “wound closure” contradicts a 26040 claim, whatever code went out. A clinical reviewer looks for that first. The basics of medical billing explain how note quality carries through to clean-claim rates.

How a 26040 claim moves from note to payment

Most denials on this code start long before the payer sees it. This is the usual path, and where it tends to break.

1. Scheduling. The front desk checks eligibility and whether the plan needs prior authorization. A missed auth here is hard to fix later.
2. Procedure and note. The surgeon documents the needle approach, digits, cords and angles on the day.
3. Coding. The coder reads the note, assigns one 26040 per hand with RT, LT or 50, and links M72.0.
4. Charge entry. The 90-day global window starts, so follow-up visits are booked as no-charge post-op care.
5. Submission and remittance. The 837P goes out through the clearinghouse, and the ERA shows what was paid or denied.

Before you submit, check that:

• The note says “needle” or “percutaneous” and never “excised”
• There is one unit per hand, whatever the number of cords
• RT, LT or 50 matches the hands in the note and the payer’s format
• M72.0 is active and linked to the line
• Any required authorization number is on the claim

Six denial reasons on 26040, and how to prevent each one

Denials on 26040 cluster around six predictable causes. Each one has a fix you can make before the claim goes out.

When a denial does come back, work it from the remittance code rather than resubmitting as-is. The denial management in healthcare guide covers appeal workflows and the documentation that resolves each cause.

How Pabau keeps 26040 claims clean before they go out

In many hand surgery practices, the coder re-keys the procedure, diagnosis and modifiers from the note into a separate billing system. Each re-keyed field is another chance for a wrong unit or a missing authorization number.

Pabau’s claims management software pre-fills the claim from the patient record, so the 26040 charge and M72.0 land on the form already. Built-in CPT and ICD-10 lookup libraries help coders confirm each code, and the claim can’t be sent until required fields are complete.

For US practices, claims go out as 837P files through Claim.MD, with real-time eligibility checks and ERA posting. Your team sees each claim’s status, so a rejection gets corrected the same week instead of sitting in a queue.

Send hand surgery claims with fewer errors

Pabau pre-fills each claim from the patient record and checks required fields before it’s sent. US claims go out through Claim.MD with eligibility checks and ERA posting.

Book a demo

Conclusion

Billing 26040 well comes down to two habits. Read the note for “needle” or “percutaneous” before you pick a code, and bill one unit per hand however many cords were released.

Get those right and the remaining risks are routine ones. A missing authorization or a post-op visit billed inside the 90 days can be caught at the front desk and at charge entry.

Book a demo to see how Pabau pre-fills hand surgery claims from the record and sends them through Claim.MD.

Continue your research

Need a clearinghouse that submits claims and posts remittances? Claim.MD clearinghouse overview explains how 837P transmission, ERA posting and payer enrollment work for US practices.

Trying to reduce your denial rate across surgical codes? Denial management in healthcare covers appeal workflows, CARC code interpretation and the fixes that prevent repeat denials.

Looking for a checklist of what a clean claim needs? Clean claim requirements outlines the data elements an 837P file needs for first-pass acceptance.

Scheduling Dupuytren’s cases on commercial plans? The prior authorization process walks through a five-step request workflow, with a checklist and a log for open requests.

Frequently asked questions