MedDeviceGuideMedDeviceGuide
Back

FDA Human Factors Final Guidance 2026: Three Submission Categories and What Changed

Guide to FDA's final Human Factors guidance (effective August 1, 2026), covering Categories 1-3, Decision Point D flexibilities, and eSTAR submission rules.

Ran Chen
Ran Chen
Global MedTech Expert | 10× MedTech Global Access
Published 2026-08-03Last reviewed 2026-08-0320 min read

The U.S. Food and Drug Administration (FDA) Center for Devices and Radiological Health (CDRH) has issued its long-awaited final guidance, "Content of Human Factors Information in Medical Device Marketing Submissions" (Federal Register Doc. 2026-10734, published May 29, 2026). FDA expects submissions received on or after August 1, 2026 to follow this guidance, which formally replaces the December 2022 draft guidance and establishes a standardized, risk-based framework for including Human Factors Engineering (HFE) and Usability Engineering (UE) data in 510(k), De Novo, PMA, and Humanitarian Device Exemption (HDE) submissions.

For regulatory affairs managers, human factors engineers, and medical device executives, the key message of the final guidance is not that "more testing is required across the board." Rather, FDA has formalized a clear risk-based triage mechanism that categorizes submissions into three distinct HF Submission Categories. Most importantly, the final guidance introduces Decision Point D—a critical addition since the 2022 draft—which gives manufacturers a structured pathway to file a rationale instead of conducting costly human factors validation testing, even when critical tasks are present or impacted.

This guide provides an authoritative breakdown of the final guidance, detailing the three submission categories, the mechanics of Decision Point D, the eSTAR template integration, grandfathering rules for pending submissions, and practical steps to ensure compliance without over-testing.


Scenario Brief: Immediate Impact on In-Flight Submissions

Scenario Question: Our 510(k) submission is nearly complete, and FDA's Human Factors final guidance became effective on August 1, 2026. Which of the three HF Submission Categories applies to our device, can we leverage Decision Point D to avoid new validation testing, and does the guidance apply to an already-pending submission?

Direct Answer: If your 510(k), De Novo, PMA, or HDE is received by FDA on or after August 1, 2026, you must explicitly select an HF Submission Category (1, 2, or 3) in your eSTAR or marketing application package:

  1. Category 1 (Modified Device with No UI/Use Changes): Requires only a high-level summary and conclusion confirming that the modification does not impact the user interface, intended users, intended use environments, training, or labeling.
  2. Category 2 (No Critical Tasks, No Impacted Critical Tasks, or Validated Justification): Requires a contextual HFE summary, use-related risk analysis (URRA), and an evidence-based rationale demonstrating why new human factors validation testing is unnecessary.
  3. Category 3 (New or Impacted Critical Tasks Requiring Validation): Requires a full Human Factors Engineering / Usability Engineering report, including summative human factors validation test results for all critical tasks.

Under the new Decision Point D, even if your device has new or impacted critical tasks, you are not automatically forced into Category 3. You can file under Category 2 if you provide a robust, documented justification based on user-interface use history, UI simplicity, and existing risk controls. Furthermore, for submissions received by FDA before August 1, 2026 or already under active review, FDA reviewers do not expect manufacturers to retrospectively re-format or add newly recommended guidance sections, although submitted HF data will be evaluated under standard review principles.


Evolution of FDA's Human Factors Policy: Draft vs. Final

To understand the 2026 final guidance, it is helpful to look at how CDRH's human factors oversight has evolved over the past decade.

Historically, FDA relied on its 2016 draft guidance List of Highest Priority Devices for Human Factors Review, which named specific product types (such as infusion pumps, hemodialysis systems, and automatic external defibrillators) that automatically required HF data. Industry feedback criticized that approach for being both rigid and reactive: unlisted devices with high use-related risk escaped structured submission requirements, while low-risk modifications to listed devices were subjected to unnecessary regulatory friction.

In December 2022, FDA released the draft guidance Content of Human Factors Information in Medical Device Marketing Submissions, shifting to a universal, risk-based framework applicable to all device types. After reviewing extensive public comments—including requests from AdvaMed and industry groups for a 12-month implementation window—FDA issued the final guidance on May 29, 2026, setting an effective compliance date of August 1, 2026.

Parameter / Feature 2016 Draft (Priority List) December 2022 Draft May 2026 Final Guidance (Effective Aug 1, 2026)
Scope Named list of high-priority device types All 510(k), De Novo, PMA, HDE submissions All 510(k), De Novo, PMA, HDE submissions
Categorization Structure Binary (Priority List vs. Non-Priority) 3 HF Submission Categories 3 HF Submission Categories (Refined)
Critical Task Logic Product-code dependent If Critical Tasks present $\rightarrow$ Mandatory Validation (Category 3) Decision Point D Added: Justification allowed even if Critical Tasks are present
Report Organization General HFE report recommendations Section 5 (Testing) & Section 6 (URRA) layout Swapped & Reorganized: URRA precedes testing; 3x expanded appendix examples
Submission Gate Narrative PDF attachment Voluntary electronic filing Mandatory structured selection field in CDRH eSTAR
QMSR Linkage Design Controls (21 CFR 820.30) Implicit reference Explicit footnote (p. 9 n. 28) linking Category 1/2 rationales to QMSR inspection

What Are the Three HF Submission Categories and Which Applies to Your Device?

FDA's decision logic for determining your device's HF Submission Category is governed by a four-step decision tree (Figure 1 in the final guidance). The decision hinges on whether the device is new or modified, whether use-related hazards or critical tasks exist, and whether existing evidence mitigates the risk without requiring new validation trials.

              [ Marketing Submission: 510(k), De Novo, PMA, HDE ]
                              |
                              v
         Decision Point A: Is it a MODIFICATION of an existing device?
       NO (new device)                           YES (modified device)
            |                                            |
            |                                            v
            |               Decision Point B: Does the change affect the UI,
            |               intended users, uses, use environment, training,
            |               or labeling?
            |                       |                  |
            |                    NO |              YES |
            |                       v                  |
            |                 CATEGORY 1              |
            |                                            |
            +------------------------+-------------------+
                                     |
                                     v
            Decision Point C: Based on the URRA, are there critical tasks
            (new device), or new or impacted critical tasks (modified device)?
                  |                                 |
               NO |                              YES |
                  v                                 |
            CATEGORY 2                             |
                                                   v
                Decision Point D: Given (1) UI history of use,
                (2) UI complexity, and (3) adequacy of existing risk
                controls — should HF validation test data be submitted?
                      |                              |
                NO (justified)                    YES |
                      v                                |
                CATEGORY 2                           v
                                          CATEGORY 3

Category 1: Modified Devices with No User-Interface Changes

Category 1 is the most streamlined pathway. It applies exclusively to modified devices where the modification does not change:

  • The device-user interface (physical, visual, auditory, or software UI)
  • Intended user groups or user characteristics
  • Intended uses or clinical indications
  • Operational or storage environments
  • User training or instructions for use (IFU) / labeling

Required Documentation:

  • A statement confirming the device is a modification of a previously cleared or approved device.
  • A high-level summary of the modification.
  • A brief conclusion and rationale explaining why the change does not affect human factors aspects of the device.

Example: Replacing an internal micro-controller chip with an equivalent component that requires no software or enclosure changes, or updating a backend database architecture that operates invisibly to the clinician.

Category 2: Low Use-Risk, No Impacted Critical Tasks, or Validated Justification

Category 2 applies in three distinct scenarios:

  1. New Devices: A complete Use-Related Risk Analysis (URRA) demonstrates that the device has no critical tasks (tasks where improper execution could lead to serious harm).
  2. Modified Devices: Modifications affect the user interface or labeling, but the URRA confirms that no new critical tasks were created and no existing critical tasks were impacted.
  3. Devices with Critical Tasks (Decision Point D): Critical tasks exist or are impacted, but the manufacturer provides an evidence-based justification demonstrating that new human factors validation testing is not required.

Required Documentation:

  • High-level summary and statement of HF submission category.
  • Description of intended device users, uses, use environments, and user training.
  • Detailed description of the device-user interface.
  • Summary of known use problems (from historical complaint databases, FDA MAUDE, or clinical literature).
  • Complete Use-Related Risk Analysis (URRA) and critical task identification methodology.
  • Evidence-Based Rationale (for Decision Point D cases) explaining why validation testing is unnecessary.

Category 3: Full HFE/Usability Engineering Report Required

Category 3 represents the full regulatory submission standard for human factors. It applies to:

  • New devices with one or more critical tasks.
  • Modified devices where changes introduce new critical tasks or impact existing critical tasks, and where Decision Point D criteria for a justification cannot be met.

Required Documentation:

  • All elements required under Category 2.
  • Summary of preliminary HFE analyses and formative evaluations.
  • Detailed design and methodology for the human factors validation test.
  • Full summative human factors validation test results, including objective pass/fail task performance data, subjective user feedback, protocol deviations, and analysis of all use errors, close calls, and operational difficulties.
  • Conclusion establishing that the device-user interface is safe and effective for the intended users, uses, and use environments.

For detailed guidelines on conducting summative testing, refer to our comprehensive guide on human factors validation testing.


Recommended Reading
How to Get FDA to Tell You Which Center Will Regulate Your Product: The Pre-RFD Playbook
Regulatory PMA2026-07-16 · 24 min read

What Is Decision Point D? (The Key Flexibility Mechanism)

The single most consequential structural change in the 2026 final guidance is the addition of Decision Point D.

In the 2022 draft guidance, Decision Point C served as a rigid gatekeeper: if a manufacturer answered "Yes" to whether critical tasks were present or impacted, the decision tree forced the submission straight into Category 3, requiring a full human factors validation study. Industry stakeholders noted that this forced redundant testing for well-understood, low-complexity interfaces or minor changes to established devices.

In response, FDA introduced Decision Point D in the final guidance. Decision Point D asks:

"Can the manufacturer provide a robust, evidence-based rationale demonstrating that human factors validation testing is not necessary to assure safe and effective use, despite the presence of new or impacted critical tasks?"

Evaluating Decision Point D: What FDA Actually Asks You to Weigh

FDA builds Decision Point D on three core considerations, stated directly in the guidance:

  1. User interface history of use for the intended use, intended users, and use environment(s).
  2. Device user interface complexity.
  3. Adequacy of existing risk control measures.

FDA then opens the analysis up, directing submitters to "examine multiple considerations, including but not limited to" the intended user and uses, technological characteristics, user familiarity and experience with the device interface, user characteristics, the clinical impact of use errors, and the use environment. In practice, these collapse into a working checklist a regulatory team can step through before deciding whether validation testing must be submitted:

  • User interface complexity — Is the interface simple, standardized, and familiar to the user population, or complex with multiple screens, menus, and physical controls?
  • Operational workflow complexity — Does operation involve multi-step sequences, rapid decision-making, or complex programming, monitoring, or maintenance?
  • History of safe use — Does the same or a substantially similar interface carry an established postmarket safety record? FDA explicitly encourages comparative analyses against legally marketed devices (labeling comparison, comparative task analysis, physical comparison) to identify where the same or similar risks apply.
  • New critical tasks introduced — Does the change create entirely new user interactions where error could cause serious harm?
  • Impact on existing critical tasks — Does the change alter the force, display, menu structure, or cognitive load of an existing critical task? FDA's own worked example adds a pediatric user group to an automated insulin delivery system precisely because it raises complexity and severity questions even when the device interface itself is unchanged.
  • Novel technology or interaction paradigms — Does the interface introduce unfamiliar mechanisms (e.g., augmented-reality displays, touchless gesture control)?
  • Changes in users or use environment — Is the device moving from an ICU operated by trained clinicians to home use operated by lay users?
  • Known use-error and postmarket signals — FDA historically cites device types such as infusion pumps and hemodialysis systems as associated with use-error concerns that warrant heightened scrutiny; review your complaint, MDR/MAUDE, and recall data.
  • Severity of potential harm — If a use error occurs on a critical task, could it cause death or irreversible harm, or is residual risk limited to minor discomfort?

If that evaluation points to low residual risk and an established history of safe use, a Category 2 rationale under Decision Point D is defensible. If any factor flags heightened risk — new users, higher severity, novel interaction, or a known-use-error device type — plan for Category 3 validation testing.

Crafting a Winning Category 2 Rationale Under Decision Point D

If your evaluation indicates low residual risk, your Category 2 rationale must be supported by empirical evidence rather than subjective assertions. Acceptable evidence streams include:

  • Substantial UI Similarity: Demonstrating that the user interface, layout, and operational sequence are identical to a cleared predicate device with a proven postmarket safety record.
  • Formative Test Data: Submitting data from rigorous formative evaluations showing that users successfully navigated the critical task without errors.
  • Leveraging Prior Submissions: Referencing previously reviewed HF validation data from your own prior cleared 510(k) or PMA for the same platform, accompanied by a side-by-side comparative analysis showing the changes do not degrade usability.
  • Standardized Usability Compliance: Demonstrating adherence to recognized consensus standards, such as the IEC 62366-1 usability engineering process.

Grandfathering & Effective Date Nuances (August 1, 2026)

Regulatory teams must pay close attention to the compliance dates and transition rules established by CDRH.

The 60-Day Operational Window and the August 1, 2026 Cutoff

FDA guidances take effect when issued, and this one was issued on May 29, 2026. But FDA paired issuance with a transition window: the guidance itself states that FDA "recognizes and anticipates that the Agency and industry may need a minimum of 60 days to perform activities to operationalize the policies within this guidance." Sixty days from the May 29, 2026 publication lands on roughly July 28, 2026, and FDA rounded its practical cutoff to the start of the following month — August 1, 2026.

Rather than tying the transition to the literal 60th day, FDA anchors it to a single clean date: submissions received on or after August 1, 2026 are expected to follow the final guidance, while submissions already pending or received before that date are not. For filing-decision purposes, use August 1, 2026, not July 28.

Grandfathering Rules for In-Flight Submissions

FDA has provided clear transition instructions for pending applications:

  • Submissions Received BEFORE August 1, 2026: Submissions currently under review, or submitted prior to August 1, 2026, are not expected to retrospectively adopt the newly recommended submission category structure or append new guidance checklists. FDA lead reviewers will complete their evaluations using the standards in place at receipt.
  • Voluntary Early Adherence: FDA reviewers will accept and review HF information formatted under the 2026 final guidance if submitted prior to August 1, 2026.
  • Submissions Received ON OR AFTER August 1, 2026: Must include the structured HF Submission Category selection and associated documentation. Because the category is now a mandatory eSTAR field (see below), an incomplete HF selection can hold up acceptance screening or draw an early deficiency.

Operationalizing Compliance: eSTAR and QMSR Integration

1. Mandatory eSTAR Selection Fields

To operationalize the final guidance, FDA updated the official CDRH eSTAR (Electronic Submission Template and Resource) templates for 510(k) and De Novo submissions.

Within the Human Factors / Usability section of eSTAR, submitters are now presented with mandatory radio buttons corresponding to Category 1, Category 2, or Category 3. Selecting a category dynamically unlocks the required attachment fields:

  • Selecting Category 1 un-hides fields for the modification rationale and high-level summary.
  • Selecting Category 2 requires uploading the URRA, UI description, known use problems summary, and (if applicable under Decision Point D) the evidence-based testing waiver rationale.
  • Selecting Category 3 opens attachment nodes for the complete HFE/UE report, validation test protocol, raw data tables, and root cause analysis of use errors.

2. The QMSR Footnote: Inspections vs. Submissions (p. 9 n. 28)

A critical nuance often overlooked by regulatory teams is contained in Footnote 28 on Page 9 of the final guidance. FDA explicitly notes:

"While certain human factors information may not be required for submission to FDA under Category 1 or Category 2, manufacturers are reminded that Design Controls requirements under 21 CFR Part 820 / ISO 13485 (QMSR) require maintaining complete use-related risk analysis, user interface evaluation, and design verification/validation records within the Design History File (DHF)."

The Inspection Risk: Successfully filing a Category 1 or Category 2 submission does not exempt your organization from human factors scrutiny during an FDA Quality Management System Regulation (QMSR) inspection. Investigators conducting an inspection under Compliance Program CP 7382.850 can request your URRA, formative testing notes, and Decision Point D rationale. If your internal DHF lacks thorough documentation supporting your Category 2 classification, FDA can issue a Form FDA 483 observation for inadequate design validation under 21 CFR 820.30(g).


Recommended Reading
FDA TAP Pilot Program Guide: Total Product Life Cycle Advisory Strategy
Regulatory Clinical Evidence2026-07-31 · 21 min read

Alignment with Existing Guidance and Standards

The 2026 final guidance does not exist in a vacuum; it functions as part of an integrated regulatory framework alongside existing standards and companion guidance documents.

+-----------------------------------------------------------------------------------+
|                            FDA HF REGULATORY FRAMEWORK                            |
+-----------------------------------------------------------------------------------+
|  2016 Final Guidance: "Applying Human Factors and Usability Engineering..."       |
|  --> Defines HOW to perform HFE (URRA, formative testing, summative protocols)    |
+-----------------------------------------------------------------------------------+
                                         |
                                         v
+-----------------------------------------------------------------------------------+
|  2026 Final Guidance: "Content of HF Information in Marketing Submissions"        |
|  --> Defines WHAT to submit to FDA (Category 1, Category 2, or Category 3)        |
+-----------------------------------------------------------------------------------+
                                         |
                                         v
+-----------------------------------------------------------------------------------+
|  International Standard: ANSI/AAMI/IEC 62366-1:2015+AMD1:2020                     |
|  --> Global Usability Engineering Process (maps directly to FDA Category 2/3)     |
+-----------------------------------------------------------------------------------+
  1. Relation to the 2016 HF Guidance: The 2016 final guidance, Applying Human Factors and Usability Engineering to Medical Devices, remains fully active. It dictates how to perform usability engineering (task analysis, hazard identification, validation study design). The 2026 guidance specifies what portion of that work must be packaged and submitted to CDRH.
  2. Relation to IEC 62366-1: The documentation required for Category 2 and Category 3 directly parallels the outputs of an IEC 62366-1 Usability Engineering File (UEF). A company maintaining compliance with IEC 62366-1 already generates the URRA, UI specification, and summative report needed for FDA submission.
  3. Application to Combination Products & IVDs: While this guidance is issued by CDRH, medical devices regulated as combination products (e.g., drug-delivery auto-injectors) or home-use IVDs must account for additional center-specific requirements. For drug-delivery systems, review our auto-injector critical-task matrix guide and our analysis of home-use IVD HF and labeling requirements.

To prepare applications for filing on or after August 1, 2026, regulatory and quality teams should implement the following four-step action plan:

[ STEP 1: Audit In-Flight Submissions ]
  --> Check target filing date. If >= Aug 1, 2026, assign HF Submission Category (1, 2, or 3).

[ STEP 2: Perform URRA & Evaluate Decision Point D ]
  --> Map critical tasks. If critical tasks exist, weigh UI use history, complexity,
      severity, and existing risk controls against FDA's Decision Point D factors.
  --> Determine if an evidence-based Category 2 rationale is defensible.

[ STEP 3: Update eSTAR Assembly Workflow ]
  --> Ensure HFE documentation matches eSTAR attachment nodes for the chosen Category.

[ STEP 4: Verify DHF Completeness for QMSR ]
  --> Confirm that complete URRA and UI evaluation records exist in DHF per Footnote 28.
  1. Audit Pending Submissions: Identify all 510(k), De Novo, PMA, and HDE applications scheduled for submission on or after August 1, 2026. Assign a tentative HF Submission Category to each project.
  2. Conduct Use-Related Risk Analysis Early: Ensure your URRA clearly defines critical tasks using clear risk thresholds (tasks where execution errors could cause serious harm). If critical tasks exist, perform a formal Decision Point D assessment against the nine FDA risk factors to determine whether validation testing can be justified as unnecessary.
  3. Draft Robust Rationales for Category 2: If invoking Decision Point D, build a data-backed justification using predicate use history, formative evaluation data, or prior submission clearances. Avoid vague assertions such as "the device is intuitive."
  4. Utilize the Pre-Submission (Q-Sub) Program: If you are uncertain whether FDA will accept your Decision Point D rationale for Category 2, file a Q-Submission before initiating expensive summative validation testing. Obtaining CDRH concurrence during a Pre-Submission eliminates the risk of an unexpected Refuse-to-Accept or additional information request during marketing review.

Frequently Asked Questions (FAQ)

Can I reference human factors data from a prior FDA submission instead of resubmitting it?

Yes. If your company previously submitted comprehensive human factors validation data for a cleared predicate or parent platform in a prior 510(k) or PMA, you can reference that data to support a Category 2 rationale under Decision Point D. You must provide the prior submission number (e.g., Kxxxxxx or Pxxxxxx), demonstrate that the user interface and critical tasks remain substantially equivalent, and include a comparative analysis showing that any minor changes do not introduce new use-related hazards.

Will FDA ask about human factors during a QMSR inspection even if I submitted under Category 1 or 2?

Yes. As explicitly stated in Footnote 28 of the final guidance, classification into Category 1 or Category 2 affects only what is submitted in your premarket marketing application. It does not relieve your firm of Design Controls obligations under 21 CFR 820.30 / ISO 13485 (QMSR). FDA field investigators can inspect your Design History File (DHF) to verify that you conducted a use-related risk analysis and maintained appropriate user interface evaluation records.

Has FDA updated the eSTAR templates for the HF Submission Categories?

Yes. CDRH has updated the official 510(k) and De Novo eSTAR templates to incorporate structured selection fields for HF Submission Categories 1, 2, and 3. Submitters must select the applicable category via radio buttons, which automatically adjusts the required document attachment nodes within the eSTAR file.

What is the most common deficiency that gets a human factors section flagged during review?

The most frequent deficiency cited by CDRH reviewers is an incomplete or improperly formatted Use-Related Risk Analysis (URRA). Common mistakes include failing to explicitly identify which tasks are "critical tasks," omitting clear severity definitions for use-error outcomes, or submitting a Category 2 rationale based on subjective opinion rather than objective, documented evidence.

Should I file a Pre-Submission if I am unsure whether validation testing is needed?

Yes. FDA explicitly encourages manufacturers to utilize the Q-Submission (Pre-Submission) program when there is ambiguity regarding category selection, the adequacy of a Decision Point D rationale, or the design of a summative validation protocol. Securing FDA feedback during a Q-Sub prevents costly delays and avoids the risk of receiving a major deficiency letter during 510(k) or PMA review.


Recommended Reading
Human Factors Content for FDA Medical Device Marketing Submissions
Design Controls Regulatory2026-05-12 · 13 min read