How medical necessity works under LCDs and NCDs, why claims with a listed diagnosis still deny, how ABNs shift liability, and what MA plans must follow.
Medicare pays only for services that are reasonable and necessary, and the rules that define "necessary" for a specific service live in two places: National Coverage Determinations (NCDs), which apply everywhere, and Local Coverage Determinations (LCDs), which apply in one Medicare Administrative Contractor's jurisdiction. When a claim doesn't fit the applicable NCD or LCD, it usually comes back as CO-50: not medically necessary, provider liable.
Most of these denials are preventable, but not by coding alone. The diagnosis code has to match the policy, and the record has to support the policy's criteria. This guide covers how the pieces fit, where claims fail, and how to manage liability when coverage is in doubt. It sits alongside our coding denial code taxonomy, which separates medical necessity denials from the ones coding alone can fix.
Where medical necessity rules come from
The statutory standard is Section 1862(a)(1)(A) of the Social Security Act: Medicare won't pay for items or services that aren't reasonable and necessary for diagnosis or treatment. CMS and its contractors translate that standard into service-level policy.
| Source | Who issues it | Where it applies | What it contains |
|---|---|---|---|
| Statute and regulation | Congress, CMS | Nationally | Benefit categories, exclusions, general coverage rules |
| National Coverage Determination (NCD) | CMS | Every MAC jurisdiction | Coverage conditions for a specific item or service |
| Local Coverage Determination (LCD) | A Medicare Administrative Contractor (MAC) | That MAC's jurisdiction only | Coverage criteria where no NCD exists, or detail an NCD leaves open |
| Billing and Coding Article (LCA) | The same MAC | That jurisdiction | The CPT/HCPCS and ICD-10-CM codes, and coding rules, that go with the LCD |
CMS defines an LCD as a MAC's decision on whether a service is covered in its jurisdiction under Section 1862(a)(1)(A). The full process is in Chapter 13 of the Medicare Program Integrity Manual.
One structural change trips up coders who learned on older policies: codes have largely moved out of LCDs. The Medicare Coverage Database now notes that, for the most part, codes are no longer in the LCD itself. They're in the companion Billing and Coding Article. DME MACs are the exception, where CPT and HCPCS codes stay in the LCD. If your edit library still reads diagnosis lists out of LCD text, it's reading the wrong document.
Jurisdiction decides which rules apply
An LCD only binds claims processed by the MAC that wrote it. The same test can be covered for a diagnosis in one state and not in the next. For providers billing across MAC jurisdictions, this is where "national" denial rules quietly break.
Three practical consequences:
- Your edit library needs a jurisdiction key. A medical necessity edit has to know which MAC processes the claim, not just which code was billed.
- Confirm which MAC processes each claim type. Professional, facility and DME claims can go to different contractors, and the deciding factor isn't always where the patient lives.
- Subscribe to policy changes. The MCD lets you subscribe to any NCD, LCD or article. Billing and Coding Articles are revised often, including for the annual ICD-10-CM update each October 1.
Why claims with a "covered" diagnosis still deny
The most common complaint in medical necessity work is "we billed a diagnosis that's on the list." CGS, a Medicare Administrative Contractor, has published the reasons it sees most when that happens. Paraphrased:
- The diagnosis is on the article but not related to the service performed. It's listed for a different procedure in the same article.
- The article groups diagnoses by CPT code. Some ICD-10 groups support only specific procedure codes, not every code in the article.
- The policy requires two diagnoses and the claim carries one.
- The documentation doesn't support the diagnosis that makes the claim pass.
The first three are coding-logic failures that a pre-bill check can catch if it reads the article's code groups correctly. The fourth is the one that matters most in an audit. A claim that passes the edit because the right code was selected, without the record to back it, is a compliance problem rather than a solved denial.
Callout: the code has to come from the record. Selecting a diagnosis because it appears on the covered list, rather than because the provider documented it, is the pattern payers and auditors look for. The coder's job is to code what's documented. If what's documented doesn't meet the policy, the fix is a provider conversation or an ABN, not a different code.
Reading the remittance: CO-50 and its relatives
Medical necessity denials arrive with a small set of codes. CGS lists CO-50, CO-57, CO-151 and remark code N115 as the codes on its LCD and NCD denials.
| Code | Meaning (paraphrased) | Typical first step |
|---|---|---|
| CO-50 | Not deemed medically necessary by the payer; provider liable | Check the applicable NCD/LCD and article against the record |
| CO-151 | Payer judges the information doesn't support this many or this frequency of services | Check frequency limits in the policy |
| N115 (RARC) | The decision was based on a Local Coverage Determination | Open the named LCD and its article |
| PR-50 | Not medically necessary, but liability shifted to the patient | Confirm a valid ABN is on file |
The group code is the money question. CO means the provider absorbs the loss. PR means the patient can be billed, which on Medicare generally requires a valid Advance Beneficiary Notice.
Managing liability: ABNs and modifiers GA, GZ, GX and GY
When a provider expects Medicare to deny a service as not reasonable and necessary, the CMS ABN booklet requires an Advance Beneficiary Notice (form CMS-R-131) before the service if the provider wants to shift financial liability to the patient. The claim then carries a modifier that tells Medicare which situation applies.
| Modifier | Situation | What Medicare does |
|---|---|---|
| GA | Expected medical necessity denial; a required ABN was issued | Patient liable if denied |
| GZ | Expected medical necessity denial; no ABN issued | Line automatically denied, provider liable, no complex review |
| GX | Voluntary notice for a service excluded by statute rather than medical necessity | Informational |
| GY | Service statutorily excluded or not a Medicare benefit | Denied as non-covered |
Two rules keep ABNs defensible. They can't be routine: an ABN given to every patient for every service doesn't meet the requirement that the provider genuinely expects a denial. And they have to be delivered before the service, on the current form, with the specific reason the provider expects non-coverage.
Medicare Advantage now follows the same policies
Before 2024, Medicare Advantage (MA) plans had more room to apply their own medical necessity criteria. CMS's 2024 MA final rule narrowed that. Starting January 1, 2024, MA plans must comply with NCDs, LCDs and general Traditional Medicare coverage rules. They may use internal coverage criteria only when Medicare criteria aren't fully established, and those internal criteria must be based on current evidence and publicly accessible under 42 CFR 422.101(b)(6).
This matters for denial work in two ways. First, an MA denial that applies stricter criteria than the applicable NCD or LCD is worth challenging, citing the rule. Second, the same LCD-alignment checks you run for Traditional Medicare now apply to MA claims in the same jurisdiction. CMS's follow-up guidance also clarified that an MA plan relying on an LCD from outside the applicable service area is treated as using internal criteria.
Building medical necessity checks that hold up
A working prevention process has four layers, each owned by someone different.
| Layer | When | Check | Owner |
|---|---|---|---|
| Order entry | Before scheduling | Does the ordered service have an NCD or LCD in this jurisdiction, and does the reason for the order meet it? | Ordering provider, scheduling |
| Front end | Before service | If coverage is doubtful, issue an ABN; record which modifier applies | Patient access |
| Coding | After service | Code the documented diagnoses, then check them against the article's code groups for this CPT code, including dual-diagnosis rules | Coding |
| Pre-bill edit | Before release | Jurisdiction-aware edit against the current article version; frequency limits | Revenue integrity |
The order-entry layer prevents the most denials and is the one most organizations skip. In imaging, for example, the reason for exam on the order drives the diagnosis, which is why radiology report and order documentation decides most medical necessity outcomes before a coder sees the study.
The pre-bill layer is where most of the automation sits. It only works if the edit library is current and jurisdiction-aware, and if each hit goes to someone who can act on it. Our guide to building a pre-bill edit layer covers how to measure each rule's precision so medical necessity edits don't turn into work queues of false positives. For bundling-related denials that look similar on a dashboard but have a different fix, see NCCI edits and modifier 59.
Where AI-assisted coding fits
Matching a documented diagnosis to the right code group in the right jurisdiction's article is rule work, and software does it quickly. Deciding whether the documentation meets an LCD's clinical criteria isn't. Neither is deciding whether to issue an ABN.
MEDIQCODE's approach is AI-assisted coding with coder sign-off. The system surfaces the applicable policy and the record passages that bear on it, flags dual-diagnosis and frequency rules, and leaves the final code and any query to the coder. It doesn't choose a diagnosis to fit a policy, because that's the failure the audit finds.
Frequently asked questions
What is the difference between an NCD and an LCD?
An NCD is issued by CMS and applies in every Medicare jurisdiction. An LCD is issued by a Medicare Administrative Contractor and applies only in that contractor's jurisdiction, usually where no NCD exists or where an NCD leaves detail open.
Where are the covered ICD-10 codes for an LCD?
In most cases, in the companion Billing and Coding Article, not the LCD itself. The Medicare Coverage Database links each LCD to its articles. For DME MACs, CPT and HCPCS codes remain in the LCD.
Why was my claim denied when the diagnosis is on the covered list?
Common reasons are that the diagnosis is listed for a different procedure in the same article, the policy requires a second diagnosis, or the documentation doesn't support the diagnosis billed. Check the article's code groups for the specific CPT code you billed.
Do Medicare Advantage plans have to follow LCDs?
Yes, since January 1, 2024. MA plans must comply with NCDs, LCDs and general Traditional Medicare coverage rules, and may apply internal criteria only when Medicare coverage criteria aren't fully established.
Can I bill the patient after a CO-50 denial?
Not on Medicare unless a valid ABN was issued before the service and the claim carried modifier GA. CO-50 means the provider is liable.
This article is general coding and billing education, not a coverage or coding determination for any specific service. Coverage policies vary by jurisdiction and change often.