Your Diagnosis Is Not on the NCD’s List. Does That Mean Medicare Will Not Cover It?

A coverage check that finds nothing looks like a clean result and is not one. When a diagnosis does not turn up against a National Coverage Determination, at least four different situations produce the same empty screen, and they have different consequences.

The code may be absent from a list CMS did publish. A list for that policy may never have been published at all. A mapping may have existed and been terminated before the date of service. Or the policy may simply not be the one that governs the service. None of those is a finding of non-coverage, and treating any of them as one is the failure this question exists to prevent.

1. Establish which National Coverage Determination you are asking about. A diagnosis checked against a policy nobody selected answers a question nobody asked.
2. Check whether a published diagnosis code list exists for that policy. Most NCDs have none; the lists that exist come from CMS’s laboratory NCD code list.
3. Where the code appears, read the resolution CMS assigned it rather than treating any appearance as support.
4. Where it does not appear, do not infer non-coverage. Read the policy text.
5. Check the date. A mapping CMS terminated does not govern a later date of service, and its end date is a published fact you can quote.

Listed and supported. The policy’s published list identifies the diagnosis under CMS’s coverage resolution. That is what CMS published. It is not a statement about how a particular claim will be handled, and the documentation requirements in the policy still apply.

Listed under a different resolution. The list identifies the code as denied, or as not supporting medical necessity. This is a definite negative rather than an absence, and it is far more informative than silence.

No list held. The policy is a real NCD, but no published diagnosis code list for it exists in the loaded data. The honest result names that gap rather than reporting the diagnosis as absent from a list that was never consulted.

Terminated mapping. CMS listed the diagnosis under the policy and published the day the mapping ended. A date of service after that day is outside the window, and the correct report is that the mapping ended on that date — not that CMS never listed the code.

• Reading absence as non-coverage. A code’s absence from a published list does not establish non-coverage by itself.
• Reading no applicable policy as coverage. Failure to identify an applicable policy does not establish coverage either. The two errors are mirror images.
• Assuming a policy. Checking a diagnosis against whichever NCD is nearest to hand produces an answer to a different question.
• Forgetting Local Coverage Determinations exist. An LCD issued by a Medicare Administrative Contractor may govern the service and sits entirely outside a national policy check.
• Ignoring a termination date. A mapping CMS ended is not a mapping CMS never made.

A published code list answers one narrow question: whether CMS named this diagnosis in this policy, and under which resolution. It does not carry the policy’s documented coverage requirements, its frequency limitations, or its conditions of coverage. Those live in the policy text, and they are frequently the part that decides a claim.

Where a list shows support, the record still has to satisfy what the policy asks for. Where a list shows nothing, the record and the policy text together are the answer, not the empty result.