In this episode, Etienne Nichols sits down with Staci Miller, a Human Factors and UX Strategist at GenUX, to demystify the role of human factors (HF) in the medical device regulatory pathway. Staci explains that many companies mistakenly treat HF as a "box-checking" exercise late in development, leading to costly submission delays or rejections when the FDA finds the documentation fails to tell a cohesive safety story.

The conversation dives deep into the technical distinctions between a Use-Related Risk Analysis (URRA) and a User Failure Mode and Effects Analysis (uFMEA). Staci provides a framework for deciding which approach fits your product, emphasizing that while large conglomerates with post-market data may lean toward uFMEAs, startups and those with novel devices should prioritize the URRA to effectively map out user interactions without the crutch of existing market data.

Finally, Staci addresses one of the most persistent myths in the industry: the idea that clinical trial data can replace human factors validation. She clarifies that while the two can overlap in specific, premeditated circumstances (such as complex implants like aortic valves), they serve entirely different masters—one focused on clinical efficacy and the other on the safety of the user interface across diverse environments.

Key Timestamps

04:12 – The common disconnect: Integrating Human Factors into ISO 14971 risk management.
06:45 – URRA vs. uFMEA: How to choose based on your post-market data and predicate device status.
10:30 – The "Definition of Done": Tracking the lifecycle of HF documentation from phase zero to market release.
13:15 – System errors vs. Use errors: How to identify root causes during summative studies.
18:50 – The "Clinical Trial Myth": Why efficacy data is not the same as usability validation.
22:10 – Design Inputs vs. Design Outputs: The "Blueprint and the House" analogy for FDA submissions.
25:40 – The impact of the "Use Environment": Testing for movement in ambulances and lighting in radiology suites.

Quotes

"The FDA doesn't put things out there just to have a good time... If they've made human factors a requirement and you're treating it as a 'suggestion,' you're giving yourself enough rope to hang yourself." - Staci Miller

"People are obsessed with the product themselves—the design outputs. But the FDA wants to see the design inputs. They want to see the blueprints of how you built that house, not just the wallpaper." - Staci Miller

Takeaways

Premeditation is Key: If you intend to use clinical trial data for HF validation, it must be planned in the protocol from the start; you cannot retroactively claim clinical data satisfies usability requirements.
Map User Groups Early: Distinguish clearly between primary and secondary users. Bloating user sets without explaining how or why they engage with the device complicates your risk profile.
Environment Matters: Documentation must account for the physical "10,000-foot view," including noise, lighting, and motion (e.g., an ambulance), as these are often where critical use errors occur.
HF is Risk Management: Human factors should not live in a silo. It must align with the scales of harm (negligible to catastrophic) defined in ISO 14971 and work in tandem with Quality and Regulatory teams.

References

ISO 14971: The global standard for the application of risk management to medical devices.
FDA Human Factors Guidance: The primary document outlining expectations for usability testing and documentation.
Etienne Nichols: LinkedIn Profile

MedTech 101: URRA vs. uFMEA

Think of a uFMEA (User Failure Mode and Effects Analysis) like a car manufacturer looking at an old model to see why the brakes failed in the past—it relies on known data to fix specific parts.

A URRA (Use-Related Risk Analysis) is like teaching someone to drive a brand-new type of vehicle (like a spaceship) for the first time. Since you don't have "crash data" yet, you have to carefully map out every single step the pilot takes and imagine every possible way they could push the wrong button in the heat of the moment.

Feedback Call-to-Action