How it works
The exact logic behind every verdict
This page describes what the engine actually checks, in the order it checks it. Where CMS publishes a rule with real teeth, like a modifier indicator or an adjudication indicator, we explain the specific teeth rather than a rounded-off summary.
Before submission
Scrubbing a claim
Three steps, run in this order, every time.
- 1
Validate the input
The date of service must parse as a real calendar date, because it decides which CMS edit quarter governs every check that follows. Each line's code must be five characters and units must be a positive whole number. A claim that fails validation runs no edits at all rather than a verdict against a code or date it could not parse.
- 2
Check every pair for a PTP edit
Every distinct pair of billed lines is checked, in both code orderings, against the NCCI procedure-to-procedure table for the date of service. An edit only applies if it was in force on that date: effective on or before it, and not yet deleted. A pair with no match in our dataset is reported not checked, not clean.
- 3
Sum units and check the MUE
Units for the same code across multiple lines are summed for the date of service, because a medically unlikely edit judges the whole day's total, not one line in isolation. The sum is compared against the CMS MUE value for that code, and the remedy depends entirely on the adjudication indicator, not on how far over the limit you are.
PTP edits
What a modifier indicator actually permits
An NCCI procedure-to-procedure edit bundles a component code (column 2) into a comprehensive code (column 1). What happens next depends entirely on the modifier indicator CMS publishes for that pair, not on which modifier you happen to have on hand.
| Indicator | Meaning | What DenialPath reports |
|---|---|---|
| 0 | No modifier can ever bypass this edit. | Will deny Remove the component code, or bill it on a different date of service. A 59 or X modifier here is flagged as an incorrect use of the modifier, not a fix. |
| 1 | A modifier may bypass the edit when the services were genuinely distinct. | Will deny if no bypass modifier is present, naming the specific modifiers that could apply, never a blanket instruction. Bypassed if one of them (59, XE, XS, XP, XU) is already on the component line. |
| 9 | The edit does not apply, or was deleted for this date of service. | Not reported as a finding. Treated as if no edit exists for this pair on this date. |
| no match | We hold no PTP row for this pair, or it was not in force on the billed date of service. | Not checked Our PTP data is a curated subset of the full CMS file. This is never rendered as a pass. |
The pair is directional. CMS always publishes column 1 (payable) and column 2 (bundled), and it is always column 2 that gets denied, regardless of the order you billed the two lines in.
MUE edits
Why the adjudication indicator matters more than the overage
A medically unlikely edit caps the units of one code payable for one patient on one date of service. Units across every line billing the same code are summed first, then compared to the CMS limit. What happens if you are over depends on the MAI, not on how far over you are.
| MAI | Type | Can it be overcome |
|---|---|---|
| 1 | Line edit | Only the units over the limit deny on that line. Reporting genuinely separate services on separate lines with an appropriate modifier may be correct. Splitting units across lines purely to defeat the edit is not. |
| 2 | Date of service, absolute | No. Units above the limit are never payable on that date, regardless of documentation, a modifier, or an appeal. The only remedy is to reduce the units billed to the limit. |
| 3 | Date of service, clinical | Yes, on appeal, when the medical record supports the higher count. This is the one MAI where an appeal is a genuine option rather than a formality. |
A code with no MUE row in our dataset is reported Not checked not a pass. Our MUE data is a curated subset of the CMS practitioner MUE table.
After a denial
Turning a CARC and RARC into a ranked plan
Resolving a denial is deterministic lookup and ranking, not a model guessing at what a remittance code means.
- 1
Parse the CARC and any RARCs
A group code prefix (CO, PR, OA or PI) is split from the reason code number. CO means the provider is responsible and the amount cannot be billed to the patient; PR means it may be billed to the patient; OA and PI cover the remaining cases. Any RARCs on the same line are looked up alongside it.
- 2
Rank the corrective actions
Each CARC and RARC we hold carries its own corrective actions and an appeal-worthiness rating (low, medium or high) with the reasoning behind it. Actions from the CARC come first, RARC actions are added and de-duplicated, so you get one ranked list instead of two lists to reconcile by hand.
- 3
Draft the appeal letter
The letter argues the billing question the corrective actions raise, cites the CARC, RARC and payer sources behind it, and states plainly which fields it could not fill in: a claim number, a date of service, a practice name. It never invents a clinical fact about the patient, because the engine does not know one.
Versioning
Why the date of service decides everything
CMS republishes the NCCI PTP and MUE files every quarter, and an edit that exists this quarter may not have existed when the claim was actually rendered. Every verdict records the edit quarter it was checked against, derived from the date of service, not from today's date. An edit applies only if it was effective on or before the date of service and had not yet been deleted; if either date is missing or malformed, the edit is treated as inapplicable rather than assumed live. That quarter is part of the answer, and part of the audit trail Pro saves with every claim.
FAQ
Mechanism questions
What does modifier indicator 0 mean on a PTP edit?
No modifier is permitted to bypass this edit under any circumstances. The component code is bundled into the comprehensive code and stays bundled no matter what is appended to it. The remedy is to remove the component code or bill it on a separate date of service.
What does modifier indicator 1 mean?
A modifier may bypass the edit, but only when the services were genuinely distinct: a different session, site, or encounter. The engine names the specific modifiers CMS recognises for this (59, XE, XS, XP, XU), not a blanket instruction to add modifier 59. If one of those modifiers is already present on the component line, the finding is reported as bypassed rather than as a plain pass, so you can see it was allowed through and on what authority.
What is the difference between MAI 1, 2 and 3?
MAI 1 is a line edit: only the units over the limit deny on that line, and reporting genuinely separate services on separate lines with an appropriate modifier can be correct. MAI 2 is an absolute date-of-service edit: units above the limit are never payable on that date, full stop, and no modifier, documentation or appeal changes that. MAI 3 is a clinical date-of-service edit: units above the limit can be allowed on appeal when the medical record actually supports the higher count.
Why does a result ever say not checked instead of pass?
Because our NCCI PTP and MUE datasets are curated subsets of much larger CMS files, and reporting a pass we did not earn would let a claim go out on a green light we never actually gave. See the methodology page for exactly how much of the CMS files we cover today.
NoticeDenialPath provides billing and administrative guidance based on published CMS and X12 sources. It is not medical advice, not a coverage determination, and not a guarantee of payment. NCCI and MUE edits are republished quarterly and payer policies vary by contract. Always confirm against the payer's own current policy before submitting or appealing.
Try it on a real claim
The free scrubber runs this exact logic in your browser. No card, no signup.