What Does an MUE Adjudication Indicator of 1, 2 or 3 Change?

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. Coders often read the number and stop there. The number is only half of it.

The MUE Adjudication Indicator decides what the number is compared against. Under one indicator, a claim carrying the same code on three lines is three separate comparisons. Under another, it is one comparison against the sum. The same claim and the same published value can pass one way and fail the other.

The distinction between 2 and 3 is not cosmetic. Both sum the day, but only one of them is open to a documentation argument.

1. Find the published value for the code in the programme and care setting on the claim. CMS publishes a separate table for each, and the value is genuinely not the same in all of them.
2. Read the indicator beside it before comparing anything.
3. If the indicator is 1, compare each line separately.
4. If the indicator is 2 or 3, total the units for that code across the date of service and compare the total.
5. If the total exceeds the published value, treat it as a published utilization threshold exceeded and a prompt to review — not as a denial.

A line edit. A code with a published value of 2 and an indicator of 1 appears on three lines, two units each. Each line is judged alone, so each is compared against 2 and each is within it. The day’s total of six is not the figure CMS compares under this indicator.

A date-of-service edit. The same code, same three lines, but the indicator is 2. Now the comparison is against the day’s total of six, which exceeds the published value of 2. The finding is that a published threshold has been exceeded, and the next step is review of whether the units are correctly reported.

A published value of zero. 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 a single assumed unit already sits above it.

• Reading a value of 0 as “no MUE”. Zero is a published value. A code with no published MUE is simply absent from the file, which is a different thing.
• Reading no published value as “no limit exists”. CMS states that not every code carries an MUE, that most values are published, and that some are confidential and not releasable. Absence from what you can see does not establish absence.
• Comparing line units under a date-of-service indicator. Under 2 and 3 the day is summed, and a claim that passes line by line can still exceed the published figure.
• Treating an exceeded threshold as a denial. It is a utilization-rule finding. How a particular claim is handled depends on circumstances and rules beyond the value.
• Carrying a value across settings. The published figure differs by programme and care setting.

Under an indicator of 3 the basis is clinical judgement, so documentation can matter: the record may support units above the published figure for a specific patient on a specific day. Under an indicator of 2 the basis is policy, which CMS treats as absolute, and no documentation changes the arithmetic.

In every case the first documentation question is simpler than the edit: are the units on the claim the units that were actually provided? A threshold finding can be a units-entry problem rather than a policy problem.