Glossary · Coding

Code pair

A code pair is two CPT codes that CMS's National Correct Coding Initiative (NCCI) has determined should not ordinarily be billed together on the same claim, because one service is considered a component of—or overlaps with—the other. Submitting both codes without a valid modifier typically results in automatic claim denial or bundling.

Verified May 8, 2026 · 5 sources ↓

Drawn from CMSAAOSAoassnCme

Definition

Source · Editorial summary grounded in 5 cited references ↓

Under the NCCI Procedure-to-Procedure (PTP) edit system, CMS maintains a table of code pair edits that flag combinations of CPT codes deemed mutually exclusive or inherently bundled. When two codes in the table are submitted together for the same patient, same date of service, and same provider, the payer automatically adjudicates only the 'column 1' (higher-valued) code and rejects the 'column 2' (component) code. The edit reflects the clinical judgment that the work described by the column 2 code is already captured in the reimbursement for the column 1 code.

Each PTP code pair carries a Correct Coding Modifier Indicator (CCMI): a value of '1' means an NCCI-associated modifier (most commonly Modifier 59 or an X-modifier) may legitimately bypass the edit when the two procedures were genuinely distinct—different anatomic sites, separate encounters, or independently indicated services. A CCMI of '0' means the edit is absolute; no modifier can override it because the two codes are considered mutually exclusive by definition.

In orthopedic surgery, code pair edits are especially dense in the musculoskeletal CPT range (20000–29999). A surgeon performing multiple arthroscopic procedures on the same shoulder in the same session, for example, must know which combinations are bundled and whether a Modifier 59 or an X-modifier is appropriate—and whether adequate documentation exists to justify it. The AAOS Code-X tool and the CMS NCCI PTP Coding Edits database are the primary references for looking up current pair edits and their modifier indicators.

Why it matters

Ignoring code pair edits is one of the most audited billing patterns in orthopedics. If both codes in an unbundlable pair are submitted without proper justification, the claim is either auto-denied or, worse, paid in error and later recouped during a RAC or OIG audit—potentially triggering overpayment demands, interest, and compliance scrutiny. Conversely, failing to apply a valid modifier when the procedures truly were distinct leaves legitimate reimbursement on the table. Understanding which pairs have a CCMI of '1' versus '0' is the difference between appropriate unbundling and improper billing.

Common mistakes

Where people most often go wrong with this concept.

Source · Editorial brief grounded in cited references ↓

Applying Modifier 59 to a code pair with a CCMI of '0' (absolute edit), which provides no billing benefit and signals a compliance risk.
Billing the column 2 code alone without recognizing it is already bundled into the column 1 code's reimbursement, resulting in duplicate work attribution.
Using Modifier 59 as a blanket bypass without documentation demonstrating the services were distinct in site, session, or indication—documentation that must exist before the claim is submitted, not after an audit.
Failing to list the highest-RVU procedure in the primary (column 1) position, which can trigger edit flags even when the combination is otherwise billable.
Confusing MUE (Medically Unlikely Edit) limits with PTP code pair edits—these are separate NCCI mechanisms with different bypass rules.
Not checking updated NCCI tables quarterly; CMS revises code pair edits each quarter, and a pair that was separately billable in one quarter may be bundled in the next.

Related codes

Codes commonly involved when this concept appears in practice.

CPT

Modifiers

59 Distinct procedural service XS Separate structure RT Right side LT Left side

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 5 cited references ↓

01What is the difference between a code pair edit and a bundling rule?

Bundling is the broader concept—one code's payment includes the work of another. A code pair edit is the specific NCCI mechanism that enforces bundling by flagging two CPT codes that CMS has determined overlap. Not all bundling situations appear in the NCCI PTP table; some are governed by CPT coding guidelines or the global surgical package rules instead.

02Can Modifier 59 always override a code pair edit?

No. A modifier can only bypass a code pair edit when the Correct Coding Modifier Indicator (CCMI) for that pair is '1'. When the CCMI is '0', the edit is absolute and no modifier—including Modifier 59 or any X-modifier—will cause the payer to reimburse both codes. Submitting a modifier against a '0' edit does not change the outcome and may attract audit attention.

03Where can I look up current NCCI code pair edits for orthopedic procedures?

The CMS NCCI PTP Coding Edits table is publicly available on the CMS website and is updated quarterly. The AAOS Code-X tool also incorporates current NCCI edit information specific to musculoskeletal CPT codes and is the resource most commonly used by orthopedic coders and surgeons.

04How often do code pair edits change?

CMS updates the NCCI PTP edit tables four times per year (quarterly). New pairs can be added, existing pairs can be deleted, and CCMI values can change. Practices should verify their common code combinations against the current quarter's table, especially after major CPT code updates at the start of each calendar year.

05In orthopedic shoulder arthroscopy, which code pairs are commonly flagged?

CMS's NCCI policy manual specifies that most pairs of CPT codes describing two procedures on the ipsilateral shoulder cannot be bypassed with a modifier when performed through the same surgical approach. Common flagged pairs include rotator cuff repair (29827) billed with distal clavicle excision (29824) or biceps tenodesis (29828). Whether a modifier applies depends on the specific pair's CCMI and on documentation supporting anatomic or procedural distinctness.

Sources & references

Editorial content was developed using the following public sources. Last verified May 8, 2026.

Mira AI Scribe

Mira's coding layer checks every CPT combination generated from the operative note against the current NCCI PTP edit table before the claim is finalized. When a code pair edit is detected, Mira flags the column 2 code and surfaces the CCMI value. If the CCMI is '1' and the operative documentation supports a distinct service—separate anatomic site, separate incision, or independently indicated procedure—Mira prompts the coder to confirm and, if appropriate, appends the most specific X-modifier (XS for separate structure, XE for separate encounter, etc.) rather than defaulting to the generic Modifier 59. If the CCMI is '0', Mira blocks the pair and alerts the coder that no modifier can override the edit, preventing a claim submission that would fail or trigger a compliance flag. All modifier suggestions are held pending coder or surgeon confirmation; Mira does not auto-append modifiers without human review.

See Mira's approach

The National Correct Coding Initiative (NCCI) is a CMS program of automated prepayment edits that prevent Medicare and Medicaid from paying for procedure code combinations that are incorrectly billed together or billed in quantities that exceed what is clinically reasonable.

Bundling Coding

Bundling is the payer rule that treats two or more CPT codes as a single reimbursable unit, paying only the primary code when the secondary procedure is considered an inherent or integral part of it. Billing the bundled codes separately without proper justification constitutes unbundling, a compliance violation.

MUE (Medically Unlikely Edit) Coding

An MUE (Medically Unlikely Edit) is a CMS-established cap on the maximum units of service (UOS) that Medicare will reimburse for a given HCPCS/CPT code billed by the same provider for the same patient on the same date of service. Claims exceeding the MUE value are automatically denied at the line level.