CPT® Code 20680

Last Updated: January 2026 | Verified for 2026 AMA, CPT & CMS Guidelines

Quick Reference:

• What CPT 20680 means: CPT 20680 reports the surgical removal of a deep implant (for example, a buried wire, pin, screw, nail, rod, or plate) when the implant is sufficiently deep that removal typically requires incision and layered dissection rather than simple superficial extraction. The key coding distinction is depth: 20680 is used when hardware is under deeper soft tissue planes and requires operative exposure consistent with “deep” removal.
• Major procedure under Medicare global surgery rules: Under Medicare’s global surgery framework, procedures designated “major surgery” are those assigned 090 global days in the Medicare Physician Fee Schedule database/relative value files. CMS instructs providers to apply global surgery billing rules (including postoperative package concepts and modifier logic for separate procedures during the global). The authoritative operational reference is the CMS MLN booklet on global surgery.
• Bundling is the dominant compliance risk: CMS NCCI policy is explicit that removal of implants (including 20670 and 20680) is not separately reportable when performed as a necessary, integral component of another procedure (for example, revision fracture repair for nonunion/malunion that requires removal of previously inserted hardware). If implant removal is required to complete the primary procedure, the removal is packaged into the primary code.
• Not reportable for wire suture removal in certain re-operations: CMS NCCI policy also states that removal of wire sutures during certain cardiac reoperation or sternal procedures is not separately reportable with 20670/20680. This is a common denial/audit pattern when claims attempt to separately report removal that CMS considers integral to the reoperation.
• One unit per anatomic site is the default expectation: CMS NCCI policy explains that the descriptors for 20670/20680 do not define a unit of service, and CMS policy allows one unit of service per anatomic site for implant removal reporting under the NCCI framework. A second unit is only defensible when implants are removed from a distinct anatomic site, and documentation must make that distinctness clear. The Medicaid NCCI manual contains parallel unit-of-service guidance.
• When multiple sites are removed on the same date: If deep implant removal is performed on separate anatomic sites during the same operative session, the claim must clearly distinguish sites (and, where payer rules require, use an appropriate distinctness modifier such as 59 or a more specific X-modifier). The underlying compliance requirement is not the modifier itself; it is the medical record proof that two separate anatomic sites were treated.
• Documentation must prove depth, site, and necessity: Operative documentation must support (1) the reason for removal (pain, mechanical failure, infection concern, prominent or symptomatic hardware, etc.), (2) that the implant was deep (operative exposure beyond superficial tissue), (3) the exact implants removed and their location, and (4) whether removal was complete or partial. Where removal occurs during a global period, documentation must also support the modifier rationale under global surgery rules.
• Payer policy variation is real (authorization and benefit design): Even when coding is correct, payment may depend on plan prior authorization and site-of-service rules. Examples of plan-specific tools include Central California Alliance’s procedure code lookup, Superior HealthPlan’s Medicaid effective code list, and UnitedHealthcare Community Plan Florida’s prior authorization list. These documents can change and should be checked for the member’s plan and date of service. CPT 20680 is straightforward in concept—remove symptomatic deep orthopedic hardware—but it is frequently denied or recouped for reasons unrelated to surgical technique.

The practical reimbursement risks cluster into four categories:

• bundling (billing 20680 when removal was integral to another billed procedure),
• unit-of-service errors (billing multiple units for multiple screws/plates in the same anatomic site),
• global surgery misapplication (incorrect use of staged/related/unrelated logic during a postoperative period), and
• documentation gaps (failure to prove depth, site, or medical necessity). This 2026-focused guide uses CMS global surgery guidance and CMS NCCI policy as the primary compliance anchors, and it highlights payer authorization variability as an operational constraint rather than a substitute for correct coding.

1. Clinical Definition and Code Intent

CPT 20680 is used to report the operative removal of a deep implant. “Deep” is not a billing synonym for “a lot of screws” or “took a long time.”

In coding terms, the claim must be able to withstand a post-payment reviewer asking a simple question: did the procedure require operative exposure consistent with a deep implant removal rather than a superficial extraction?

In practice, deep implant removal typically requires an incision and dissection sufficient to reach hardware under deeper tissue planes, with controlled exposure, removal of one or more implanted components, hemostasis, and layered closure.

The most important practical distinction is between:

• 20680 (deep implant removal): Removal of hardware that is buried and requires operative exposure consistent with deep dissection and access to the implant.
• 20670 (superficial implant removal): Removal of implants considered superficial, often closer to subcutaneous planes and not requiring deeper operative exposure (reportable under its own descriptor; selection is driven by actual depth/approach, not by implant type alone). Compliance boundary: A payer does not need to “disagree with your clinical decision” to deny 20680. If the operative record does not prove deep removal (depth, exposure, site), the denial can be framed as insufficient documentation or incorrect code selection. Your operative note is the primary defense.

2. Global Surgery Rules: What “90 Days” Actually Means Operationally

Under Medicare, global surgery is a payment package concept: Medicare payment for many procedures includes the procedure itself plus the typical related pre- and post-operative services furnished within the assigned global period. CMS explains global surgery concepts and billing requirements in the MLN Global Surgery booklet, including how Medicare classifies procedures into 0-, 10-, and 90-day global periods, and how postoperative care is packaged.

For major surgeries (090 global days), global surgery rules affect how you bill additional services furnished during the postoperative period, including whether a second procedure is treated as:

• Part of the original package (not separately payable because it is routine follow-up or integral care),
• A staged or planned procedure (separately reportable with the correct global modifier logic when applicable),
• An unplanned return to the operating room for a related problem (separately reportable under the “return to OR” concept when criteria are met), or
• An unrelated procedure (separately reportable if the record proves unrelatedness). CMS emphasizes that global surgery rules apply across settings (hospital inpatient, outpatient, ASC, office) and that providers in the same group and specialty bill as though they are one physician for global surgery purposes.

Operationally, when implant removal occurs during a postoperative period, the clinical record must answer:

• Was implant removal planned as part of the original treatment plan? If yes, that is staged logic under global rules.
• Was implant removal required due to a related complication or failure? If yes, it may fit “return to OR for related procedure” logic depending on circumstances and documentation.
• Was implant removal unrelated to the original procedure? If yes, the record must demonstrate unrelated medical necessity and distinctness. CMS provides the Medicare Physician Fee Schedule search/overview as an entry point to the PFS tool and associated documentation and files that include global surgery indicators for procedure codes. In Medicare operations, the global-day indicator is an attribute of the code in the PFS database and is a foundational input to correct modifier and postoperative billing logic.

3. CMS NCCI Bundling: When 20680 Is Not Separately Reportable

The single most important policy anchor for CPT 20680 reimbursement risk is the CMS National Correct Coding Initiative (NCCI) Policy Manual.

NCCI policy addresses when certain procedures are considered integral components of other procedures and therefore not separately reportable, even if they are performed.

In the Medicare NCCI Policy Manual, Chapter 4, CMS explicitly discusses implant removal codes 20670 and 20680.

3.1 “Integral to another procedure” principle

CMS states that removal of internal fixation devices (including 20670/20680) is not separately reportable if the removal is performed as a necessary integral component of another procedure.

The manual provides an example: if a revision of an open fracture repair for nonunion or malunion requires removal of a previously inserted pin, 20670 or 20680 is not separately reportable.

Practical interpretation:

• If the primary billed procedure requires exposure and removal of prior hardware to complete the definitive work (revision fixation, osteotomy, reconstruction), CMS expects the removal work to be included in the primary code.
• Separately billing 20680 in this setting is commonly interpreted as unbundling.

3.2 Removal of wire sutures in specified contexts

CMS further states that 20670/20680 shall not be reported for removal of wire sutures during cardiac reoperation procedures or sternal procedures (including debridement, resection, closure of median sternotomy separation). This is relevant because claims sometimes attempt to treat wire removal as a separately billable “implant removal.” CMS policy rejects that interpretation in the specified contexts.

3.3 Debridement performed in the same surgical field

Another repeated orthopedic billing pitfall is reporting debridement codes (for example 11042/11045 or other debridement families) in addition to a musculoskeletal procedure when the debridement is simply part of exposure or cleanup in the same operative field.

CMS NCCI policy states that debridement of tissue in the surgical field of another musculoskeletal procedure is not separately reportable, with a limited exception for debridement at the site of an open fracture/dislocation using specific open-fracture debridement codes.

High-yield denial prevention rule: If the operative note reads like implant removal was performed to allow the surgeon to complete a more comprehensive primary procedure, do not expect 20680 to be separately payable under CMS NCCI policy—even if the removal was technically challenging.

4. Units of Service and Multiple Sites: Preventing Overbilling

Implant removal is commonly miscoded as a “per implant” service (for example, one unit per screw, one unit per plate, one unit per incision).

CMS NCCI policy explains why that approach fails: the descriptors for 20670 and 20680 do not define a unit of service, and CMS policy allows one unit of these codes for implant removal in a single anatomic site under NCCI logic, with additional units only when implants are removed from a distinct site.

The Medicaid NCCI policy manual mirrors this concept: it describes unit-of-service concerns and emphasizes that correct unit reporting matters because coding units of service incorrectly is a source of improper billing. It also references the Medicare Physician Fee Schedule database/relative value file as the source for global day designations used by the program.

4.1 What counts as “one site” in practice

CMS policy does not provide a universally perfect anatomical map in the implant-removal paragraph, so “site” is operationally proven through documentation:

• Document the anatomic region precisely: e.g., “left distal radius volar plate,” “right tibial shaft intramedullary nail with proximal and distal locking screws,” “left lateral malleolus plate.”
• Document laterality and level: laterality alone is often insufficient; include the bone and segment/level.
• Document separate operative fields when billing multiple units: If two distinct sites are treated on the same date, the record should make the distinctness obvious without inference.

4.2 Multiple 20680 codes on the same date

If hardware is removed from two distinct sites during one operative session (for example, hardware from the tibia and hardware from the femur), reporting multiple implant-removal codes may be appropriate depending on payer rules and claim structure.

However, compliance depends on two things:

• NCCI consistency: each additional unit must represent a distinct site consistent with CMS policy.
• Record clarity: the operative note must clearly distinguish sites, hardware, and exposure so the second unit is defensible on chart review.

5. Documentation Standards: What Auditors and Payers Look For

Documentation is not a cosmetic requirement for 20680; it is the difference between a payable claim and a recoupment.

CMS global surgery guidance and CMS NCCI policy together imply the minimum necessary record structure: the chart must prove the service was (a) medically necessary, (b) correctly coded as deep removal, (c) not bundled into another procedure, and (d) billed with correct global/modifier logic when applicable.

5.1 Minimum operative note elements for CPT 20680

• Indication/medical necessity: document why removal was necessary (symptomatic pain attributable to hardware, mechanical failure, loosening, prominent hardware with functional limitation, suspected infection scenario when clinically relevant, or other documented complication/clinical rationale).
• Confirmation of status of underlying condition: for post-fracture hardware, record healing/union status (often radiographic) when removal is performed because the fracture is healed and the hardware is now symptomatic or no longer needed.
• Depth and surgical approach: describe incision location and depth of dissection and exposure required to reach the implant (for example, dissection to fascia and deeper planes, exposure to hardware, removal steps, layered closure).
• Implant inventory detail: specify what was removed (implant type and count where useful for clarity) and where it was removed from. “Removed hardware” without identification is a common weakness.
• Completeness: document whether removal was complete or partial and why (for example, broken screw fragments left in situ for safety, or partial removal because only symptomatic components were removed).
• Relationship to other procedures: if another procedure was performed at the same time, explicitly document whether implant removal was required to complete that procedure (which strongly suggests bundling under NCCI) or whether it was a distinct, separately necessary service.

5.2 When global modifiers become documentation problems

When implant removal occurs during a postoperative period for a previous procedure, global surgery rules determine whether separate payment may apply and which modifier framework is relevant.

CMS’s MLN booklet is the baseline operational reference for the global package concept and billing requirements. In practice, you should document why the second procedure was staged/planned, related/unplanned, or unrelated, because the payer’s adjudication depends on this classification.

Audit-proofing principle: The most defensible operative note reads as though the surgeon expects a third-party reviewer to reconstruct (1) the reason for removal, (2) why the implant was “deep,” (3) why the removal is not bundled, and (4) why any postoperative billing logic (if relevant) is correct.

6. Comparison Table: 20680 vs 20670 vs Debridement Codes

7. Medicare and Payer Policy: Coverage vs Authorization Reality

For Medicare, the core compliance rules for implant removal claims flow from CMS global surgery policy (packaging rules during postoperative periods) and CMS NCCI bundling policy (integral services not separately reportable). These frameworks determine whether the service is separately billable and how it should be coded when performed alongside other procedures.

However, reimbursement in day-to-day operations is also constrained by payer-specific authorization and utilization management rules—especially for Medicaid managed care and commercial plans.

The correct approach is to treat payer tools as operational requirements (authorization, site rules) while using CMS policy as the coding integrity baseline.

7.1 Examples of payer operational tools (illustrative)

• Central California Alliance (Medi-Cal plan): Provides a procedure code lookup tool intended to determine whether a procedure code requires prior authorization and related billing constraints. This is plan-specific operational guidance and may change; confirm by date of service and member eligibility.
• Superior HealthPlan (Texas Medicaid managed care): Publishes a Medicaid effective codes list for prior authorization requirements. Use plan documents as the operational source of truth for PA requirements for that plan.
• UnitedHealthcare Community Plan Florida (Medicaid): Publishes a Florida Medicaid prior authorization requirements list. The presence of a code in a PA list does not change CPT coding rules, but it can determine whether payment will be denied for lack of authorization. Do not confuse authorization with coding correctness: A prior authorization approval does not cure a bundling error, and correct coding does not override a plan’s PA requirement. Treat these as separate controls.

8. Real-World Clinical Scenarios

Scenario 1: Symptomatic plate removal after healed fracture

Setting: Outpatient hospital or ASC.

Clinical story: Patient has a healed fracture and persistent focal pain attributable to a plate and screws. Imaging supports union. Surgeon performs operative exposure and removes the plate and multiple screws through deep dissection and layered closure.

Coding logic: CPT 20680 is appropriate when documentation supports deep operative exposure and removal. The claim should reflect one unit for the anatomic site consistent with CMS unit-of-service expectations, unless a second distinct anatomic site is clearly documented.

Documentation tip: Make the record prove depth (exposure planes), specify implants removed, and include the indication (symptoms and why removal is medically reasonable).

Scenario 2: Removal performed because it is necessary to complete a revision repair

Setting: Inpatient or outpatient revision orthopedic surgery.

Clinical story: Patient undergoes revision fracture repair for nonunion/malunion. Prior hardware must be removed to allow the revision fixation/reconstruction.

Coding logic: Under CMS NCCI policy, implant removal (20670/20680) is not separately reportable when it is an integral component of the revision procedure. Billing 20680 in addition to the revision procedure is a classic unbundling pattern.

Documentation tip: If removal is integral, document it as part of the primary procedure narrative; do not attempt to transform integral removal into a separately billed service without a defensible, distinct operative indication and field.

Scenario 3: Two distinct anatomic sites on the same date

Setting: Single operative session, multiple sites.

Clinical story: Surgeon removes symptomatic deep hardware from the left tibia and also removes symptomatic deep hardware from the left femur during the same operative encounter.

Coding logic: Reporting implant removal for distinct anatomic sites can be appropriate when documentation clearly distinguishes sites and hardware. CMS policy emphasizes one unit per anatomic site and allows additional units when a distinct site is involved. Claims typically need site-specific documentation and, depending on payer rules, an appropriate distinctness modifier on the additional line.

Documentation tip: Use separate headings in the op note (e.g., “Left tibia hardware removal,” “Left femur hardware removal”), with distinct incision, exposure, and implant details for each.

Scenario 4: Debridement performed in the same surgical field as implant removal

Setting: Implant removal with routine wound/field cleanup.

Clinical story: During deep implant removal, the surgeon performs debridement of superficial or deeper tissue in the same operative field as part of exposure and cleanup.

Coding logic: CMS NCCI policy generally does not allow separate reporting of debridement codes when performed in the surgical field of another musculoskeletal procedure; routine debridement associated with exposure/cleanup is considered included.

Documentation tip: If debridement is truly distinct (different site/field and meets criteria for separately reportable debridement), document the separate site and medical necessity explicitly; otherwise, avoid overcoding.