The guidance that went back to draft

A guidance document finalized in 2018 reads, to a monitoring pipeline and to a person, like a closed question. FDA answered it once, in writing, and the file moves on. The Q&A guidance behind a narrow safe harbor in Section 502(a) stayed closed that way for eight years — until FDA reopened the same document this June, not as an update, but as a draft.

A safe harbor with named conditions, not a blank check

Section 502(a) of the FD&C Act, at 21 U.S.C. § 352(a), is the misbranding statute drugs and devices share. Buried inside it is a proviso Congress built for one specific audience and one specific kind of claim: a manufacturer’s health care economic information — cost, comparative-value, and outcomes data — shared with a payor, a formulary committee, or a similarly credentialed entity making a coverage decision, is not automatically “false or misleading” just because it goes beyond the label. The safe harbor dates to Section 114 of the 1997 FDA Modernization Act and was widened by Section 3037 of the 2016 21st Century Cures Act, which extended it to information tied to an unapproved use and broadened who counts as the audience. It is narrow on purpose: a specific claim, to a specific reader, resting on competent and reliable evidence — not a general license to promote off-label.

One statute, two guidances, eight years apart

FDA answered the practical questions — what counts as HCEI, who counts as a payor, what a manufacturer has to disclose alongside it — in a final Q&A guidance published in June 2018. That document has sat as the field’s working answer key since. On June 3, 2026, FDA published a revised draft of the identical guidance, reopening the same questions for comment. The window closed August 3, 2026, and as of this writing FDA has not yet posted a final version to replace it — which means the 2018 answers are still the only final ones in force, on a document FDA itself has already told the public it is reconsidering.

A final guidance answers a question as of the day it was written. It does not promise the answer will still be FDA’s the next time someone reads the document.

What the pipeline actually did with it

FDA Radar’s Federal Register feed ingested the June notice the same way it ingests every device-relevant document: the title carries the word Device — word-bounded, not a substring match — so the filter kept it, and the title’s own “Guidance for Industry; Availability” phrasing categorizes it as FDA Guidance. A second structural check reads “Revised Draft Guidance” in the same title and sets the record’s own guidance_stage fact to Draft. Nothing about that classification required a human, or a model, to notice that this particular draft revises an eight-year-old final guidance rather than introducing a new topic — the field says Draft because the title says Draft, and the history behind it is a fact a reader has to bring themselves.

The practice

A guidance document’s legal weight doesn’t move when it gets revised — final or draft, it still isn’t a rule, and neither status binds FDA or a manufacturer the way a regulation would. What moves is the working answer a compliance or medical-affairs team relies on day to day. A payor-communications policy built on the 2018 Q&A now rests on text FDA has already reopened once; the practice is watching for the eventual final revision rather than assuming the 2018 version is the last word, and reading what changes between the two documents before assuming either one settles a specific communication. This describes how one safe harbor and one guidance history work, regulatory intelligence and method, never a determination about whether any specific communication qualifies for it — that is a question for the professionals who own the file.