Someone hands you a copy of ISO 10993-1 or IEC 60601-1 and says, more or less, “make sure we’re compliant.” The ask sounds simple and is not, because a recognized consensus standard is not a checklist you satisfy — it is a document with its own internal structure, its own binding and non-binding sections, and its own relationship to FDA that most people never learn to read closely.
What “recognized” means, and what it does not
Section 514(c) of the Federal Food, Drug, and Cosmetic Act gives FDA the authority to recognize, in whole or in part, standards developed by outside bodies — ISO, IEC, AAMI, and others — as a basis for meeting certain requirements for medical devices. FDA maintains a searchable database of exactly what it currently recognizes, and the entry for any given standard is the actual scope of recognition: sometimes the full document, often a specific edition, occasionally with conditions or exceptions FDA has attached that narrow what a declaration of conformity to that standard will cover. Citing “ISO 10993-1” from memory is not the same as checking what FDA’s recognition entry for ISO 10993-1 actually says today, and the gap between those two is where declarations get challenged.
Reading the standard itself, not just citing it
A consensus standard is organized the way a regulation is: most of its substance sits in normative sections, written in the same “shall” language a regulation uses for a binding requirement, while informative annexes explain intent or offer guidance without creating an obligation on their own. Skimming a standard for its scope statement and assuming the rest follows is how people end up declaring conformity to sections they never actually applied. The standard also will not tell you which of its own clauses are relevant to your specific device — that judgment is yours to make and document, the same kind of risk-based call examined in how to explain a regulatory decision. And because standards revise on their own schedule, the edition FDA recognizes today is not guaranteed to be the edition on your shelf; that mismatch is one of the most common, and most avoidable, gaps a reviewer finds.
- Confirm the exact edition FDA currently recognizes — not just the standard’s family name.
- Check the recognition entry for conditions or limitations attached to that edition.
- Separate normative clauses from informative annexes before promising conformance to the whole document.
- Keep the underlying test data even though a declaration does not require submitting it — FDA can ask for it.
- Note, in writing, any clause you deliberately did not apply, and be ready to say why.
Two habits that undermine a declaration of conformity
Citing the standard family without the recognized edition
“We conform to IEC 60601-1” is not a claim a reviewer can evaluate. Which edition, which amendments, and whether FDA’s recognition of that edition carries any conditions all have to be answered before the citation means anything.
Treating the declaration as though it replaces the testing
A declaration of conformity is a statement that the testing was done and met the standard — it is not a substitute for having actually run it. Reviewers can and do ask for the underlying data behind a declared clause.
Sources & further reading
- 21 U.S.C. § 360d(c) (FD&C Act Section 514(c)) — recognition of consensus standards fda.gov
- FDA Recognized Consensus Standards Database — the versions FDA currently accepts accessdata.fda.gov
- Regulatory Academy — Building the 510(k): eSTAR, Screening, and the Testing Burden regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal or regulatory advice.
