Cortex now checks every chart against the full ICD-10 Excludes1 rule set

There is a class of claim denial that billers see every single week. The chart looks complete. The documentation is solid. And the payer denies the whole claim anyway, because two diagnosis codes on it contradict each other.

A real example: I12.9 (hypertensive chronic kidney disease) billed alongside I15.0 (renovascular hypertension). One code says high blood pressure damaged the kidneys. The other says the kidneys caused the high blood pressure. ICD-10 requires you to pick one story — and when both codes land on a claim, major payers deny everything on it, including the visit itself and any ancillary services.

The rules are published. Nobody can hold them.

These are not arbitrary payer whims. ICD-10-CM ships with Excludes1 notes — official "never code these together" rules, maintained by the CDC and updated every fiscal year. Payer claim-edit engines enforce them automatically.

There are more than five thousand of them.

No physician finishing a visit, and no biller working through a stack of charges, can reliably hold five thousand exclusion rules in their head. That is exactly the kind of work software should be doing — and as of today, Cortex does it on every chart.

What shipped

Cortex Engine now ingests the complete official ICD-10-CM Excludes1 table and cross-checks every active diagnosis pair on the chart against it, deterministically. Not a model's best guess — the published rule, applied the same way every time, in milliseconds, as part of the problem-list checks that already run on every analysis.

When a conflict is found, the Lens flags it before sign-off with the rule it violated and both resolution paths: keep one code, or keep the other. And because ICD-10 itself allows one exception — an Excludes1 pair may legitimately coexist when the two conditions are genuinely unrelated — Cortex surfaces the conflict for review rather than pretending the judgment call doesn't exist. The clinician and the biller stay in charge; they just stop getting ambushed.

This pairs with the checks Cortex already ran: combination-code redundancies (plain polyneuropathy coded next to diabetes-with-polyneuropathy), duplicate diagnoses, stage and specificity gaps. Together they cover the most common ways a clean-looking chart turns into a denied claim.

Why it matters in dollars

A clean claim typically pays in one to two weeks. A denied claim means re-keying, a physician consult to resolve the conflict, resubmission paperwork, and a fresh 30-to-45-day adjudication clock — industry surveys put the cost of reworking a single claim at $25 or more, before counting the cash-flow lag. A practice posting a handful of mutually-exclusive-code denials per week is quietly funding a lot of rework.

Catching one of these pairs before signature costs nothing. That trade is the whole product thesis: the chart-entry workflow doesn't change, and an entire category of denial quietly stops happening.

The full rule table updates with each ICD-10-CM fiscal-year release, so the checks stay current as the code set evolves. It's live now — open a chart, run the Lens, and the encyclopedia is on your side.