Skip to main content

Medically Unlikely Edits

MedCoder provides supported CMS-derived MUE information within its non-CPT data scope. Where CMS publishes a value for a supported HCPCS Level II code, MedCoder reports that value, the indicator that governs how it is applied, and the release it was published in.

What an MUE is

An MUE is the maximum units of service CMS publishes for a code on the vast majority of appropriately reported claims by the same provider or supplier, for the same beneficiary, on the same date of service. It is a utilization figure attached to one code. It says nothing about whether that code pairs correctly with another, and nothing about whether the service is covered.

It is also a threshold rather than a verdict. Exceeding a published MUE is a utilization-rule finding — published utilization threshold exceeded, review required — and how any particular claim is handled depends on the applicable circumstances and rules.

Why the indicator matters as much as the value

CMS publishes an MUE Adjudication Indicator alongside every value, and it changes what the number is counted against. Under indicator 1 each claim line is considered on its own. Under indicators 2 and 3 the units compared are the sum across every line carrying that code on one date of service, which is a different and usually stricter comparison.

The three also differ in what they rest on: 2 is grounded in policy, which CMS treats as absolute, while 3 is grounded in clinical judgement and may be supported by documentation. MedCoder reports CMS’s indicator with its published label rather than collapsing the three into one number.

Zero is a published value

CMS publishes an MUE of 0 for codes it does not consider reportable in a given setting. That is the strictest edit it publishes, not an absence, and MedCoder reports it as a published value. A code with no published MUE is simply absent from the file, which is a different thing entirely and is reported differently.

What a result shows

Each field is read from the CMS row or from the release it came from. Where CMS publishes nothing for a field, MedCoder reports it as absent rather than supplying a figure.

  • MUE value — The maximum units of service CMS publishes for the code in that programme and setting. Zero is a published value, not an absence.
  • MUE Adjudication Indicator — CMS’s indicator, with its published label: a line edit, a date-of-service edit grounded in policy, or a date-of-service edit grounded in clinical judgement.
  • Rationale — CMS’s own published reason for the edit, quoted as published.
  • Programme and care setting — Medicare or Medicaid, and practitioner, hospital outpatient or DME supplier. CMS publishes a separate table for each combination and the value is not the same in every setting.
  • Release and version — The MUE release the value was read from, with the effective window that release covers.
  • Units compared — The unit count the published value was compared against, and where that count came from. Claim Check collects codes rather than quantities, so it states plainly when the comparison used an assumed single unit.

The outcomes, and what each one means

The distinction the whole feature turns on is between a value CMS did not publish and a value MedCoder does not carry. Both mean no number is shown; they mean opposite things about CMS.

  • Published MUE information found — within the published value — The units reported are below the value CMS publishes for the code in that setting. A statement about that published figure, and nothing more.
  • Published MUE information found — at the published value — The units reported are exactly the published value.
  • Published utilization threshold exceeded — review required — The units reported are above the value CMS publishes. A utilization-rule finding, not a statement that a payer will deny the claim.
  • No supported published MUE information found — The loaded release does not list a value for this code in this setting. CMS states that not every code carries an MUE, that most values are published while others are confidential, and that confidential values are not releasable — so this does not establish that no MUE exists.
  • Value not carried for this code — CMS publishes a value, but the code belongs to a licensed code set MedCoder does not carry. The gap is MedCoder’s, not CMS’s, and the result says so and points to CMS’s own table.
  • Not applicable — The token is not a procedure or supply code, or the line reports no unit count to compare.
  • Data unavailable — No MUE release is loaded, no loaded release covers the date of service, or more information is needed before a value can be applied — for instance a date of service when a code appears on more than one line.

The deliberate boundary

CPT is permanently outside MedCoder’s scope. The CMS files behind this rule set are keyed on both HCPCS Level II and CPT; only the HCPCS Level II rows are stored, and the CPT-keyed rows are counted and discarded at ingest. MedCoder therefore holds a supported subset of this rule set and never the whole of it, and a pair or code it holds no row for is a gap here — not a statement that CMS published nothing.

So MedCoder does not contain a complete MUE database and makes no claim to. It reports supported published values for the HCPCS Level II codes it is permitted to retain.

MedCoder publishes only what CMS publishes. CMS holds some MUE values confidential and does not release them; none of those has been reconstructed, inferred, estimated or derived here, and the absence of a value in MedCoder is never presented as evidence that CMS publishes none.

The count of rows excluded at the licence boundary is recorded at ingest as a data-scope metric. No excluded code is stored or shown.

An MUE finding is a utilization finding. It is kept separate from NCCI procedure-to-procedure rules, from Medicare coverage policy, and from MS-DRG grouping, because those answer different questions and merging them would let one of them be read as the others.

Source and versioning

CMS National Correct Coding Initiative Medically Unlikely Edit tables, published quarterly. As with the procedure-to-procedure tables, CMS distributes separate files by programme and care setting and MedCoder loads each as its own source.

The CMS MUE tables carry no per-row effective or deletion dates — a release is the window, and every value in one shares it. That is why MedCoder reports the release and its effective window rather than a per-value date: attaching one would invent a fact CMS did not publish.

Every result names the CMS source it came from and the release version behind it, with the effective window that release covers and, where CMS publishes one, the rule’s own effective and deletion dates. A claim is evaluated against one release per source, never a mixture, and a release that does not cover the date of service is reported as not consulted rather than quietly skipped.

Frequently asked questions

MedCoder shows no MUE for my code. Does that mean there is no MUE?

No, and MedCoder is careful never to say so. It reports that the loaded release does not list a value for the code in that setting. CMS states that not every code carries an MUE, that most published values appear on its website, and that some values are confidential and not releasable. Any of those could be true of your code, and MedCoder has no way to tell which from the file it holds.

My units are above the published MUE. Will the claim be denied?

MedCoder does not answer that and cannot. What it reports is that a published utilization threshold has been exceeded and that review is required. An MUE is a CMS utilization edit, and how any particular claim is handled depends on the applicable circumstances and rules, including documentation and policy MedCoder does not model.

Why does the same code show a different value in a different setting?

Because CMS publishes a separate MUE table for each programme and care setting, and the value is genuinely not the same in all of them. Where a claim does not state the setting, MedCoder shows the published values it holds for each one, each naming the release it was read from, rather than picking one and presenting it as the governing figure.

Does MedCoder hold historical MUE values?

It holds each loaded release with the effective window that release covers, and reports the value from the release that covers your date of service. It does not hold a per-value history, because the CMS tables publish no per-row effective or deletion dates for one to be built from. Where no loaded release covers the date, the answer is data unavailable rather than a value from a release that does not apply.

Run this rule set on a code list with Claim Check, or see all CMS coding rules. Release versions and checksums are on the Data Sources page.