MFLRC - MF License & Regulatory Consultants

July 26, 2026 · Medical Device

FDA Human Factors Submission Categories: A 2026 Guide

By Mussarat Fatima

Medical DeviceRegulatory Affairs
FDA Human Factors Submission Categories: A 2026 Guide

If you file medical device submissions with the United States Food and Drug Administration, a change lands on August 1, 2026 that touches nearly every application. On that date, FDA's final guidance on the content of human factors information takes effect, and the updated electronic submission templates now ask you to declare a human factors submission category and back it up. This is no longer a topic only for infusion pumps and complex devices. It is a field in the form for every device that goes through the template.

FDA published the final guidance, Content of Human Factors Information in Medical Device Marketing Submissions, on May 29, 2026, replacing a draft that had unsettled the device industry since December 2022. This guide explains the three human factors submission categories, the flowchart that assigns them, the new Decision Point D that can reduce your testing burden, and what the August 1 transition means in practice, including for Canadian manufacturers exporting to the United States.

What are the FDA human factors submission categories?

Direct answer: the human factors submission categories are three tiers of documentation FDA expects in a device marketing submission, scaled to use-related risk. Category 1 is a short summary for certain modified devices, Category 2 is a rationale that no critical tasks are involved, and Category 3 is a full human factors engineering report with validation testing. You select one category per submission and provide the matching evidence.

The categories are risk-based, so the more a device's use could lead to harm, the more evidence FDA wants to see. The core concept is the critical task, which is a user task that, if performed incorrectly or not performed, would or could cause serious harm. The categories did not change from the 2022 draft, and they sit alongside FDA's foundational guidance, Applying Human Factors and Usability Engineering to Medical Devices, which the content guidance is designed to complement rather than replace.

HF submission categoryWhen it appliesWhat to submit
Category 1Modified devices onlyA conclusion and a high-level summary of the human factors evaluation
Category 2No critical tasks for a new device, or no new or impacted critical tasks for a modified deviceA rationale explaining why there are no critical tasks or no new or impacted critical tasks
Category 3Critical tasks are present and validation data is warrantedA human factors or usability engineering report that includes human factors validation testing

Why this matters now: the August 1, 2026 transition and eSTAR

Direct answer: the guidance is effective August 1, 2026, and FDA has rebuilt the eSTAR templates around it. Beginning on that date, the non-IVD and IVD eSTARs prompt you to identify your human factors submission category and provide supporting information, so human factors is now a checkpoint in every template-based submission rather than an occasional add-on.

The practical mechanics matter. FDA released eSTAR version 7.0 for both non-IVD and IVD devices, and the previous version 6.2 retires on August 3, 2026. FDA has said it does not expect manufacturers to have the newly recommended human factors information ready for submissions received before August 1, and it will review such information if provided, but the direction of travel is clear. Because eSTAR is an interactive form that opens and closes sections based on your answers, an inaccurate response to the human factors questions can omit downstream questions and put your submission on a technical screening hold for up to 180 days.

How to determine your category: the flowchart and its decision points

Direct answer: FDA provides a flowchart that walks you through four decision points, A through D, to land on the right category. It asks whether the device is modified, whether the change affects the user interface or related factors, whether a use-related risk analysis identifies critical tasks, and finally whether validation testing should be submitted. Your answers, not your device's name, decide the category.

Decision pointQuestionWhat it determines
AIs the submission for a modification to an existing device?Routes modified devices and new devices down different paths
B (modifications)Is the change to the user interface, intended users, intended uses, use environment, training or labelling?Whether the change could affect safe use
CBased on a use-related risk analysis, are there critical tasks (new devices) or new or impacted critical tasks (modified devices)?Whether critical tasks are in play
D (new in the final guidance)Should validation test data be submitted, considering user interface history of use, user interface complexity and adequacy of existing risk controls?Whether a validation study belongs in the submission

The use-related risk analysis, or URRA, is the engine of the whole process. It is where you identify the tasks a user performs, the errors they could make, and the potential harm. If that analysis shows no critical tasks, you are heading toward a Category 2 rationale. If it shows critical tasks, Decision Point D then decides whether you must include validation testing or can justify leaving it out.

Decision Point D and the quiet link to QMSR inspections

Direct answer: Decision Point D is the one genuinely new element in the final guidance. It lets a submitter with critical tasks argue that human factors validation data does not need to be in the marketing submission, based on the user interface history of use, the complexity of the interface, and the adequacy of existing risk controls. It can lighten your submission, but it does not remove the underlying obligation to do the work.

This is where experienced device teams read carefully. FDA ties Decision Point D to the Quality Management System Regulation and its design verification and validation requirements, and states that human factors information should be maintained by the manufacturer whether or not it is submitted to FDA. In plain terms, choosing not to submit validation data does not make it optional. It moves the evidence from the submission file into your design history, where an investigator can ask for it during a QMSR inspection. FDA also notes that its review teams often expect to see human factors study results, and may request them during review even when the guidance suggests they are not required.

The guidance also describes what makes a user interface complex, including devices that involve programming, monitoring or maintenance, and systems with many steps such as connections, disconnections and selections that influence how the device operates. If that sounds like your device, expect FDA to lean toward wanting validation data, and prepare your justification accordingly. When the category or the need for validation testing is unclear, FDA points sponsors to the pre-submission program, which is the right place to align before you file.

What this means for Canadian device makers exporting to the United States

Direct answer: Canadian manufacturers who sell into the United States must meet the new expectations in their FDA submissions, and the good news is that a sound usability programme built for Health Canada carries most of the way. Health Canada expects usability and human factors information for medical device licence applications and recognizes the international usability engineering standard IEC 62366-1, so the analysis is largely shared.

The catch is packaging. FDA now wants the human factors story told in a specific structure, mapped to a submission category and entered into eSTAR, with the design history behind it available for a QMSR inspection. A file that satisfies IEC 62366-1 for a Canadian Medical Device Licence still needs to be reframed into FDA's category language and decision-point logic. Teams that treat the two systems as one connected quality effort, rather than two separate paperwork exercises, save the most time and avoid contradictory records.

A worked example: how a category is chosen

Direct answer: the category comes from working the flowchart honestly against your use-related risk analysis. Two devices with similar technology can land in different categories depending on whether their use involves critical tasks and how strong the existing evidence is. Two short examples make the logic concrete.

First, imagine a new, simple, single-use device with a straightforward interface. At Decision Point A it is new, so you skip the modification question. At Decision Point C, your use-related risk analysis finds no critical tasks, because no user error in the analysis could lead to serious harm. That routes the device to Category 2, and your submission provides a clear, evidence-based rationale explaining why there are no critical tasks. No validation study is expected, but the rationale must be solid, because an unconvincing no critical tasks claim is a common source of deficiencies.

Now imagine a modified infusion device where the change alters the programming screen. At Decision Point A it is a modification, at Decision Point B the change is to the user interface, and at Decision Point C the risk analysis identifies a new critical task, because a programming error could cause an overdose. You then reach the new Decision Point D. If the interface is complex and the risk controls are not clearly adequate, you should include human factors validation testing and file as Category 3. If a strong history of safe use and robust risk controls exist, you may justify not submitting the validation data, but you keep that evidence in your design history file for a possible request. The device did not choose the category. Your analysis did.

What to prepare before you file

Direct answer: before you open eSTAR, assemble the evidence that supports your category so the form becomes a summary of decisions already made, not a place where you improvise. The core package is your use-related risk analysis, your critical-task determination, your category rationale, and any validation results or the justification for omitting them.

In practice that means a current use-related risk analysis tied to your risk management file, a documented list of tasks and which are critical, and a short written rationale that maps each flowchart decision point to a conclusion. If you are using Decision Point D to omit validation data, write the justification against the three factors FDA lists: user interface history of use, interface complexity, and adequacy of existing risk controls. Keep all of it in the design history file. When the guidance or your category is genuinely unclear, a pre-submission meeting with FDA is the lowest-risk way to confirm your approach before you commit to a filing.

Compliance checklist for the new human factors expectations

  • Download and use eSTAR version 7.0 for non-IVD or IVD submissions, and retire version 6.2 by August 3, 2026.
  • Complete a use-related risk analysis and a documented critical-task determination for the device.
  • Work the flowchart through Decision Points A, B, C and D and record how you reached your category.
  • Write a defensible rationale for any Category 2 selection or Decision Point D justification.
  • Keep all human factors evidence in the design history file, whether or not you submit it.
  • Answer the eSTAR human factors questions accurately to avoid a technical screening hold.
  • Use a pre-submission if your category or the need for validation testing is uncertain.

Common mistakes we see

  • Treating human factors as a formatting task. The category flows from a real use-related risk analysis, not from a template field filled in at the end.
  • Assuming Decision Point D removes the obligation. It moves validation evidence into your design history, where a QMSR investigator can request it.
  • Under-scoping critical tasks. Declaring no critical tasks to reach Category 2 without a rigorous analysis invites a deficiency.
  • Using the retired eSTAR version. Filing on version 6.2 after it retires invites additional information requests about the differences.
  • Answering eSTAR questions carelessly. An inaccurate response can hide required sections and trigger a technical screening hold of up to 180 days.
  • Keeping Canadian and US files separate. One usability programme should feed both IEC 62366-1 for Health Canada and the FDA category structure.

Frequently asked questions

When does the FDA human factors guidance take effect?

The final guidance was published on May 29, 2026 and is effective August 1, 2026. FDA gave at least 60 days to operationalize it and does not expect manufacturers to include the newly recommended information in submissions received before that date, though it will review the information if provided.

How many human factors submission categories are there?

Three. Category 1 is a high-level summary for certain modified devices, Category 2 is a rationale that there are no critical tasks or no new or impacted critical tasks, and Category 3 is a human factors engineering report that includes validation testing. The number of categories did not change from the 2022 draft.

What is new in the final guidance compared with the draft?

The main substantive change is a new Decision Point D in the flowchart. It lets a submitter with critical tasks evaluate whether human factors validation data should be included, based on the user interface history of use, the interface complexity, and the adequacy of existing risk controls. The final guidance also adds appendices with example reports and justifications.

Which submission types does this apply to?

The framework applies to premarket submissions reviewed by CDRH, including 510(k), De Novo and premarket approval applications, and it is built into both the non-IVD and IVD eSTAR templates.

If I use Decision Point D to avoid submitting validation data, am I done?

No. FDA ties Decision Point D to the Quality Management System Regulation and expects human factors information to be maintained by the manufacturer whether or not it is submitted. Review teams may still request the results during review, and an investigator may ask for them during a QMSR inspection.

Does a Canadian usability file meet the FDA expectations?

Largely, because Health Canada recognizes IEC 62366-1 and the underlying analysis is shared. However, the file must be reframed into FDA's submission category and decision-point language and entered into eSTAR, with the supporting design history available for inspection.

How MFLRC can help

MFLRC supports device manufacturers, importers and distributors across Canadian and cross-border submissions. Through our Regulatory Affairs, Licensing and Import and Export practice, we help you determine the right human factors submission category, build the use-related risk analysis and critical-task determination, and prepare a defensible rationale for a Category 2 or Decision Point D position before you file in eSTAR.

We also help you close the gap between the submission and the design history, so that your human factors evidence holds up in a quality system audit. Our support spans ISO 13485 and QMSR readiness, gap assessments, SOP development, mock audits and inspection preparation, so one connected quality effort serves both Health Canada and FDA.

If you have a submission planned in the next few months, now is the time to lock down your human factors position. Talk to us before you file.

Conclusion

The August 1, 2026 change reframes human factors from an occasional testing question into a standing feature of every device submission. The three categories are unchanged, but the new Decision Point D and the eSTAR fields mean you now have to state your position clearly and defend it. The smart move is to decide your category from a real use-related risk analysis, keep the evidence in your design history whether you submit it or not, and treat the submission and the inspection file as one connected record. Do that, and the deadline is a formality rather than a scramble.

Sources and references

Share with others

Tags

Human FactorsMedical DevicesFDAQMSRISO 13485United States
Book a consultation