TLDR

On May 29, 2026, FDA finalized "Content of Human Factors Information in Medical Device Marketing Submissions," replacing the December 2022 draft. The guidance introduces a new Decision Point D in the submission category flowchart, expands flexibility for justifying forgoing HF validation testing, clarifies the use of existing data across submissions, and provides a revised HFE/UE report outline with three times as many practical examples. Medical device companies submitting 510(k)s, De Novo requests, and PMAs must update their human factors planning process immediately. The FDA will hold a Town Hall on July 22, 2026 to discuss the final guidance.

Human factors engineering sits at the intersection of patient safety and regulatory compliance. When a device is difficult to use, confusing to read, or inconsistent with user expectations, the result is use error — and use error is one of the leading causes of adverse events in medical devices.

FDA has known this for decades. The agency's 2016 guidance, "Applying Human Factors and Usability Engineering to Medical Devices," established the foundational framework for how manufacturers integrate usability into the design process. What that guidance did not resolve was a persistent question: exactly what information must appear in a premarket submission, and for which devices?

The May 2026 final guidance answers that question directly.

What the May 2026 Final Guidance Does

FDA published "Content of Human Factors Information in Medical Device Marketing Submissions" on May 29, 2026. This document finalizes the December 2022 draft guidance and works as a companion to — not a replacement of — the 2016 HFE guidance.

Where the 2016 guidance explains how to conduct human factors activities during device development, the 2026 final guidance specifies what to include in the regulatory submission. Both documents remain active and must be read together.

The guidance applies to:

• 510(k) submissions
• De Novo requests
• Premarket Approval (PMA) applications
• Combination products

The scope covers all devices for which FDA may request human factors information, and the new framework makes that determination more systematic than it has ever been.

The Three HF Submission Categories

The guidance organizes submissions into three categories based on the risk profile and complexity of the device and its user interface.

HF Submission Category 1 applies to modifications to existing devices with low use-related risk impact. Manufacturers provide a high-level conclusion and summary of the HF evaluation. This category requires the least documentation burden.

HF Submission Category 2 applies when a manufacturer can demonstrate there are no critical tasks (for new devices) or no new or impacted critical tasks (for modified devices). A clear rationale is required, supported by a Use-Related Risk Analysis (URRA).

HF Submission Category 3 requires a full HFE/Usability Engineering (UE) report, including HF validation testing data. This applies to devices with significant use-related hazards, complex user interfaces, major redesigns, or novel interaction paradigms such as augmented reality or new interoperable system architectures.

Category selection now appears directly in the updated eSTAR templates, which means every submission reviewer will see the category claimed and the supporting justification. Human factors is no longer a background consideration — it is a front-and-center element of every device review.

What Changed: The New Decision Point D

The most consequential structural change in the 2026 final guidance is the addition of Decision Point D to the risk-based flowchart that determines which HF Submission Category applies.

The prior flowchart included three decision points:

• Decision Point A: Is this a modification to an existing device?
• Decision Point B: Does the change affect the user interface, intended users, intended uses, use environments, training, or labeling?
• Decision Point C: Based on a Use-Related Risk Analysis, are there critical tasks or new/impacted critical tasks?

In the December 2022 draft, a "Yes" answer to Decision Point C automatically placed a submission into Category 3, requiring full validation testing. The 2026 final guidance changes this. A fourth decision point now intervenes:

Decision Point D asks manufacturers to evaluate three considerations:

1. The user interface history of use for the intended users and use environments
2. The complexity of the user interface
3. The adequacy of existing risk control measures

A device can answer "Yes" to Decision Point C and still avoid full HF validation testing if Decision Point D analysis supports a robust justification. This flexibility is particularly valuable for modifications to well-established devices with documented safe-use histories and strong existing risk mitigations.

Importantly, FDA's footnote to Decision Point D signals that HF documentation should still be maintained by the manufacturer under the Quality Management System Regulation (QMSR), regardless of what is submitted. This opens the door for FDA investigators to request HF records during inspections — meaning the documentation must exist even when it is not submitted. [Source: FDA, Content of HF Information in Medical Device Marketing Submissions, 2026]

Justifying Forgoing HF Validation Testing

One of the most practically significant changes in the 2026 guidance is the explicit recognition that manufacturers may, under appropriate circumstances, provide a well-reasoned justification in lieu of new HF validation data.

This approach has worked in practice for years, particularly for modified devices or devices with interfaces well understood by their intended user populations. The 2026 guidance formalizes FDA's acceptance of this pathway, so manufacturers no longer rely on informal precedent.

What makes a justification robust? According to FDA:

• A comprehensive, well-documented Use-Related Risk Analysis that maps identified risks to mitigations
• Evidence from prior submissions demonstrating HF performance of the same or substantially similar user interface
• Use-error history data — field complaint records, post-market surveillance data, or published literature — that demonstrates safe performance in real-world use
• Clear traceability between the URRA findings, design decisions, and the final user interface configuration

The guidance explicitly encourages manufacturers to leverage existing HF data from prior submissions. Previously submitted HF content does not need to be resubmitted; cross-references to earlier submissions are acceptable. This rewards manufacturers who maintain organized, traceable HF documentation throughout device development. [Source: Emergo by UL, Key Updates in the Final FDA Guidance, May 2026]

Revised HFE/UE Report Outline

The 2026 final guidance also revises the structure of the HFE/UE report, which is the primary document submitted for Category 3 devices.

The key structural change: Sections 5 and 6 are transposed from the prior outline. The summary of preliminary evaluations now precedes two consecutive sections covering the URRA and critical task identification. This sequence creates a more logical narrative flow — the formative work is presented first, followed immediately by the risk analysis that informed it, and then the critical task determination that flows from that risk analysis.

For quality teams preparing HFE/UE reports, this is an immediately actionable change. Existing report templates should be updated to reflect the new section order before the next submission.

Expanded Examples — Three Times the Page Count

The 2026 final guidance devotes three times as many pages to practical examples as the 2022 draft did. The appendices now include:

• Sample report content and outlines for each of the three HF Submission Categories
• Example scenarios covering special user populations (pediatric users)
• Example scenarios for novel interfaces (augmented reality)
• Example scenarios for devices with documented histories of known use-related problems
• Detailed case examples including a reusable duodenoscope, a stereotaxic navigation system, a continuous glucose monitor, and an interoperable automated glycemic controller

These examples reflect the actual range of devices in development today, not simplified hypothetical cases. Manufacturers preparing submissions for complex or novel devices now have concrete reference material from FDA to guide the level and structure of HF information required.

How HFE Documentation Fits Into the Design and Development File

Under the QMSR, effective February 2, 2026, the legacy Design History File (DHF) is now referred to as the Design and Development File (DDF). This terminology shift reflects FDA's harmonization with ISO 13485:2016 and does not reduce the documentation requirements — it aligns them with the global standard.

HFE documentation is a mandatory component of the DDF. Specifically, the DDF must contain:

• The Use-Related Risk Analysis (URRA) and its revisions across the development lifecycle
• Formative usability study plans and results
• Summative usability study (HF validation testing) plans, protocols, results, and analysis
• Critical task identification methodology and output
• The HFE/UE report in its final form
• Traceability between URRA findings and design decisions

The 2026 guidance explicitly notes that manufacturers should maintain full HF documentation regardless of what they submit to FDA. An investigator reviewing the DDF during a QMSR inspection may request HF records even for devices that fell into Category 1 or Category 2. If that documentation does not exist in organized, retrievable form, it creates inspection risk. [Source: FDA Law Blog, June 2026]

Formative vs. Summative Usability Studies Under the New Framework

The 2026 guidance preserves the distinction between formative and summative usability studies but provides clearer context for how each fits into the submission.

Formative evaluations occur throughout design and development. Their purpose is to identify usability problems early enough to correct them. They inform the iterative design process and feed directly into the URRA. The 2026 guidance recognizes formative evaluations as valuable evidence in justification pathways — strong formative data can support a decision to limit the scope of summative testing.

Summative usability studies (also called HF validation studies) constitute the final, controlled evaluation of the user interface with representative users performing critical tasks under simulated use conditions. These studies are required for Category 3 submissions and must be designed to detect use errors on all identified critical tasks.

FDA's guidance encourages manufacturers to think carefully about the number of participants, the selection of simulated use scenarios, and the definition of acceptable performance thresholds before conducting a summative study. The expanded appendix examples show FDA-acceptable approaches to study design across a range of device types and user populations.

What FDA Expects in a 510(k) or PMA HFE Submission

For manufacturers preparing submissions, the 2026 final guidance creates a clearer checklist of what FDA reviewers expect to see.

For Category 1 submissions (modified devices, low risk impact):

• A brief conclusion on the human factors implications of the modification
• High-level summary of any formative HF activities conducted
• Rationale for why no new critical tasks result from the change

For Category 2 submissions (no critical tasks identified):

• A robust URRA demonstrating no critical tasks exist for the device or that no new critical tasks result from the modification
• Description of the user population, intended use, and use environments
• Rationale for the category selection

For Category 3 submissions (full HF report required):

• Complete HFE/UE report in the revised format outlined in the 2026 guidance
• URRA with critical task identification
• Formative evaluation summaries
• Summative usability study protocol, results, and analysis
• Traceability between critical tasks, test scenarios, and URRA findings
• Justification for participant sample size and test scenario selection

If a manufacturer is uncertain which category applies, the guidance recommends using FDA's pre-submission program to align with the review team before finalizing the HF study plan. [Source: Pure Global, FDA Human Factors Guidance 2026 Update, June 2026]

Implications for QMS Design Control Processes

The 2026 final guidance has direct implications for how medical device companies structure their design control processes within their Quality Management Systems.

Human factors planning must begin earlier. Decision Point D considerations — use history, interface complexity, and risk control adequacy — require data that is only available if HF activities are tracked systematically from the earliest stages of development. A company that waits until pre-submission to think about HF documentation will find it difficult to build a robust justification retrospectively.

Critical task identification must be traceable. Every critical task identified in the URRA must map to a test scenario in the summative study (if one is conducted) or appear explicitly in the justification (if testing is forgone). This traceability requirement means the URRA cannot be a static document — it must remain linked to design decisions throughout development.

HF study records must be maintained regardless of submission category. Because FDA has signaled that inspectors may request HF records during QMSR inspections even for Category 1 and 2 devices, QA teams must treat HF records as a standard component of the Design and Development File — not a submission-only artifact.

For medical device companies managing design controls across multiple products or development programs, this level of traceability demands a structured quality management platform. Maintaining HFE/UE reports, URRA records, formative evaluation data, and summative study records in disconnected systems — shared drives, email threads, or spreadsheets — creates the exact documentation gaps that FDA investigators identify as findings.

Cloudtheapp's cloud-based QMS platform supports full design control documentation, including the traceability structures required for HFE integration into the Design and Development File. Design inputs, outputs, verification records, validation records, and risk documentation all live in a single, configurable, FDA-validated environment — making URRA traceability and HFE report management a structured process rather than a manual effort. [Request a demo at https://www.cloudtheapp.com/demo/]

The July 22, 2026 FDA Town Hall

FDA has scheduled a Town Hall discussion for July 22, 2026, specifically to discuss the final guidance. This is an important opportunity for manufacturers to hear directly from FDA reviewers and, in some cases, submit questions for discussion.

Quality and regulatory teams should monitor FDA announcements for registration details and prepare questions in advance — particularly around Decision Point D application, the scope of the pre-submission program for HF category alignment, and expectations for HF records during QMSR inspections.

Conclusion

The May 2026 final guidance on human factors engineering is not a radical departure from existing expectations. FDA has not invented new requirements — it has clarified, refined, and made more actionable the framework that has governed HFE submissions for years. The introduction of Decision Point D gives manufacturers real flexibility for well-justified submissions, and the expanded appendix examples give quality teams concrete reference material for a wide range of device types.

What the guidance demands is rigor: a well-documented URRA, disciplined traceability, organized HF records, and a human factors process that begins at the start of design and continues through the life of the submission. For companies that already embed these practices into their design control workflows, the 2026 guidance is a welcome formalization. For companies that treat HFE as a submission-stage task rather than a development-integrated discipline, the guidance signals that FDA's tolerance for incomplete or retroactive HF documentation is decreasing.

Medical device quality teams that want to build compliant, inspection-ready human factors documentation programs can request a demo of Cloudtheapp's design control and risk register management capabilities at https://www.cloudtheapp.com/demo/.

Sources: FDA Final Guidance: Content of Human Factors Information in Medical Device Marketing Submissions, May 2026 | Emergo by UL, Key Updates in the Final FDA Guidance, May 2026 | FDA Law Blog, FDA Issues Final Guidance for Content of HF Information, June 2026 | Pure Global, FDA Human Factors Guidance 2026 Update, June 2026 | FDA, Applying Human Factors and Usability Engineering to Medical Devices, 2016 | NAMSA, Regulatory Framework for Human Factors and Usability Engineering, April 2026 | IEC 62366-1:2015, ISO.org

This post created by and appeared first on Cloudtheapp