Does every medical device need a summative usability evaluation?

Not every device requires a formal summative evaluation, but FDA's guidance requires documented justification if one is not conducted. For devices where use errors could cause serious harm, a summative evaluation is effectively expected. For very simple devices with minimal user interaction risk, a risk-based justification may be acceptable. The decision must be documented and defensible.

What is the difference between formative and summative evaluation?

Formative evaluations are conducted during development to identify and fix problems. They are iterative and can be informal. Summative evaluations are conducted after the design is substantially mature to generate objective evidence for the FDA submission. Summative evaluation results document what use errors occurred, whether they caused harm, and whether the device is safe and effective to use. Formative evaluations improve the design; summative evaluations confirm it.

Who qualifies as a "representative user" for a summative evaluation?

A representative user is someone who matches the intended user population in relevant characteristics: clinical training level, device familiarity, physical and cognitive capabilities, and relevant experience. For a device intended for use by trained nurses, participants must be nurses with relevant training levels. For a device intended for patient self-use, participants must be lay users without clinical training. Using more skilled or knowledgeable participants than the intended users produces optimistically biased results.

Does HFE documentation go in the 510(k) submission?

Yes. FDA expects an HFE report or HFE summary as part of most 510(k) submissions for devices where use errors could cause serious harm. The submission should describe the HFE process, the summative evaluation design, and the results, and should explain how residual use errors have been mitigated or accepted as part of the risk management process.

How does HFE connect to risk management under ISO 14971?

The connection is required, not optional. Use errors identified in the HFE process that have potential for patient harm must be entered into the risk management file (ISO 14971). Risk controls applied to those hazards (design changes, warnings, protective measures) must be documented and their effectiveness confirmed. The summative evaluation then provides evidence that the risk controls are effective in actual use. An HFE program that operates independently of risk management is incomplete.

Is IEC 62366 mandatory for FDA submissions?

IEC 62366-1 is a voluntary consensus standard recognized by FDA. Compliance is not mandatory. However, the standard provides a widely accepted framework for demonstrating conformance with FDA's HFE guidance, and most device programs use it for that reason. FDA's 2016 HFE guidance is the binding reference; IEC 62366-1 is the implementation framework most commonly used to meet it.

Human Factors Engineering for Medical Devices: IEC 62366 and FDA Usability Requirements

Direct answer: Human factors engineering (HFE) for medical devices is a structured process of studying how intended users interact with a device, identifying potential use errors, and testing the device to confirm that those errors are either impossible or tolerable under actual use conditions. FDA requires HFE documentation for most 510(k) and PMA submissions. The primary standard is IEC 62366-1 (usability engineering for medical devices). As of July 2026, FDA's primary guidance document on this topic is "Applying Human Factors and Usability Engineering to Medical Devices" (2016), which remains in effect.

Use errors can cause serious harm. Insulin pump dosing errors, infusion pump programming errors, automated external defibrillator pad misplacement, home oxygen equipment misassembly. The FDA has documented many adverse events and recalls that trace to design decisions that made it easy for trained professionals, caregivers, or patients to make mistakes with their devices. Human factors engineering exists to find those failure modes before a patient does.

For device founders, HFE is not an add-on that happens near the end of development. It is a design input. What you learn from user research in the first months of development should shape the physical form, the display layout, the alarm logic, and the instructions for use. Starting HFE late is one of the most common reasons device programs slip their 510(k) timelines.

What Is Human Factors Engineering?

Human factors engineering, also called usability engineering or ergonomics in some contexts, is the application of knowledge about human behavior, capabilities, and limitations to the design of equipment and environments. In medical devices, HFE focuses on the interaction between the device and its intended users in the intended use environment.

The term "use error" is precise in the HFE context. A use error is an action or omission by a user that produces an unintended result, and that could have been prevented by better design. It is distinct from device malfunction (a failure of the device itself) and from misuse (use outside the device's intended purpose). HFE addresses use error.

The Regulatory Framework: FDA and IEC 62366

FDA's primary HFE guidance is "Applying Human Factors and Usability Engineering to Medical Devices," finalized February 2016 (https://www.fda.gov/media/80481/download). It describes FDA's expectations for HFE in premarket submissions and covers both 510(k) and PMA pathways.

The international standard is IEC 62366-1:2015 + AMD1:2020, "Medical devices: Part 1: Application of usability engineering to medical devices." FDA recognizes IEC 62366-1 in its recognized standards database (https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfStandards/search.cfm). Conformance with IEC 62366-1 is voluntary, but it provides a widely accepted framework for demonstrating that FDA's HFE guidance requirements have been met.

An important nuance: FDA's 2016 guidance and IEC 62366-1 are not identical. Where they differ, FDA's guidance reflects FDA's current regulatory expectations, and manufacturers should understand both. In practice, most U.S.-bound device programs use IEC 62366-1 as the structural framework and cross-reference it against FDA's guidance to catch any gaps.

Who Must Submit HFE Documentation to FDA?

FDA's guidance states that HFE/usability engineering is expected for devices where use errors could result in serious harm to the user or others. In practice, this covers the vast majority of Class II and Class III devices.

FDA does not enumerate an exhaustive list of device types that require HFE documentation. Instead, it applies a risk-based principle: if a use error with the device could cause serious harm, HFE documentation is expected. FDA has been explicit that it applies this expectation across a broad range of devices, from surgical instruments to in vitro diagnostic (IVD) devices to connected software applications used in clinical settings.

For 510(k) submissions, FDA's "Human Factors Studies and Related Clinical Study Considerations in Combination Product Design and Development" guidance (2016, https://www.fda.gov/media/89893/download) and the primary HFE guidance together define what the submission must contain.

The HFE Process: From Analysis to Summative Evaluation

The HFE process, as described in FDA's guidance and IEC 62366-1, follows a defined sequence of activities. This is not a rigid waterfall, but the core activities must occur in the right order.

Step 1: Intended Use and User Analysis

The starting point is a clear description of the intended use, intended users, and intended use environments. "Intended users" must be specific: trained clinical professionals, lay caregivers, patients with specific conditions, pediatric patients, older adults who may have age-related sensory, cognitive, or dexterity considerations. The broader the user population, the more diverse the HFE program must be.

The use environment matters too. A device used only in ICUs by trained nurses has a different risk profile than the same device used at home by patients without clinical training. Environmental stressors, distractions, lighting conditions, and time pressure all affect use error probability.

Step 2: User Interface Description and Use Scenarios

The user interface of a device is not just the screen. FDA's guidance defines it broadly: all components of the device with which users interact, including controls, displays, packaging, labels, and instructions for use. Each of these elements is subject to HFE analysis.

Use scenarios describe how users will interact with the device in normal use and under foreseeable misuse conditions. High-risk use scenarios are those where a use error could cause serious harm.

Step 3: Known Problems and Preliminary Analysis

Manufacturers must review known problems and use errors associated with similar predicate devices and with similar use scenarios from the literature. FDA expects manufacturers to consult MAUDE (the FDA adverse event database, https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfmaude/search.cfm) and other sources to identify use-error patterns relevant to their device type.

Step 4: Formative Evaluations (Iterative Testing During Development)

Formative evaluations are usability tests conducted during design and development to identify use errors and redesign the device to eliminate or mitigate them. They are iterative: identify a problem, redesign, test again. Formative evaluations are not submitted to FDA in the same level of detail as summative evaluations, but FDA expects that they occurred and that the summative evaluation reflects a mature, tested design.

Common formative evaluation methods include cognitive walkthroughs, expert reviews (heuristic evaluations), early prototype testing with representative users, and contextual inquiry in the use environment.

Step 5: Summative Evaluation (The Critical FDA-Facing Test)

The summative evaluation is the formal usability study that provides the objective evidence that the device user interface can be used safely and effectively. It must be conducted with representative users (a term of art, not a synonym for "convenient volunteers"), in a simulated use environment that reflects actual use conditions, performing the critical tasks identified in the HFE analysis.

FDA's guidance provides specific direction on summative evaluation design, including:

The study must include participants from all intended user groups
Tasks must include all safety-critical tasks
The test environment must simulate actual use conditions
Results must include use errors observed, root cause analysis, and whether the error could cause harm

The summative evaluation report is submitted to FDA as part of the 510(k) or PMA.

What Goes in the 510(k) HFE Section

FDA's guidance describes the HFE documentation expected in a 510(k) submission as a Human Factors Engineering Report (or HFE Summary). Key elements:

Description of intended users, use environments, and intended use
Description of the user interface (including instructions for use, labeling, and packaging)
Summary of known use problems and how they were addressed
Summary of formative evaluations and design changes they produced
Summative evaluation study description, methods, participants, results, and conclusions
Residual risks: use errors that remain after mitigation and why they are acceptable

For simple, low-complexity devices with minimal user interaction risk, FDA may accept a justification that summative evaluation data is not necessary. This justification must be supported by analysis. FDA's guidance is clear that the decision not to conduct a summative evaluation requires documented rationale, not a simple assertion.

Common HFE Mistakes That Delay 510(k) Reviews

Testing with unrepresentative users. Using engineers or regulatory staff as test participants when the intended user is a home caregiver or a minimally trained technician produces invalid results. FDA will ask whether the study participants represented the actual intended user population.

Insufficient sample size. FDA's guidance does not specify a minimum sample size. The figure of 15 participants per distinct user group is a widely used industry convention (originating in FDA's earlier human factors draft materials and adopted broadly in practice), not a binding requirement in the 2016 guidance. Studies with very small samples for high-risk devices attract scrutiny.

Missing critical tasks. The tasks tested in the summative evaluation must cover all tasks where a use error could cause serious harm. Omitting a critical task is a straightforward FDA Additional Information request.

Formative evaluation without documentation. FDA does not require formative evaluation reports to be submitted, but it does expect evidence that formative evaluation occurred. If the summative evaluation is the first time users were ever observed, that is a process gap.

Treating HFE as a standalone activity. HFE results must connect to risk management (ISO 14971). Use errors with potential for harm must appear in the risk management file with mitigations documented. An HFE program that never feeds the risk management file is a documentation gap.

IEC 62366-1: The Key Deliverables

For programs following IEC 62366-1, the primary deliverables are:

Usability Engineering File: The complete collection of HFE documentation (analogous to the design and development file)
Intended Use and User Profile
List of Use Scenarios and Use Errors
Usability Evaluation Plan
Summative Usability Evaluation Report

IEC 62366-2:2016 provides supplementary (informative) guidance on applying IEC 62366-1 in practice, including guidance on methods for specific device types.

From Usability Data to Marketing Claims

The evidence your HFE program generates is commercially valuable beyond the 510(k). Summative evaluation data showing that trained nurses completed a critical task successfully and accurately is the foundation for honest, specific marketing claims about ease of use and clinical workflow integration. The data you generate to satisfy FDA is the same data that gives your sales team something credible to say to hospital procurement.

Buzzbox Media works with device companies to build marketing programs around what the device actually demonstrated in clinical and usability testing. When your human factors data shows that your device reduced setup errors in simulation, that finding belongs in your product story, framed accurately and in line with your cleared indication.

If you are building your HFE program now and want to think through how the data will connect to your launch marketing, a 30-minute conversation is a practical place to start. Book at https://www.buzzboxmedia.com/book.