What you will learn
By the end of this topic, you should be able to distinguish FDA regulations, guidance and consensus standards; confirm whether FDA recognises a standard wholly or partly; choose between a declaration of conformity and general use; and connect standards evidence to the device, product code, risks and submission questions.
FDA encourages appropriate use of voluntary consensus standards
FDA-recognised consensus standards can make device evidence more consistent and support an efficient review. Conformance is generally voluntary unless a standard has been incorporated by reference into regulation. A recognised standard does not replace the FD&C Act, applicable 21 CFR requirements, special controls, guidance or the need to demonstrate safety and effectiveness for the proposed device.
A standard is useful when it addresses a defined requirement or review question for the selected device and submission. Recognition alone does not make the standard applicable.
MTL-302 — US FDA Medical-device Regulations: 21 CFR Overview explains the binding framework within which standards are used.
Start with classification, product code and pathway
Define intended use, indications for use, patient population, user, environment, technology and claims. Identify the classification regulation, product code, device class, submission pathway, predicate or De Novo strategy, applicable special controls and device-specific guidance. These determine the evidence questions that standards may help answer.
- Confirm the statutory device status and responsible FDA centre.
- Identify regulation number, product code and classification.
- Establish the 510(k), De Novo, PMA, IDE or other pathway.
- Review special controls, guidance, prior decisions and recognised standards associated with the product code.
- List the technological differences and device-specific risks that require evidence.
- Use the Q-Submission programme where the standards strategy or testing plan needs FDA feedback.
Check the FDA recognition record—not just the standard title
FDA's Recognized Consensus Standards Database is the current source for recognition status. Each record can identify the recognised edition, recognition number, extent of recognition, transition information, relevant product codes and a Supplemental Information Sheet. FDA may recognise all, part or none of a standard.
A standard can sometimes be used under FDA's general-use approach even when it is not recognised, but the submission cannot present it as the basis for an FDA declaration of conformity. Explain its relevance and provide adequate supporting information.
Use standards in one of several ways
Declaration of conformity
For an applicable FDA-recognised standard, identify the recognition number, edition, extent of conformity, deviations and supporting information required by FDA.
General use
Use a non-recognised or differently applied standard as a scientifically justified method, supplying enough information for FDA to assess it.
Complete performance standard
Where a recognised device-specific standard covers the relevant characteristics, conformity may answer a substantial part of the review question.
Partial method
Use selected clauses or test methods while identifying uncovered risks, claims, differences and supplementary evidence.
Do not claim complete conformity when exclusions, deviations, untested configurations or partial recognition apply. The declaration and submission narrative must match the actual evidence.
Typical standards families for FDA-regulated devices
The set depends on the product code and technology. Common candidates include ISO 14971 for risk management; IEC 62366-1 for usability engineering; IEC 62304 for software lifecycle processes; the IEC 60601 family for medical electrical equipment; the ISO 10993 family for biological evaluation; ISO 11607 for sterile-barrier packaging; ISO 15223-1 and ISO 20417 for information supplied; and cybersecurity standards such as ANSI/AAMI SW96 and IEC 81001-5-1 where recognised and applicable.
For the quality system, FDA's Quality Management System Regulation incorporates ISO 13485:2016 by reference, with FDA-specific provisions. Certification to ISO 13485 does not replace QMSR compliance or FDA inspection.
FDA's voluntary ASCA programme can increase confidence in qualifying test-laboratory results for eligible standards and scopes, including areas such as biocompatibility and basic safety and essential performance. Participation does not transfer the manufacturer's responsibility for the device.
Build a submission-oriented standards matrix
Map each standard to the review question it addresses—not merely to an engineering discipline. Record the product code or requirement, risk or technological characteristic, recognised edition and recognition number, clauses used, test article, method, acceptance criteria, deviations, evidence and submission location.
Regulatory basis
Classification, special control, guidance recommendation or submission question.
Standard status
Recognition number, edition, extent, transition and applicable clauses.
Device application
Configuration, accessories, environment, operating modes and worst case.
Evidence conclusion
Result, deviation, residual gap and relationship to safety and effectiveness.
Maintain the matrix with design inputs, risk controls and verification planning. Standards selected after testing often expose the wrong sample configuration, incomplete acceptance criteria or missing documentation.
Example: a connected infusion pump
A connected infusion pump may need recognised standards for electrical safety and essential performance, EMC, software lifecycle, usability, risk management, biocompatibility, alarms, cybersecurity, wireless coexistence and interoperability. Its 510(k) strategy must also compare intended use and technological characteristics with the predicate and address differences.
Passing IEC 60601 testing does not by itself demonstrate substantial equivalence. The submission must explain the tested configuration, essential performance, software and cybersecurity boundaries, alarm behaviour, use-related risks, network interactions and any differences from the predicate.
Use MTL-104 — Essential Performance and Safety Concepts, MTL-109 — Medical-device Cybersecurity and MTL-322 — FDA Interoperable Medical Devices for the connected evidence.
Present standards use clearly in the submission
- Identify each standard accurately on the appropriate submission forms and summaries.
- State whether it is FDA-recognised and provide the recognition number.
- Describe full or partial conformity, exclusions, deviations and adaptations.
- Provide the declaration of conformity and any information specified by FDA.
- Identify test laboratories, accreditation or ASCA status where relevant.
- Describe the test article, software version, accessories, operating modes and worst-case configuration.
- Link results to risks, special controls, predicate differences and acceptance criteria.
- Supply supplementary data where the standard does not fully answer the review question.
The reviewer should be able to understand what the standard establishes without guessing what was tested or how its result supports the requested decision.
Maintain recognition and evidence through change
FDA recognition records, editions and transition periods change. Monitor the database and assess revised standards against products in development and on the market. Changes to the device, software, materials, suppliers, manufacturing, intended use or labelling may also invalidate assumptions or require new testing.
Use MTL-129 — Configuration and Change Management and MTL-321 — FDA Changes to Existing Devices and Software to connect standards maintenance to change assessment and submission decisions.
Common misconceptions
“FDA recognition makes a standard mandatory.”
Generally no. Recognition enables appropriate regulatory use and declarations of conformity; applicability still depends on the device and requirement.
“A declaration of conformity means no supporting information is needed.”
No. FDA may require information specified in the recognition record, and device-specific gaps or deviations still need evidence.
“The newest published edition is automatically the FDA edition.”
No. Check the recognised edition and transition details in the current database.
“Using standards replaces predicate or benefit-risk reasoning.”
No. Standards evidence must be integrated into the pathway-specific safety, effectiveness or substantial-equivalence argument.
Practical checklist
- Define intended use, product code, class and pathway.
- Identify special controls, guidance and device-specific review questions.
- Search the current FDA recognised-standards database.
- Review the exact edition, recognition number, extent and transition.
- Choose declaration-of-conformity or general-use treatment deliberately.
- Map standards to risks, differences, tests, evidence and submission sections.
- Control test-article configuration, deviations and supplementary evidence.
- Consider ASCA where an eligible scope adds value.
- Monitor recognition and product changes through the lifecycle.
Use recognition precisely, not decoratively
- FDA regulations and pathway-specific requirements remain the controlling framework.
- Recognition status, edition and extent must be checked in the current database.
- Standards can be used through declarations of conformity or as justified general-use methods.
- Partial conformity and deviations must be explicit.
- Standards evidence must answer device-specific review questions and risks.
- Recognition and evidence need active lifecycle maintenance.