Usage Examples
- The use-related risk analysis promoted four tasks to critical, so the validation protocol grows by four scenarios.
- We have two distinct user populations, which means 30 participants in HF validation, not 15.
- That was a formative evaluation, so it cannot be submitted as our human factors validation study.
What is Human Factors Engineering (HFE)?
Human Factors Engineering is the device design discipline that shapes the user interface so use errors capable of causing harm are eliminated or reduced, then proves it by testing critical tasks with representative users under simulated use.
Human Factors Engineering exists because use error cannot be forecast the way component failure can. FDA's guidance states the problem directly: probability is very difficult to determine for use errors, and many use errors cannot be anticipated until device use is simulated and observed. Human Factors Engineering therefore substitutes observation for prediction, ranking hazards by severity of harm.
Human Factors Engineering covers the entire device user interface: hardware controls, displays, software, packaging, labels and labeling, and training. Human Factors Engineering does not cover whether the therapy itself works, and it does not replace the risk management file. Its boundary is use, meaning whether the intended users, in the expected environment, can run the critical tasks without causing harm.
Human Factors Engineering is applied as a sequence, not a single study. Preliminary analyses such as task analysis, FMEA, fault tree analysis, and formative evaluation identify the critical tasks. Risk controls then eliminate or reduce those hazards. Only afterwards does Human Factors Engineering run the validation test, with at least 15 representative participants per distinct user population, and close with a residual use-related risk argument.
Not to be confused with
- Usability testing
- usability testing is one method inside HFE, and most of it is formative work aimed at improving a design that is still moving. HFE is the whole chain: critical task identification, risk control, validation, residual-risk argument. A stack of formative sessions is not an HF validation study.
- ISO 14971 risk management
- risk management covers every hazard class, including electrical, mechanical, and biological. HFE covers only use-related hazards, and it builds on the ISO 14971 risk analysis rather than running beside it. FDA's guidance derives critical tasks from that risk analysis, so a weak risk file produces a weak HFE scope.
- Design validation
- design validation asks whether the finished device meets user needs and intended use across the whole design. HF validation asks only whether intended users can perform the critical tasks without harmful use error. HF validation is an input to design validation, not a synonym for it.
- HF validation testing
- validation testing is the last step of HFE, not the whole of it. It runs after use-related hazards have already been designed out, and its job is to demonstrate the controls hold. Running it to discover problems makes it a formative evaluation, whatever the protocol is called.
The operative obligations sit in FDA's 2016 final guidance, carried into the quality system through design and development.
What you must do
- 1Identify and categorize critical tasks by the severity of the harm a use error could cause, working from the risk analysis rather than from intuitionApplying Human Factors and Usability Engineering to Medical Devices, Section 6.1
- 2Eliminate or reduce every identified use-related hazard, by designing it out where possible, before the human factors validation test beginsApplying Human Factors and Usability Engineering to Medical Devices, Section 7
- 3Recruit a minimum of 15 test participants, and at least 15 from each distinct user population, all representative of the intended usersApplying Human Factors and Usability Engineering to Medical Devices, Section 8.1.1
- 4Include every critical task from the preliminary analyses in the validation test, grouped into use scenarios described in the protocol, with successful performance defined before testing startsApplying Human Factors and Usability Engineering to Medical Devices, Section 8.1.2
- 5Run the HFE program inside design and development, which for class II, class III, and the named class I devices means Clause 7.3 of ISO 13485 as incorporated by the QMSR21 CFR 820.10(c)
Common mistakes
Running HF validation to find problems
validation exists to demonstrate that hazards already controlled stay controlled, and FDA expects use-related hazards to be eliminated or reduced before the test starts. A critical-task failure discovered in validation forces redesign plus a retest, which adds a full study cycle to a submission timeline that was usually built assuming one.
Testing 15 participants when the device has two user populations
the floor is 15 per distinct population, and FDA treats populations as distinct when their characteristics affect device interaction or their tasks differ. A device used by nurses and by patients at home needs 30. A single 15-participant study cannot be argued away in an interactive review; it has to be re-run.
Treating the priority-devices list as settled policy
the List of Highest Priority Devices for Human Factors Review was issued as a draft on 3 February 2016 and was still listed as draft in FDA's guidance database as of February 2026. Scoping an HFE program by whether the device appears on that list, instead of by the use-related risk analysis, leaves the deficiency exactly where the reviewer will look.
When This Matters
- The use-related risk analysis promoted four tasks to critical, so the validation protocol grows by four scenarios.
- We have two distinct user populations, which means 30 participants in HF validation, not 15.
- That was a formative evaluation, so it cannot be submitted as our human factors validation study.
Frequently Asked Questions
FDA recommends a minimum of 15 participants, and at least 15 from each distinct user population. FDA views populations as distinct when their characteristics would likely affect their interactions with the device or when their tasks differ, so a device used by clinicians and by lay caregivers needs 30 participants, not 15.
Related Use Cases
- Medical Devices Use Cases
Prepare 510(k), PMA, and De Novo submissions with AI-guided pathway selection
- Consulting Use Cases
Manage 15+ client programs from one dashboard with per-client workspaces and tracking
- Regulatory Affairs Workflows
Cut regulatory intelligence tracking from 10+ hours/week to automated, real-time alerts
- Quality/QA Workflows
Track GxP regulation changes and enforcement trends
Related Regulatory Intelligence
Related Actions
Sources & References
- FDA Guidance - Applying Human Factors and Usability Engineering to Medical Devices (Final, 3 February 2016)
- FDA Guidance - Application of Human Factors Engineering Principles for Combination Products: Questions and Answers (Final, 7 September 2023)
- FDA Guidance - List of Highest Priority Devices for Human Factors Review (DRAFT, 3 February 2016)
- 21 CFR 820.10 - Requirements for a quality management system
- Medical Devices; Quality System Regulation Amendments - Final Rule (2 February 2024)
