IEC 62366 vs. FDA human factors engineering
IEC 62366-1:2015 + AMD1:2020 ↔ FDA human factors engineering guidance
The short answer
IEC 62366-1 (usability engineering) and the FDA human factors engineering (HFE) guidance pursue the same goal — safe operability by mitigating use-related risk — with different vocabulary and emphasis. 62366-1 is process-centric; the FDA HFE guidance is activity/method-centric. Both feed use-related risk into risk management and rely on formative testing followed by final validation. They are closely aligned but not interchangeable.
Terminology bridge
| IEC 62366-1 | FDA HFE |
|---|---|
| Usability engineering | Human factors engineering (HFE) |
| Summative evaluation | Human factors validation testing |
| Formative evaluation | Formative evaluation / studies during development |
| Use specification | Use specification / intended use & use environment |
| Hazard-related use scenarios | Critical tasks / hazard-related use scenarios |
Where they differ
- Emphasis: 62366-1 describes a process; the FDA guidance emphasises activities and methods
- Terms: the FDA does not use "summative" — it speaks of "human factors validation testing"
- Scope of applicability: 62366-1 is international/EU-oriented; the FDA HFE guidance is US-specific
What is the same
Both aim to identify and mitigate use errors with harm potential, both connect usability to risk management, and both rely on a formative phase followed by a final validation.
Frequently asked questions
Does applying 62366-1 automatically meet FDA expectations?
Not automatically. The processes are closely aligned and can largely be documented together, but the FDA has its own expectations (e.g. on critical tasks and validation sampling). Plan a deliberate mapping rather than assuming identity.
Can I keep one file for both?
In practice, yes — many manufacturers keep one usability/HFE file addressing both requirement sets. The terms should be cleanly mapped, not merged.