What is ISO 14971 (Medical devices: Application of risk management to medical devices)?

ISO 14971 is the international standard for risk management of medical devices, including software as a medical device. It sets the process for identifying hazards, estimating and evaluating the associated risks, controlling them, and monitoring whether the controls work.

The current version is the third edition, ISO 14971:2019, published on December 10, 2019. It defines terminology, principles, and a process for managing risk, and its scope explicitly includes software as a medical device and in vitro diagnostic devices. It requires the manufacturer to set objective criteria for risk acceptability, but it does not say what risk levels are acceptable. That decision belongs to the manufacturer and has to be justified. Risk management can be part of a quality management system, but the standard does not require one. Guidance on applying it is published separately as ISO/TR 24971.

How it connects to software and FDA

FDA's 2023 guidance on device software functions lists ISO 14971 next to IEC 62304 among the consensus standards it harmonized with, and asks for a risk management file in every software submission: a risk management plan, a risk assessment showing that risks have been appropriately mitigated, and a risk management report. The same risk thinking decides the Documentation Level. A sponsor considers all known or foreseeable software hazards, including reasonably foreseeable misuse and the chance that inadequate cybersecurity compromises the device, before risk controls are applied. If a software failure could cause a hazardous situation with a probable risk of death or serious injury, Enhanced Documentation applies.

What it looks like day to day

  • A hazard analysis that lists what the software could do wrong and what harm could follow.
  • Risk controls traced to requirements, so every control is built and tested.
  • Verification that each control works, linked back to the hazard it addresses.
  • Monitoring of whether the controls stay effective after release, so the file stays current.

Example

A remote monitoring dashboard shows each patient's latest blood pressure. A hazard: the device stops syncing and the dashboard keeps showing a three-day-old reading as if it were current, so a clinician misses a deterioration. Risk controls: show the measurement time next to every value, flag readings older than a set threshold, and alert when a device goes silent. Each control becomes a requirement with a test, and the residual risk is judged against the acceptability criteria the manufacturer set at the start.