CorePulse Field Notes / AI Coding NCCI PTP Edits 2026

An edit that fires is not a door that closes. It is a question the chart has to answer.

Most over-coding does not come from missing content. It comes from correct-coding edits a practice already owns and never enforced. Here is how CorePulse, ASP-RCM's autonomous coding engine, reads a Procedure-to-Procedure edit the way a senior coder does: check the indicator first, then ask what the documentation actually supports.

48%

of measured over-coding

traced back to NCCI Procedure-to-Procedure edits that were already owned and available, but sat unenforced at the point of coding. The content was never the gap. Enforcement was.

The gap is enforcement, not content

The NCCI Procedure-to-Procedure (PTP) edit tables and the NCCI Policy Manual are published quarterly by CMS and are free to every practice in the country. The question was never whether a team had the edits. It was whether every claim actually ran through them, line by line, before it left the building.

0 & 1

The two Correct Coding Modifier Indicators (CCMI) that decide whether a PTP edit can ever be bypassed

Quarterly NCCI edit-table releases CorePulse re-syncs against every year

Questions asked of every CCMI-1 edit: is it documented, and is an approved modifier justified

95%+

CorePulse coding accuracy with NCCI enforcement running inline on complete claims

CCMI is the first read, and it is binary

Every PTP edit carries a Correct Coding Modifier Indicator. Before CorePulse considers a modifier at all, it reads the indicator. That single value decides whether the conversation is even open.

CCMI = 0 / Closed

No modifier can separate these codes

A CCMI of 0 means the edit cannot be bypassed under any circumstance. There is no documentation, no clinical scenario, and no modifier that makes the column-two code separately payable with the column-one code on the same claim. CorePulse holds the line and reports the edit rather than routing around it.

The pairing is not separately reportable, period
Modifier 59 and the X{EPSU} subset are irrelevant here
Bypassing a CCMI-0 edit is an unbundling exposure, not a recovery

CCMI = 1 / Conditional

Conditionally bypassable, only if the chart earns it

A CCMI of 1 does not mean "a modifier is allowed." It means the edit is conditionally bypassable, and only when the documentation supports a distinct service and an approved modifier is genuinely justified. The edit existing does not prove both services are separately billable. The record has to.

Distinct service must be documented in the note, not assumed
An approved modifier must be clinically justified by that documentation
Absent both, the correct action is to leave the edit in force

How CorePulse walks a CCMI-1 edit

The engine treats a conditional edit as a decision with a burden of proof, evaluated on the complete claim, not on a line pulled out of context.

Read the indicator

Match the code pair to the current NCCI PTP table and pull its CCMI. A 0 stops here and stays bundled.

Test the documentation

For a CCMI of 1, look for a distinct service in the note: separate session, site, lesion, or encounter that the record actually describes.

Justify the modifier

Only if the distinct service is documented does CorePulse consider an approved modifier, and it picks the most specific one the note supports.

Otherwise, hold

No documented distinction means no bypass. The edit stays in force and the line is flagged, not silently overridden.

Default posture: edit in force. A bypass is an earned exception backed by the record, never the starting assumption.

Modifier 59 and X{EPSU} are exceptions, never defaults

These modifiers exist to describe a specific documented circumstance. CorePulse never reaches for them to clear an edit. It reaches for them only when the note already tells the story, and it prefers the precise X subset over the blunt instrument.

The distinct-service set

59 XE / separate encounter XS / separate structure XP / separate practitioner XU / unusual, non-overlapping

The X{EPSU} subset is a more specific alternative to 59. When the documentation points to one, CorePulse uses the specific subset rather than defaulting to 59.

An edit firing does not prove two services are separately billable. It proves a question needs answering. The answer lives in the documentation, not in the modifier.

No modifier is a default. 59 and every X subset require a documented clinical circumstance. Applied without one, they convert a coding shortcut into an audit finding.

Owned versus enforced

Every practice already owns the NCCI edit content. The measured difference shows up in how consistently those edits actually run against complete claims before submission.

CorePulse, inline NCCI enforcement

95%+ coding accuracy

Manual review, edits owned but unenforced

enforcement gap

The lower bar is not a content problem. It is the share of edits that never got checked at the point of coding, the same enforcement gap behind roughly half of measured over-coding. CorePulse closes it by running every PTP edit on every complete claim, every time.

Guidelines CorePulse codes against, by name

No proprietary interpretation stands in for the source. CorePulse cites the same authorities a compliance auditor would open.

NCCI POLICY MANUAL 2026The National Correct Coding Initiative Policy Manual for Medicare Services (2026) governs how Procedure-to-Procedure edits are interpreted and when a distinct service may be reported.

PTP EDIT TABLESThe quarterly NCCI Procedure-to-Procedure edit tables define each column-one / column-two pairing and carry the modifier indicator CorePulse reads first.

CCMI 0 / 1The Correct Coding Modifier Indicator: 0 means the edit cannot be bypassed, 1 means it is conditionally bypassable with appropriate documentation and an approved modifier.

MODIFIER 59The distinct procedural service modifier, reserved for documented circumstances and used only when a more specific subset does not apply.

X{EPSU} SUBSETThe XE, XS, XP, and XU modifiers, specific alternatives to 59, each requiring its own documented clinical circumstance.

Stop routing around the edits you already own

CorePulse enforces the NCCI PTP tables inline on every complete claim, reads CCMI before it reads a modifier, and never treats a distinct-service modifier as a default. If half your over-coding traces to edits you already have, the fix is enforcement, and it can run this quarter.

See CorePulse on your claims

ASP-RCM Solutions / CorePulse Autonomous Coding Engine