Glossary · Coding
NCCI modifier indicator
The NCCI modifier indicator (also called the Correct Coding Modifier Indicator, or CCMI) is a single-digit value—0, 1, or 9—assigned to every NCCI Procedure-to-Procedure (PTP) edit that tells billers whether an NCCI-associated modifier can ever be appended to bypass that edit and receive separate payment.
Verified May 8, 2026 · 6 sources ↓
Definition
Source · Editorial summary grounded in 6 cited references ↓
Every PTP edit in the CMS NCCI edit files pairs a Column One CPT/HCPCS code with a Column Two code. When both codes are submitted for the same patient on the same date of service, the Column Two code is automatically denied—unless the modifier indicator signals that a bypass is possible. A CCMI of '1' means an appropriate NCCI-associated modifier (such as 59, XE, XP, XS, or XU) may be appended when the clinical circumstances genuinely support separate and distinct services—for example, procedures performed at different anatomic sites, during separate encounters, or on contralateral paired structures. A CCMI of '0' means no modifier can ever override the edit; the two codes are considered inseparable under any clinical scenario, and billing both will always result in denial of the Column Two code. A CCMI of '9' is a housekeeping value applied only when a code pair's deletion date equals its effective date, meaning the edit never had an active life; the pair is billable without a modifier.
In orthopedics, the CCMI has direct implications for common arthroscopic and open procedures performed during the same operative session. For instance, the PTP edit pairing shoulder capsulorrhaphy (CPT 29806) with limited shoulder debridement (CPT 29822) carries a CCMI of '1,' indicating that Modifier 59 or an X-modifier can justify separate payment if documentation clearly supports two distinct services. By contrast, a CCMI of '0' on a pair—such as certain component codes bundled into a major surgical procedure—signals that no documentation, however detailed, will unlock separate reimbursement.
CMS publishes NCCI PTP edit files quarterly, and the CCMI value for any given pair can change across update cycles. Coders and orthopedic practices must verify the current modifier indicator in the active CMS edit files rather than relying on cached references or prior-quarter tables, since additions, deletions, and CCMI changes are posted each quarter.
Why it matters
Misreading or ignoring the CCMI is one of the most direct routes to both claim denial and post-payment audit exposure. Appending Modifier 59 to a code pair with a CCMI of '0' will not unlock payment—the edit will still deny—and repeated inappropriate modifier use on '0' pairs can trigger Medicare Administrative Contractor (MAC) scrutiny or a Targeted Probe and Educate review. Conversely, failing to append a modifier to a CCMI '1' pair when the clinical record genuinely supports separate services leaves legitimate reimbursement on the table. Because orthopedic surgeons frequently perform multiple arthroscopic procedures in a single session, correctly interpreting the CCMI on pairs like 29827/29826 or 29806/29822 can mean the difference between full payment and systematic underpayment across an entire practice.
Common mistakes
Where people most often go wrong with this concept.
Source · Editorial brief grounded in cited references ↓
- Appending Modifier 59 to a code pair with a CCMI of '0,' assuming any modifier will unlock payment—it will not; a '0' indicator is absolute.
- Using a prior-quarter NCCI edit file and missing a CCMI change; CMS updates indicator values quarterly and a '1' can become '0' or a pair can be deleted entirely.
- Confusing the CCMI with the MUE (Medically Unlikely Edit) adjudication indicator—these are separate fields governing different types of edits and are not interchangeable.
- Appending Modifier 59 on a CCMI '1' pair without documentation that specifically supports a separate site, separate encounter, or contralateral structure—the modifier is clinically gated, not a billing override.
- Treating a CCMI of '9' as a special permission indicator rather than recognizing it simply marks an edit that was never active because the effective and deletion dates are identical.
- Overlooking that modifiers 22, 76, and 77 are not NCCI PTP-associated modifiers and cannot bypass any PTP edit regardless of the CCMI value.
Related codes
Codes commonly involved when this concept appears in practice.
CPT
- 29806 $972.97Arthroscopic surgical repair or tightening of the shoulder joint capsule to correct instability or recurrent dislocation.
- 29807 $951.93Arthroscopic surgical repair of a superior labrum anterior and posterior (SLAP) lesion of the shoulder joint.
- 29822 $516.04Arthroscopic shoulder surgery with limited debridement of one or two discrete structures within the shoulder joint.
- 29823 $558.80Arthroscopic surgical debridement of the shoulder involving three or more discrete anatomic structures.
- 29826 $147.63Arthroscopic shoulder surgery to decompress the subacromial space, including partial reshaping of the acromion and release of the coracoacromial ligament when performed. Add-on code — always listed in addition to a primary shoulder arthroscopy code.
- 29827 $976.31Arthroscopic surgical repair of the rotator cuff, performed entirely through the shoulder joint via endoscopic technique.
- 27447 $1,159.35Knee replacement surgery addressing both the medial and lateral tibiofemoral compartments, with or without resurfacing of the patella.
- 27487 $1,574.52Revision total knee arthroplasty with replacement of both the femoral and tibial components, with or without the use of allograft tissue.
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 6 cited references ↓
01What is the difference between a CCMI of '0' and a CCMI of '1'?
02Can I use Modifier 22 or 76 to bypass an NCCI PTP edit?
03How often does CMS change CCMI values?
04In orthopedic surgery, when would a CCMI of '1' realistically allow separate billing?
05What does a CCMI of '9' mean in practice?
06Where can I look up the current CCMI for a specific code pair?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01cms.govhttps://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits
- 02cms.govhttps://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits/medicare-ncci-faq-library
- 03cms.govhttps://www.cms.gov/medicare/coding-billing/national-correct-coding-initiative-ncci-edits/medicare-ncci-procedure-procedure-ptp-edits
- 04cms.govhttps://www.cms.gov/files/document/2025nccimedicarepolicymanualcompletepdf.pdf
- 05aaos.orghttps://www.aaos.org/globalassets/quality-and-practice-resources/coding-and-reimbursement/resident-guide/resident-guide-coding-reference-tools_what-is-ncci-ptp.pdf
- 06apta.orghttps://www.apta.org/your-practice/payment/coding-billing/correct-coding-initiative-cci
Mira AI Scribe
When Mira's documentation layer detects that two CPT codes subject to an NCCI PTP edit have been selected for the same date of service, it should surface the current CCMI for that pair before the note is finalized. - If CCMI = 1: Prompt the surgeon to document the specific clinical rationale that distinguishes the two services—different anatomic site, separate incision, contralateral structure, or separate encounter. Flag that Modifier 59 or the appropriate X-modifier (XE, XP, XS, XU) will be required on the Column Two code at billing, and that the operative note must support it. Do not auto-append the modifier; confirm clinical justification first. - If CCMI = 0: Alert the user that these two codes cannot be billed together under any circumstances. The Column Two code will deny regardless of modifier use. Recommend selecting only the Column One code or verifying whether the intended service maps to a different CPT code that is not bundled. - If CCMI = 9: Note that the edit is inactive; both codes are separately reportable without a modifier. Mira should source CCMI values from the most recent quarterly CMS NCCI PTP edit file (updated January, April, July, October) and display the effective date of the indicator alongside any alert. Do not rely on hardcoded values from prior quarters. Modifier suggestions generated here do not constitute a guarantee of payment; MAC adjudication and documentation quality remain determinative.
See Mira's approach