How do you tell whether a document is actually a rule?
A document that explains a rule is not the rule. The test is public comment: a legislative rule must be published for notice and comment, while interpretative rules and policy statements are exempt. Guidance that binds nobody can still decide your claim, and knowing which you hold changes what you can argue.
Every denial letter names a document. In the letters I read, usually a number, sometimes a title, occasionally both.
That document is treated as the reason. Whether the document binds anybody is a different question, and the letter almost never answers it.
Here is the part that decides what happens next. Some of what an agency publishes has to be argued with. Some of it only has to be pointed at.
A daughter reads the paragraph explaining why the answer was no. An adviser works out whether an appeal has anywhere to go. Each of them is holding a document number and a decision resting on it. These pages are written for them.
Contents
- What does the document itself tell you about its own standing?#
- How do you tell a national coverage determination from a local one?#
- If a document does not bind, why does your plan follow it?#
- What is a claim worth if its only source is guidance?#
- What do you do when you cannot tell which one you are holding?#
What does the document itself tell you about its own standing?#
More than most readers expect. Less than the letter implies.
Start with who issued it. An agency, a contractor working for an agency, or Congress. Three authors, three weights. The author is printed on the paper, the way a letter tells you who signed it before it tells you anything else.
Then look at what the document is deciding. A coverage decision, an instruction to staff, an answer to a common question. Those are three different acts wearing one format.
None of that is hidden. It is skipped, because the letter has already told the reader what the document means, and going behind a letter takes a reason.
One more thing sits on the page and gets read past. The date. A document reissued last year and a document unchanged since 2015 look identical in a citation, and only one of them describes the programme somebody is dealing with now.
The habit worth building is small. Before arguing with what it says, spend a minute on what it is.
How do you tell a national coverage determination from a local one?#
By the issuer and the reach. Both are stated in the regulations.
A national coverage determination is “a decision that CMS makes regarding whether to cover a particular service nationally.” One author, the whole programme.
Its local counterpart is different. The regulations call it “a decision by a fiscal intermediary or a carrier” about whether to cover a service “on an intermediary-wide or carrier-wide basis.” A contractor, one region.
Their names sit one word apart. National, local. The documents look alike, arrive through the same database and get cited in the same sentence of a denial letter.
They do not carry the same force, and the direction matters more than the difference. A national determination binds the judge hearing your appeal outright. A local one does not bind that judge, but takes substantial deference and a written reason to depart from. Which one binds, and why, is its own subject.
Getting that backwards is expensive in one specific way. A reader who thinks a national determination merely gets weight will argue that the judge should set it aside. That is the one argument unavailable.
The opening left is narrower. That it does not apply to this case, or that it was applied wrongly. It is like arguing a speed limit sign belongs on another street.
If a document does not bind, why does your plan follow it?#
Because the people between the page and the decision each have a reason to.
The Government Accountability Office states the formal position plainly. “Federal regulations are legally binding, while guidance documents typically are not.” True, and incomplete on its own.
Its next line adds the half that matters here. Guidance “can show an agency’s interpretation of regulations and drive its actions.” The agency acts on its own reading, and the reading lives on the page.
Medicare writes the mechanism down. A local coverage determination does not bind the judge hearing an appeal. That judge must still give it substantial deference, and must explain in writing any decision not to follow it.
Read that twice. Not binding, and departing from it costs a written justification. A document can constrain a decision without ever binding anyone.
So the page binds nobody and shapes everything.
Both halves are true. A reader told only the first will misjudge what they are up against.
What is a claim worth if its only source is guidance?#
Less than the letter in the envelope suggests, and more than nothing.
Picture what is actually on the desk. A denial letter, a claim number, and a printed page from a manual or a contractor bulletin. If that page is the only thing behind the decision, the decision rests on an interpretation. Not on a requirement. Which is not the same as the decision being wrong. The ground under it is softer than the quoting sentence sounds.
That changes what can be argued. A requirement is argued on its terms. Does it reach this patient, this service, this date, and was it applied correctly. An interpretation can also be argued on its standing. Whether the reading is right, and whether the regulation behind the page says what the page claims.
There is one more move, and it is the one most writing on appeals leaves out. Ask the page what statute or regulation it is interpreting. Every piece of guidance points at something.
A manual page explains a regulation. A policy statement explains a statute. What it explains is where the actual requirement lives, and whether the date has passed.
Guidance that cannot name what it interprets is worth asking about twice.
What do you do when you cannot tell which one you are holding?#
Say so, and then ask the party that used it.
Some documents genuinely resist the test. Old material, reissued material, a page that reads like a rule and cites none. Unclear is the honest answer. Unclear is not guidance.
Ask the plan or the contractor which document it relied on and what that document is. The answer exists on a record somewhere. Asking costs nothing. Guessing leaves the question open.
Until the answer arrives, treat the standing as unknown rather than settled. An unknown is a live question. A guess is a closed one, and a closed question is harder to reopen than an open one.
Nobody is served by pretending. It is the same discipline as a claim from a tool. The confident version and the accurate version part company at the point where somebody stops checking.
A daughter reading a denial letter at midnight will not run a legal analysis. She can ask one question. What is this document, and did anyone get to comment on it.