An EUA lasts only as long as its emergency does

This blog has already covered the emergency-use and treatment-use provisions inside 21 CFR Part 812 — both built around a single trial, a single sponsor, and a single subject or small group whose access an investigator or sponsor arranges directly. Section 564 of the FD&C Act, codified at 21 U.S.C. 360bbb-3, is a different instrument answering a different problem: it lets FDA authorize an unapproved medical product, or an unapproved use of an approved one, across an entire population, once the government has separately declared that an emergency justifies it. An EUA tracker built on the assumption that it's just Part 812's emergency use scaled up has confused two mechanisms that don't share a trigger, a scope, or an end date.

The declaration comes first, from outside FDA

Section 564(b) makes FDA's own authorization power conditional on a step FDA doesn't take itself: before an EUA can issue, the Secretary of Health and Human Services has to declare that circumstances exist justifying emergency use, and that declaration rests on a determination made elsewhere in government — from the Secretary of Homeland Security on a domestic threat, the Secretary of Defense on a military one, or HHS's own finding of a public health emergency or a significant potential for one. FDA's authorization authority under 564(c) doesn't exist in the abstract; it activates only once that separate declaration is in place, which makes the declaration itself the first artifact an EUA file has to hold, not an afterthought to the product review.

Four things FDA has to conclude, not just believe

Once a declaration is in effect, 564(c) sets out what FDA has to conclude before authorizing a specific product: that the agent named in the declaration can cause a serious or life-threatening disease or condition; that, based on the totality of the scientific evidence available, it's reasonable to believe the product may be effective in diagnosing, treating, or preventing that disease or condition; that the product's known and potential benefits outweigh its known and potential risks; and that no adequate, approved, and available alternative exists. “Reasonable to believe” is doing real work in that second criterion — it's a lower evidentiary bar than the reasonable-assurance standards a 510(k) or PMA review applies, built for a moment when waiting for that fuller evidence isn't itself a safe option.

Not a lighter HDE, and not the same population problem

A Humanitarian Device Exemption also trades away part of the ordinary effectiveness standard, but for the opposite reason an EUA does — an HDE exists because a condition affecting no more than 8,000 people a year can't generate the evidence a full PMA review would need, a population problem that holds true whether or not any emergency exists. An EUA's lower bar exists because a declared emergency has made waiting for that fuller evidence itself unacceptably risky, for a population an emergency declaration doesn't cap by size at all. A device could qualify for neither, either, or both, but the file has to keep the two rationales separate, because they answer different questions FDA is asking.

The authorization has no shelf life of its own

An EUA doesn't carry an independent expiration date the way a device clearance does. Its duration is tied to the declaration that made it possible in the first place: the authorization remains in effect only as long as the underlying section 564(b) declaration does, and it ends — automatically, or by FDA's own revocation — once that declaration terminates or the statutory criteria supporting it no longer hold. A tracker that files an EUA next to a 510(k) clearance and gives both an indefinite “active” status has missed the one field that actually distinguishes them: a clearance doesn't sunset when a government declaration does, and an EUA always does.

Where this meets the file

An EUA tracking record needs the underlying section 564(b) declaration cited by its own date and source, the specific 564(c) findings FDA made for the product, and a status field that reads from the declaration's own standing rather than a fixed expiration date — because the authorization's end is a fact about the emergency, not a fact the product file controls on its own. An EUA readiness worksheet built around these four elements is previewed in the launch catalog. If your program has run an EUA file and tracks the declaration dependency differently, the shelf takes that correction directly.