CorePulse · Autonomous Coding

The NCCI edits humans skip

Most over-coding is not a missing rule. It is unenforced NCCI. CorePulse enforces what your organization already owns, at the moment the claim is built.

The short answer

The edits that cause takebacks are almost never exotic. They are the NCCI Procedure-to-Procedure (PTP) pairs and Medically Unlikely Edits (MUEs) that CMS already publishes and updates quarterly. A busy coder skips them under volume pressure. CorePulse checks every line, every claim, reads the CCMI value on each PTP pair, and only proposes a bypass when the documentation and an approved modifier actually support it. Nothing is waived by default.

The reality operators live with

You are not missing rules. You are missing enforcement.

CMS republishes the National Correct Coding Initiative every quarter, free. The PTP tables and MUE tables ship as public files. The problem was never access to the edits. It was applying all of them, on every claim, without fatigue.

4× NCCI PTP and MUE tables refresh per year (quarterly). CorePulse loads each release the day it publishes.

100% of claim lines screened against the current PTP and MUE tables before submission. No sampling, no line extracts.

0 default modifier bypasses. A 59 or X{EPSU} is only proposed when the note documents a distinct service.

≥95% CorePulse CPT-line coding accuracy on production charts. The gap you are closing is enforcement, not knowledge.

The flow

Where CorePulse catches a PTP or MUE edit at claim build

Follow a single encounter from coded lines to a submission-ready claim. The gold node is the decision gate, where an edit either holds or is conditionally cleared with documentation.

Claim-build enforcement path

NCCI PTP + MUE · 2026 tables

Coded lines arrive input

Every CPT and HCPCS line from the encounter enters the builder with its units, date of service, and any coder-applied modifiers.

column1 / column2 pairs assembled per DOS

PTP screen NCCI table lookup

Each billable pair is checked against the current CMS NCCI Procedure-to-Procedure edit table. If the pair appears, CorePulse reads its Correct Coding Modifier Indicator (CCMI).

is (col1, col2) an active PTP edit this quarter?

MUE screen units of service

Line units are tested against the Medically Unlikely Edit value for that code. Units above the MUE are flagged with the applicable MUE Adjudication Indicator so nothing over-bills silently.

units ≤ MUE value ? pass : flag(MAI)

Decision gate CCMI resolves the pair

The edit does not decide billability by existing. CorePulse reads the CCMI and the documentation together before it does anything.

CCMI = 0 Not bypassable. The pair cannot be unbundled under any circumstance. The column-2 code is held. No modifier will clear it.

CCMI = 1 Conditionally bypassable only if the note documents a separate, distinct service and an approved modifier applies. Otherwise the edit holds.

Documentation test evidence, not assumption

For a CCMI of 1, CorePulse looks for the distinct-service evidence in the record: separate site, separate session, separate encounter, or separate lesion. No evidence means no bypass, and the line is held for review.

distinct-service documented ? propose modifier : hold

Submission-ready claim output

The claim leaves the builder either clean or with a documentation-backed, correctly scoped modifier attached. Every held line carries the reason, so the coder reviews an explanation, not a mystery denial three weeks later.

clean claim + audit trail per line

Read the indicator

What the CCMI actually permits

The Correct Coding Modifier Indicator on each PTP pair is the whole game. It is the difference between a compliant bypass and a takeback. Here is how CorePulse treats each value.

Never bypassable

The two services can never be reported separately for the same patient, same day. No modifier, no documentation, no exception clears a CCMI of 0. CorePulse holds the column-2 code.

Edit holds, always

Conditionally bypassable

Separation is allowed only when the record documents a distinct service and an approved modifier applies. The edit existing does not prove both services are separately billable. Absent evidence, it holds.

Documentation required

Not applicable

The indicator of 9 means the edit has been deleted or the modifier concept does not apply to that pair. CorePulse treats it as no active bypass logic, not as a green light.

No bypass logic

Modifiers 59 and X{EPSU} are earned, never assumed

These modifiers signal a distinct procedural service. CMS guidance is explicit that the specific X modifiers are preferred over 59 where they apply. None of them is a default. CorePulse proposes one only when the note supports the exact distinction it claims.

59Distinct procedural service (use when no more specific X modifier fits)

XESeparate encounter

XSSeparate structure or organ

XPSeparate practitioner

XUUnusual non-overlapping service

The guardrail in one line: a modifier is a claim that two services were genuinely separate. If the documentation does not show the separation, CorePulse does not attach the modifier. It holds the line for a coder. That is the difference between defensible coding and a modifier the auditor reverses.

Manual pass vs enforced pass

Same rules. Different follow-through.

The edits below are the same for everyone. What changes is whether they are applied on every line, every time. Manual and baseline figures reflect the enforcement gap, not the coders' knowledge.

Checkpoint	Manual, under volume	CorePulse at claim build
PTP pair lookup	Memory + spot checks	Every pair vs current table
CCMI read on the pair	Often skipped	Read on every edit
MUE unit ceiling	Caught after denial	Flagged before submit
59 / X{EPSU} basis	Applied to clear the edit	Only if note documents it
Held-line reason	Rarely recorded	Logged per line
Quarterly table update	Lags the release	Loaded at publish

Stop paying for edits you already own

The NCCI PTP and MUE tables are free and public. CorePulse turns them into enforcement on every claim, with a CCMI-aware gate and modifiers that are earned, not assumed. Let us run your own recent claims through it and show you the held lines.

Book a CorePulse walkthrough → ASP-RCM Solutions · autonomous coding that enforces what the manual already gave you

Sources referenced: CMS National Correct Coding Initiative (NCCI) Procedure-to-Procedure (PTP) edits, updated quarterly for 2026; CMS NCCI Medically Unlikely Edits (MUEs) and MUE Adjudication Indicators, 2026; Correct Coding Modifier Indicator (CCMI) values 0, 1, and 9; CPT modifier 59 and HCPCS modifiers XE, XS, XP, and XU (the X{EPSU} set) per CMS modifier guidance. An NCCI edit existing does not by itself prove two services are separately billable. Accuracy figures shown for CorePulse reflect production CPT-line performance; manual and baseline figures reflect the enforcement gap under volume, not coder knowledge.