How to Conduct Risk Analysis – Part 1

Every early-stage medical device startup I’ve worked with has either overlooked risk analysis entirely or treated it as something to “handle later.”

Here’s the hard truth: 

Failing to understand and address your technology’s risks early isn’t a shortcut – they will resurface later, at the expense of your regulatory submission and commercialization.  

If you are an early-stage med-tech entrepreneur still in the conceptual phase, you’ve found this article at exactly the right time. But do not skim it. Learn and apply the concepts here if you want the most efficient path forward.

If you are approaching the point where a Quality Management System must be implemented, you are behind, and you should expect development timelines to slip as a result. However, although the best time to plant a tree was a year ago, the second-best time is today, so you should not let this oversight stop you from execution. On the contrary, you should plant the tree and begin watering it immediately.


What Risk Means in Medical Device Development

In medical device development, risk is a function of :

The severity of potential patient harm, and the probability that harm occurs, as a result of foreseeable events associated with your technology.

In other words, risk is the predictable consequence of how your device can fail, how those failures manifest in the real world, and how patients are ultimately affected.

To evaluate and control risk, medical device development relies on two distinct yet interconnected analyses:

  • Hazard Analysis (HA)
  • Failure Modes and Effects Analysis (FMEA)

Each looks at the same system from a different direction. Neither is sufficient on its own.


Hazard Analysis (HA): The Patient-Centric View

Hazard analysis outlines the pathway for how a hazard can lead to patient harm. Its purpose is to identify unacceptable patient outcomes and understand what sequence of events could plausibly create the conditions for those outcomes to occur.

At its core, hazard analysis connects three elements:

  • Hazard: A potential source of patient harm arising from the nature of the device or its use.
  • Hazardous Situation: A specific condition in which a patient is exposed to the hazard.
  • Harm: The actual injury or damage experienced by the patient (e.g., injury, impairment, or death).

In practice, hazard analysis asks:

  • How could this technology realistically harm a patient?
  • What sequence of events would need to occur for that harm to happen?
  • How severe would the outcome be?

Because this requires clinical judgment, hazard analysis is most effective when performed or reviewed by physicians, clinicians, or subject-matter experts familiar with the intended use of the technology. Clinicians often identify hazardous situations that engineers miss—not due to an engineer’s lack of skill, but rather due to a lack of exposure to real-world clinical workflows.


Failure Modes and Effects Analysis (FMEA): The Engineering View

Failure Modes and Effects Analysis takes the opposite approach. It begins at the component or subsystem level of your technology and progresses upward to system-level consequences.

In an FMEA, engineers examine:

  • The intended function of a component or subsystem
  • How that function could fail (failure mode)
  • How that failure affects the parent assembly or system (effect)

Typical FMEA questions include:

  • What is this component supposed to do?
  • How could it fail to do that?
  • If it fails, what happens to the system?

On its own, FMEA tells you how the device can fail—but not whether that failure is dangerous to a patient.

That connection comes from hazard analysis.


Where Hazard Analysis and FMEA Connect

Now this is where the magic occurs!

Hazard analysis and FMEA are separate activities, but they are intentionally linked.
They meet at the point where a system-level effect creates a hazardous situation.

Here’s a useful way to visualize this relationship :

As I briefly alluded to earlier, a complete and thorough risk analysis demands both Hazard analysis and FMEA. Otherwise, you will fall into two distinct categories:

  1. Teams that perform FMEA without hazard analysis often:
    • Optimize reliability without addressing patient safety
    • Miss catastrophic but low-frequency harms
    • Underestimate regulatory expectations
  2. Teams that perform hazard analysis without FMEA identify serious risks, but:
    • Fail to understand the root cause of failures
    • Struggle to design effective controls


Both of these scenarios carry significant patient risk, and as medical device developers, your primary responsibility is to improve patient outcomes, not deteriorate them.

However, when executed comprehensively :

  • Hazard analysis defines what must never happen
  • FMEA explains how it could happen anyway

Together, they form the backbone of safe, defensible medical device development, and give you, the design authority,  a development roadmap for a safe and compliant technology.


How this works in practice

Imagine you are developing a system that delivers fluid from a bag to a cell culture vessel using a pump. This fluid sets the final cell concentration of a therapy.

For proper treatment:

  • Target delivery rate: 200 ml/min
  • Acceptable tolerance: ± 5 ml

Anything outside that window compromises therapy quality or patient safety.


Hazard Analysis Pathway

Step 1: Identify a Hazard
Air in line

Step 2: Identify the sequence of events
A clinician incorrectly primes the system, leaving air bubbles in the line; The infusion proceeds.

This step is often overlooked, but it is critical. If you do not explicitly describe how a hazard becomes a hazardous situation, you will miss severe patient risks.

Step 3: Define the Hazardous Situation
Air enters the patient.

Step 4: Identify the Harm
The patient suffers an air embolism, which may lead to stroke or death.

At this point, you know that air in line represents a serious hazard with catastrophic potential if not controlled.


FMEA Pathway

Now you analyze the system bottom-up.

Step 1: Identify a component
O-ring
(Its function is to create a seal that prevents liquids from exiting and contaminants from entering.)

Step 2: Identify a failure mode
Loose or damaged seal.

Step 3: Identify the system-level effect
A low-pressure region forms, pulling air into the fluid line.

Here’s the key connection:

A component-level failure (O-ring seal) creates a system-level effect (air drawn into line), which enables the hazard previously identified in the hazard analysis.

This is how FMEA and hazard analysis reinforce each other.


Your Assignment

At this stage, your task is simple:

  1. Meet with your stakeholders and identify your hazards
  2. Define the hazardous situations that expose patients to those hazards
  3. Map component-level failure modes that could plausibly create those situations

If you cannot draw a clean line from component failure to patient harm, your risk analysis is incomplete.


Final Thoughts on Risk Analysis

A common mistake is believing risk analysis must be exhaustive to be valuable.

However, early-stage risk analysis is not about completeness.
It is about directional correctness. Every hazard or failure mode you identify and mitigate brings you one step closer to a safe and effective product.

Additionally, refrain from making the excuse not to begin risk analysis until you have a prototype. Waiting until then guarantees your most dangerous risks will surface at the most inopportune times.