The QM toolbox: FMEA

Martin Bosch

25/06/2019

Failure modes and effects analysis (FMEA) is a risk management method. ISO 14971 states:

"Failure Mode and Effect Analysis (FMEA) and Failure Mode Effect and Criticality Analysis (FMECA) are techniques that systematically determine the effect or significance of individual components; they are more suitable for a more sophisticated design."

When used consistently, FMEA is an important tool in the medical device manufacturer's toolbox. FMEA can be used in a variety of areas, such as process FMEA (PFMEA) to evaluate failure modes in processes or design FMEA (DFMEA) to identify and treat defects in products.

In the development of medical electrical devices, it is typically used at the module level to analyze failure modes and define corrective actions. The best time to perform an FMEA is after the schematic has been created and before the layout, as changes can still be made at this point.

FMEAs are, of course, used not only in medical technology, but also in aircraft construction and the automotive industry. Various organizations provide guidelines and regulations for their implementation; among them, DIN EN 60812 deals with FMEAs.

Terms

The following table shows important terms related to FMEAs.

German English Explanation / Meaning
ID  ID Clear identification of the error (e.g. line number)
Component / Function Item / Function The FMEA refers to components or functions.
Possible error / malfunction Potential Failure Mode What kind of error can occur?
Cause of error Failure Cause What is the cause of the error
Error sequence Effect of Failure What does the error lead to (danger to patients, users or third parties, failure, etc.)
Preventive measure Preventive Action What is being done to prevent the error from occurring?
Discovery measure Detection Action What is being done to identify the error?
Rating (B) Severity (S) How big is the impact of this error?
Probability of occurrence (A) Occurence (O) What is the probability of occurrence?
Probability of detection (E) Detection (D) What is the probability of detection?
RPN (W x A x E) RPN (S x O x D) Risk priority number
Recommended remedial action Recommended Action What is the recommended remedial action?
Measure implemented Actions taken What is the implemented measure?
Rating (B) Severity (S) What is the impact of this error after the action?
Probability of occurrence (A) Occuracy (O) What is the probability of this error occurring after the measure?
Probability of detection (E) Detection (D) What is the probability of detecting this error after the measure?
RPN (W x A x E) RPN (S x O x D) Risk priority number after the measure

Implementation

The FMEA is prepared and conducted in a group setting. Participants in a design FMEA include the module's hardware and firmware developers, the system architect, and possibly quality management staff.
The FMEA should be prepared in advance. However, sufficient time must be planned for its implementation. Depending on the size of the assembly, an FMEA can take from three hours to several days.

Your contact person:
Dipl.-Ing. Martin Bosch, shareholder, hardware developer
E-mail: bosch@medtech-ingenieur.de
Phone:  +49 9131 691 241
 

Do you need support with the development of your medical device? We're happy to help! MEDtech Ingenieur GmbH offers hardware development, software development, systems engineering, mechanical development, and consulting services from a single source. Contact us.

make contact

Proceed

The sequence of the individual error considerations is shown in the following diagram:

FMEA process according to Vandenbrande [3]
Risk priority numbers aren't absolutely necessary in medical technology, as every defect should be considered. No defect is neglected due to a low risk priority number. However, they can help with the assessment and risk evaluation of a defect.

Results of an FMEA

When conducting an FMEA, various results and insights are obtained:

  • Possible errors and failure modes of the module or system.
  • Possible initial errors that endanger patient safety.
  • Notes for necessary self-tests or runtime tests.

The findings from the FMEA can result in new requirements for the system.

Conclusion

Consider FMEA as a useful tool to improve the quality of your products.
If you would like to know more about how we conduct an FMEA, please feel free to write or call us.

Best regards
Martin Bosch

Further information on FMEAs can be found at:
[1] MIL-STD-1629A
[2] Wikipedia
[3] WW Vandenbrande, How to use FMEA to reduce the size of your quality toolbox, Quality Progress, 1998


Written by Martin Bosch

Martin Bosch is a dedicated hardware developer who pursues his passion for electronics at MEDtech Ingenieur GmbH. His expertise includes the development of embedded electronics, specifically for medical applications. His focus is on the design of printed circuit boards and circuits that integrate both microcontrollers and analog circuitry. These are used in a wide variety of devices, from blood analyzers to defibrillators.


More articles

  • 26/11/2025
  • General, Hardware, Standards, Quality, Testing

Why EMC testing is vital in medical technology: Imagine a patient is lying in the hospital during critical monitoring. Suddenly, a visitor's smartphone rings – and the monitoring device... ...

Read more
  • 20/11/2025
  • General, Hardware, Quality, Technology, Testing

Have you ever considered sourcing inexpensive components from China? The temptation is strong, we know that. And we've already gained some experience, from which I... ...

Read more
  • 25/09/2025
  • General, Electrodermal Activity, Hardware, Production

May I introduce you? This is EDA – our owl for electrodermal activity. This is EDA, our little owl with a special talent. EDA can measure electrodermal activity (EDA for short) – ...

Read more
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.