What “Medical Necessity” Means Operationally
Clinically, necessity is judgment; operationally, it is a checklist. Payers adjudicate necessity against written criteria: Medicare’s national and local coverage determinations (NCDs/LCDs) with their covered-indication lists, and commercial payers’ clinical policies with criteria per service. A necessity denial rarely means the payer thinks care was wrong — it means the claim’s documentation did not demonstrate the policy’s checklist.
Why These Denials Happen
- Diagnosis-procedure mismatch: the billed diagnosis is not on the policy’s covered-indication list, or lacks the specificity the policy requires
- Missing criteria elements: the policy requires documented conservative-therapy failure, findings, or measurements the note never states
- Template documentation: cloned notes that assert nothing specific enough to satisfy anything
- Frequency and interval rules: covered services exceeding policy-defined frequencies without documented justification
Prevention: Document to the Policy
For services with known necessity scrutiny (imaging, procedures, injections, testing), the policy text is available before the service — and documentation built to its checklist prevents the denial entirely: the qualifying indication stated with required specificity, criteria elements (conservative care, findings, durations) explicitly documented, and orders connecting symptoms to services. Practices that maintain policy-crib sheets for their top scrutinized services convert this from provider burden into template discipline.
Appeals: Argue From Their Text
Necessity appeals win by demonstration, not indignation: quote the payer’s own policy criteria, then map the clinical record to each element — criterion by criterion, with record citations. Attach the relevant records rather than summarizing them. Where the denial misapplied the policy (criteria met but ignored), say so specifically; where care fell outside policy but was clinically justified, invoke the exceptions process and peer-to-peer review paths. Form-letter appeals lose because they argue nothing.
The Coding Connection
Necessity denials often masquerade as coding problems and vice versa: an unspecific diagnosis code starves a justified service of its policy match. Coding review for scrutinized services should verify the diagnosis carries the policy-required specificity — the difference between a covered indication and a denial can be one character of ICD-10 detail supported by the note.
Practical Checklist
- Policy crib sheets maintained for the practice’s top scrutinized services
- Documentation templates carrying policy criteria elements
- Diagnosis specificity verified on scrutinized claims
- Appeals built criterion-by-criterion against policy text
- Peer-to-peer and exception paths used where policies allow
- Necessity-denial patterns reviewed for prevention monthly
Frequently Asked Questions
The service was clearly appropriate — how can it be “not necessary”? The denial speaks policy, not medicine: it asserts the claim did not demonstrate the written criteria. Appropriate care documented generically loses to the checklist; the fix is demonstration — in documentation before the service, or in the appeal after.
Where do we find the criteria payers use? Medicare’s are public in the coverage database (NCDs and LCDs); major commercial payers publish clinical policies on provider portals. For any service drawing repeated necessity denials, pulling the specific policy is the first move — you cannot document to a checklist you have not read.