CorePulse · Autonomous Coding Whitepaper

Catch the edit before the claim drops, not after the denial.

Most groups treat the National Correct Coding Initiative as a cleanup job. The claim goes out, a payer rejects the PTP pair or the impossible unit count, and someone opens the rework queue. CorePulse moves that whole fight upstream.

Short version: CorePulse is an AI medical coding engine that reads every NCCI Procedure-to-Procedure edit and every Medically Unlikely Edit at charge capture, so a bundled pair or an over-the-limit unit count gets resolved on the coder's screen, before it ever becomes a clearinghouse rejection or a payer denial.

PTP and MUE denials you should be chasing post-bill when enforcement lives at charge capture

4×

NCCI + MUE table refreshes a year that CorePulse tracks: Jan 1 / Apr 1 / Jul 1 / Oct 1

MUE adjudication tiers (MAI 1, 2, 3) the engine reads before it lets a unit count pass

100K+

Active PTP pairs in the 2026 NCCI tables, checked on every line, every claim

The two-timeline problem

Same edit. Very different day, depending on when you catch it.

An NCCI PTP edit and an MUE do not change based on your workflow. What changes is whether the edit is a two-second decision in the coder's hands or a two-week loop through denials, appeals, and resubmission.

The old way · post-bill scrub

Scrub after the bill

The edit fires downstream, after the claim already left the building.

Claim drops with a bundled Column One / Column Two pair still on it.
Payer or clearinghouse returns a PTP or MUE denial, often weeks later.
Coder re-pulls the note to decide if a modifier was ever supportable.
Correct, rebill, and restart the payer clock. Some fall past timely filing.

Cost = touched twice, aged AR, appeal risk

CorePulse · charge-capture gate

Enforce before it drops

The edit fires on the coding screen, while the note is still open.

Engine checks every line pair against the current NCCI PTP table.
Reads the Correct Coding Modifier Indicator: bundle, or conditionally separable.
Counts units against the MUE and its MAI tier before the line is allowed.
Clean claim drops the first time, with the rationale already documented.

Cost = touched once, no denial loop

Inside the engine

What CorePulse actually reads on every line.

The 2026 CMS NCCI Policy Manual does not say "apply a modifier." It says check the indicator, then confirm the documentation supports a genuinely separate service. CorePulse encodes that distinction instead of flattening it.

PTP · Correct Coding Modifier Indicator

Procedure-to-Procedure edits

0Not separableNo modifier can bypass this pair. CorePulse holds the Column Two code. No exceptions offered.

1Conditionally separable, with documentationA modifier is allowed only when the note supports a distinct service. The engine prompts for that proof, it never auto-applies 59.

9Edit not applicableThe pair was deleted or never applied. CorePulse lets it through cleanly.

MUE · Adjudication Indicator

Medically Unlikely Edits

MAI 1Claim-line editUnits over the cap on one line are flagged; sometimes splittable across lines when clinically real and documented.

MAI 2Date-of-service, absoluteGrounded in anatomy or policy. The count cannot be exceeded per day. CorePulse blocks it hard, no override path.

MAI 3Date-of-service, benefit of the doubtOver-limit is possible with strong documentation. The engine surfaces it for review rather than silently passing or killing it.

On the modifier question specifically: CorePulse treats the X{EPSU} subset (XE separate encounter, XS separate structure, XP separate practitioner, XU non-overlapping service) as CMS intends, as precise descriptors the note has to earn. XU and XS are never defaults, and a CCMI of 1 is a conditional door, not a green light.

Charge capture vs. post-bill

Where the money and the rework actually go.

	Post-bill scrubbing	CorePulse at charge capture
When the check runs	After the claim is transmitted	While the note is still open, before drop
What the payer sees	The bundled pair or over-limit units	A claim that already passed NCCI and MUE
Modifier decisions	Reverse-engineered under denial pressure	Made against the CCMI with documentation in view
Rework loop	Deny, re-pull, correct, rebill, re-age	None for edits caught at the source
Timely filing exposure	Real, on anything that ages out	Removed for first-pass-clean lines
Audit trail	Reconstructed after the fact	Captured at the decision, tied to the edit

A day in the queue

A 28-provider orthopedic group, one busy surgical day.

What the coder submitted

Column One + Column Two pair, CCMI 0bundled

Debridement units, MAI 2 cap exceededover limit

Distinct-structure pair, CCMI 1, note supports itseparable

What CorePulse did at capture

Held the Column Two code, showed whyresolved

Blocked units to the MAI 2 ceilingresolved

Prompted XS, coder confirmed against noteclean

This is an illustrative walkthrough, not a client metric. The point is the pattern: two of these lines would have been denials in a post-bill model, and the third would have been an unsupported modifier waiting for an audit. All three closed on the coding screen, and the claim dropped clean the first time.

Grounded in current CMS guidance

The rules CorePulse enforces, by name.

CMS · 2026

NCCI Policy Manual for Medicare Services

Chapter 1 general correct coding policies plus the specialty chapters that define how PTP pairs and modifiers are meant to be applied.

CMS · quarterly

PTP Edits & Correct Coding Modifier Indicators

The Column One / Column Two tables with CCMI values 0, 1, and 9, refreshed each quarter and versioned inside the engine.

CMS · quarterly

Medically Unlikely Edits (MUE)

Per-day and per-line unit ceilings with MUE Adjudication Indicators MAI 1, 2, and 3, read on every unit before a line is allowed.

CMS

Medicare Claims Processing Manual

Modifier 59 policy and the X{EPSU} subset (XE, XS, XP, XU), which CorePulse treats as descriptors the documentation must support.

CMS · 2026

Medicare Physician Fee Schedule

The valuation context the edits sit inside, so held and separable lines reconcile against the correct 2026 payment logic.

Payer-specific

Commercial & Medicaid edit variants

Many payers layer their own edits on the NCCI baseline. CorePulse holds those alongside the CMS tables rather than assuming one national rule fits all.

Move the NCCI and MUE fight to where it is cheap.

See how CorePulse enforces PTP edits and Medically Unlikely Edits at charge capture on your specialty mix and your payers, before a single denial is written.

Book a CorePulse walkthrough →

ASP-RCM Solutions · autonomous coding, built on current CMS guidance