CO-151 means the payer adjusted payment because it says the submitted information does not support the number or frequency of services billed. On a pharmacy medical claim, that can point to the units on one service date or to how soon a supply or service was repeated. Read the affected line, any accompanying remark, and the service dates before deciding which question the payer raised.
If the pharmacy billed more units than it furnished, correct the claim using the payer’s instructions. If the billed quantity is accurate, compare the payer’s utilization rule with the delivery or clinical record and prior paid claims before requesting review.
What CO-151 says on the remittance
X12 defines reason code 151 as an adjustment when the payer finds that the submitted information does not support this many or this frequency of services. CO assigns the adjustment to contractual obligation. The number 151 describes the payer’s stated concern; the remittance’s service line, remark code and policy reference supply the context for that claim.
For example, Noridian’s Medicare DME guidance pairs 151 with remark N115, which points to a Local Coverage Determination. Noridian lists a reached frequency limit or an overlapping date span among its possible causes. Another payer can use different rules, and CO-151 alone does not establish that an LCD or a specific unit edit applied.
One day of units and a longer supply interval
Medicare’s medically unlikely edit, or MUE, checks units for a HCPCS or CPT code reported by the same provider for the same patient on one date of service. Some edits test each claim line; others add units across lines for that date. Not every code has an MUE, and some values are confidential. CMS updates its published files at least quarterly, including a separate DME supplier file. Finding an MUE for a code is useful context, but it does not prove that the payer used that edit for this CO-151 adjustment.
A coverage policy can instead limit how often an item or service is furnished across a longer span. In Noridian’s 151/N115 DME example, a previously paid supply period may overlap the new claim. The issue is then the relationship between dates and the policy, even when the unit count on the new line is correct.
Two claims with the same reason code
Consider two hypothetical DME claims from a pharmacy. In the first, the claim reports two billable units, but the delivery record and the code’s unit definition support one. The mismatch is on the submitted line. The pharmacy should verify the unit basis and use the payer’s corrected-claim process for the actual error.
In the second, the claim reports one valid unit, but an earlier paid claim covers a span that overlaps the new service date. Reducing the new claim to zero or changing its code would not establish when the supply was needed. Compare the earlier paid span, the new delivery date, and the policy that applied on that date. If the date span was entered incorrectly, correct it with the supporting record. If the dates are right and the patient needed the item sooner, the medical record and the payer’s exception or review rules determine whether the claim can be reconsidered.
A pharmacy should use its medical-claim history for that comparison. A separate prescription-benefit transaction does not establish what a Medicare DME contractor or medical payer already paid. The DME claim-file guide explains the order, delivery and claim records that support the medical path.
When the submitted quantity is correct
For a Noridian 151/N115 response, check the applicable LCD and policy article, the prior paid date span and the documentation of medical need. Noridian permits a self-service reopening to adjust a date span supported by records; it also describes an appeal with documentation when the billed quantity and need are supported. Those are contractor-specific routes, not automatic instructions for every CO-151 claim. Follow the named payer’s current process and filing deadline.
If the remittance, claim history or coverage rule does not explain the result, have a billing reviewer identify the disputed fact before resubmitting. A plain-language software label can make the reason easier to find, but it cannot establish the payer’s underlying rule. The medical-claim denial guide covers that broader review.
Can the patient be billed for CO-151?
Do not move a CO adjustment to patient responsibility simply to close the balance. CMS says an ABN cannot shift liability for units denied by a Medicare MUE. A separate coverage-policy denial may have different liability rules, so review the complete remittance, the applicable program and any valid notice before sending a patient bill. If those facts conflict, keep the balance for qualified review.
CO-151 concerns support for the number or frequency billed. PR-119 addresses a benefit maximum, which is a different question when the payer says the plan’s allowed count has already been used.
