MR//OS Board

Documentation Standard

ISO 14971

The risk management standard for medical devices: one process for finding hazards, deciding which risks are acceptable, and showing that the controls work.

Full title
Medical devices — Application of risk management to medical devices
Current edition
ISO 14971:2019 (third edition), confirmed in ISO’s 2025 review
Guidance
ISO/TR 24971:2020 explains how to apply it
Applies to
All medical devices, including software as a medical device and in vitro diagnostics, across the whole life cycle
Used by
FDA-recognized. Harmonised in the EU as EN ISO 14971:2019+A11:2021. Required by IEC 62304, IEC 60601-1 and ISO 13485

In short

Risk is the combination of the probability that harm occurs and the severity of that harm. The standard requires a manufacturer to define in advance what level of risk is acceptable, then work through every hazard systematically and keep the evidence in a risk management file. It does not set the acceptable levels. The manufacturer does, and has to justify them.

The process

  1. Risk management plan. Scope, responsibilities, the criteria for risk acceptability, how controls will be verified, and how information will be collected after release.
  2. Risk analysis. Intended use and reasonably foreseeable misuse; the characteristics that affect safety; hazards, the sequences of events that lead to hazardous situations, and the harm that could follow; an estimate of each risk.
  3. Risk evaluation. Each estimated risk is compared with the acceptability criteria.
  4. Risk control. Options are taken in a fixed order of priority: inherently safe design first, then protective measures, then information for safety. Each control is verified as implemented and as effective, and checked for new risks it might introduce.
  5. Residual risk. Each remaining risk is evaluated, with a benefit-risk analysis where a risk is not acceptable and cannot practicably be reduced further. The overall residual risk is then evaluated as a whole.
  6. Risk management review. Before release: the plan was carried out, the overall residual risk is acceptable, and the means to collect post-production information are in place.
  7. Production and post-production. Complaints, field data, literature and changes in the state of the art are reviewed and fed back into the file.

Key terms

On a software project

Worth knowing

Official sources

A summary for orientation. It is not regulatory or legal advice, and it is no substitute for the standard or regulation itself. Requirements change: confirm the current edition before relying on anything here. Last reviewed November 2026.