Human Factors Evidence Now Needs a Submission Category

The transition period is over

FDA issued its final guidance on the content of human factors information in medical device marketing submissions on May 29, 2026. The agency acknowledged that manufacturers and FDA would need time to operationalize the new approach and said it generally did not expect submissions received before August 1, 2026 to include the newly recommended information. That transition point has now passed.

The final FDA guidance does not create a new binding regulation. It presents FDA’s current recommendations for using a risk-based framework to decide what human factors engineering and usability engineering information should be included in a marketing submission. For manufacturers, the practical change is still meaningful: every submission team now needs a defensible category decision, not simply a folder of usability records.

This is an operating problem as much as a writing problem. The category depends on what changed, how the user interface is affected, whether critical tasks exist or are affected, whether existing controls remain effective, and whether validation evidence is needed. Those facts live across design, risk management, complaints, labeling, training, and regulatory strategy.

What the three categories actually decide

FDA’s framework leads to three Human Factors Submission Categories. The categories determine the recommended depth of information in the submission. They do not rank devices from good to bad, and they do not replace the underlying human factors work required to support a safe and effective design.

Category 1: justify why the modification does not affect human factors

Category 1 is intended for a modified device when the change does not affect human factors considerations. The submission should include a conclusion and high-level summary that explains the category decision. When prior HFE or UE evaluations are leveraged, the manufacturer should identify them and explain why the modification does not affect the user interface, users, uses, use environments, training, or labeling.

The risk is treating Category 1 as a shortcut. A short report is credible only when the underlying change assessment is complete. A software algorithm change, for example, may leave the visible interface unchanged but still alter alarms, prioritization, timing, or user response. The team must evaluate the whole interaction, not just the screen layout.

Category 2: document the rationale for not submitting validation data

Category 2 calls for more context about the device and its known use problems, plus a clear rationale. The rationale may explain why there are no critical tasks for a new device, why a modified device introduces no new or affected critical tasks, or why validation data are not needed in the submission.

That rationale should be grounded in the decision path, not written after the evidence has been assembled. If a modified task, harm, or risk control does not merit new validation data, the file should show the evidence supporting that conclusion.

Category 3: submit the comprehensive HFE or UE report

Category 3 includes a comprehensive report with human factors validation testing. FDA recommends content covering intended users and environments, the user interface, known use problems, preliminary analyses and evaluations, the use-related risk analysis, critical tasks, and validation testing of the final design.

Category 3 should not begin at report writing. It begins when formative work, risk analysis, protocol decisions, design changes, and validation evidence are controlled as one traceable story.

Make the URRA the decision backbone

FDA recommends that the use-related risk analysis, or URRA, include all user tasks and identify the critical tasks. For modified devices, the guidance says the assessment should consider the final finished device, not only the feature that changed. This is an important discipline because upstream and downstream tasks can be affected even when the change request appears narrow.

Treat the URRA as a living design record. Link each task to foreseeable use errors, hazardous situations, harms, risk controls, and the evidence showing whether those controls work. When complaints, adverse events, recalls, or problem reports identify a use-related signal, the URRA and category decision should be revisited.

This connection is especially valuable for products with complex interfaces, multiple user groups, home use, training dependencies, or maintenance steps. It turns human factors from a final submission section into an active design-control input.

Build a category decision record

Create one controlled record early in the submission plan. Identify whether the device is new or modified, summarize the proposed user-interface and labeling changes, list affected users and environments, cite the current URRA, identify new or affected critical tasks, and document known use problems.

Then record the category and rationale. Name the evidence owner for every factual statement. If the team plans to leverage a prior study, capture the prior submission reference and explain why the earlier evidence remains applicable. If uncertainty remains, decide whether a Pre-Submission question is appropriate while there is still time to act on FDA feedback.

The category decision should have cross-functional approval from regulatory affairs, design quality, risk management, and the human factors lead. Clinical, safety, software, labeling, and post-market owners should participate when their evidence affects the decision.

Five actions before the next submission

1. Add the three-category decision to the submission planning procedure and design change workflow.
2. Review URRA templates so they capture all user tasks, critical tasks, risk controls, and change comparisons.
3. Map known use problems from complaints, recalls, adverse events, service, and comparable devices into the human factors file.
4. Create report shells for Categories 1, 2, and 3 using FDA’s recommended content, while allowing device-specific judgment.
5. Run a readiness review before validation or submission lock to confirm that evidence, references, and rationales agree.

Teams preparing structured FDA submissions can connect this work with eSTAR submission readiness. A medical-device eQMS workflow can also connect design changes, the URRA, complaints, labeling, and approvals without replacing qualified human factors or regulatory judgment.

Better classification creates a cleaner review story

The value of the new framework is not a category label. It is a repeatable way to explain why the submitted evidence matches the use-related risk. When the decision is made early, teams can avoid both under-documenting a material interaction risk and overloading a submission with records that do not help the reviewer.

The strongest file shows a straight line from the final device and its users to the URRA, critical-task decision, evidence strategy, and report content. That line is what makes the category defensible.

Preparing a new or modified device submission? Use IntelaSolve’s compliance readiness analysis to identify where human factors evidence, ownership, or traceability needs attention before submission lock.