The ISO 14971 risk management process helps medical device manufacturers identify hazards, estimate and evaluate risks, put appropriate controls in place, and monitor whether those controls remain effective. It applies across a device’s life cycle—from early design through production and post-production—not only when preparing for a regulatory submission.
For manufacturers, the process provides a consistent way to make and record safety decisions. It applies to medical devices, including software and in vitro diagnostic (IVD) devices. ISO 14971:2019 sets out the process, but it does not prescribe universal acceptable risk levels; manufacturers establish criteria suited to the device and its intended use. The current edition was reviewed and confirmed by ISO in 2025. (ISO 14971:2019; FDA recognition record)
What is the ISO 14971 risk management process?
ISO 14971 describes an ongoing, documented process for identifying hazards and hazardous situations associated with a medical device, estimating and evaluating related risks, controlling unacceptable risks, and monitoring control effectiveness. Manufacturers apply it throughout the device life cycle and use the results to inform design, development, production, and post-production decisions.
A hazard is a potential source of harm. A hazardous situation occurs when people, property, or the environment are exposed to a hazard. Harm is injury or damage to health. Risk combines the probability of harm and its severity. These terms help a cross-functional team explain what could go wrong, how exposure could happen, and what the possible consequences are.
The standard’s process includes risk analysis, risk evaluation, risk control, evaluation of overall residual risk, risk management review, and production and post-production activities. The work may be iterative: a design change or new field information can send the team back to reassess earlier decisions. (FDA’s ISO 14971:2019 record)
Is ISO 14971 mandatory for MDR, IVDR CE marking and FDA 510(k)?
Risk management is a legal requirement in the EU and an expectation of FDA. ISO 14971 itself is a voluntary standard, but it is the harmonised (EU) and FDA-recognised way to show that your process meets those requirements. In practice, notified bodies and FDA reviewers expect to see risk management aligned with ISO 14971.
EU MDR 2017/745 – medical device CE marking
- What the regulation requires
- Article 10(2) requires manufacturers to establish, document, implement and maintain a risk management system. Annex I, General Safety and Performance Requirements (GSPR) 3 and 4, sets out what that system must do, including the priority order for risk controls.
- Where ISO 14971 fits
- EN ISO 14971:2019+A11:2021 is harmonised under the EU MDR. Applying it gives a presumption of conformity with the related GSPRs, and its Annex Z shows which requirements it covers.
- What the notified body checks
- Risk management outputs, including the benefit-risk analysis, form part of the MDR technical documentation reviewed before a certificate is issued.
Related: Medical device CE marking services
EU IVDR 2017/746 – IVD CE marking
- What the regulation requires
- The IVDR mirrors the MDR: Article 10(2) requires a risk management system, and Annex I GSPR 3 and 4 define how risks are identified, controlled and reduced as far as possible.
- Where ISO 14971 fits
- The same harmonised edition, EN ISO 14971:2019+A11:2021, applies to IVDs. Analysis should cover the specific risks of an IVD, such as false positive or false negative results and their effect on patient management.
- How it is shown
- Manufacturers usually trace each risk control to the relevant requirement in an IVDR GSPR checklist.
Related: IVD CE marking services
FDA 510(k) premarket notification
- What FDA requires
- Since 2 February 2026, FDA’s Quality Management System Regulation (21 CFR Part 820) incorporates ISO 13485:2016, which requires a documented risk management approach across product realization. See FDA QMSR requirements.
- Where ISO 14971 fits
- FDA recognises ISO 14971:2019 as a consensus standard, so manufacturers can cite it, including through a declaration of conformity, to support their risk analysis.
- What reviewers look for
- A 510(k) submission typically summarises hazards, risk controls and their verification. FDA guidance on device software functions and cybersecurity asks for risk management documentation as part of the premarket submission.
Related: FDA 510(k) clearance services
Using one ISO 14971 process for all three routes avoids running separate risk assessments for the EU and the US. Regional requirements, such as EU benefit-risk wording or FDA software documentation levels, can then be added on top of the same analysis.
The six stages of the ISO 14971 risk management process
1. Plan the risk management activities
Start by defining the device, intended use, life-cycle phases, responsibilities, review points, and methods the team will use. Set the criteria for risk acceptability before evaluating individual risks. The criteria should be justified for the device and its users; ISO 14971 does not give manufacturers a universal risk matrix or a single acceptable-risk threshold.
Planning also identifies how the team will verify risk controls, evaluate overall residual risk, and gather production and post-production information. A clear plan helps ensure risk decisions are made consistently and reviewed by people with suitable product, clinical, engineering, quality, and regulatory knowledge.
2. Analyze risks
Risk analysis identifies foreseeable hazards and hazardous situations, estimates the associated risks, and records the reasoning. Begin with the intended use and reasonably foreseeable misuse. Consider the device’s characteristics, users, use environment, interfaces, materials, energy sources, and life-cycle activities such as transport, installation, maintenance, and disposal.
For each potential sequence of events, describe how a hazard could lead to exposure and harm. Then estimate risk using the methods and criteria established in the plan. Teams may use qualitative or quantitative approaches, depending on the available evidence and the device. The key is to make assumptions visible, use a consistent method, and explain uncertainty rather than treating a number as more precise than the evidence allows.
3. Evaluate each risk
Compare each estimated risk with the acceptability criteria set during planning. Record whether it is acceptable or whether risk control is required. This decision should follow the defined criteria and be supported by evidence, not simply by a statement that the device meets a general industry practice.
If a risk is acceptable under the established criteria, document the rationale. If it is not acceptable, move to risk control. A change to intended use, design, user population, or available evidence may require the team to revisit its analysis and evaluation.
4. Control risks and verify the controls
For risks that require action, identify suitable control measures and implement them. ISO 14971 describes a priority order: make the device inherently safe through design; add protective measures in the device or manufacturing process; then provide information for safety, such as warnings, limitations, or instructions. Information for safety should not replace a practicable design or protective control.
After implementation, verify that each control is in place and effective. Then assess whether the control introduced new hazards, created new hazardous situations, or changed existing risks. Re-estimate and re-evaluate affected risks. If a residual risk remains unacceptable, consider further controls or a change to the device or intended use.
5. Evaluate overall residual risk and review the process
Individual residual risks may each meet their criteria while the combined residual risk still needs review. Evaluate the overall residual risk using the approach established in the plan. If it is not acceptable, consider additional controls or whether the anticipated benefit outweighs the remaining risk, as allowed by the standard and applicable regulations. Document the reasoning and any information that needs to reach users.
Before release, review whether the plan was followed, risk management activities are complete, controls were implemented and verified, and overall residual risk is acceptable. Record the review and its conclusions. This stage supports a reasoned release decision; it does not replace other required design, verification, validation, or regulatory activities.
6. Collect and review production and post-production information
Risk management continues after release. Establish ways to collect relevant information from production, complaints, servicing, users, distributors, literature, and other sources appropriate to the device. Review it to identify new hazards, changes in known risks, control failures, or trends that could affect safety.
When new information may affect the risk analysis, update the relevant assessment and controls. Feed the conclusions into design changes, labeling, training, corrective actions, and other applicable processes. This feedback loop keeps risk decisions current as the device, its use, and available evidence evolve.
How does risk management connect to the QMS and device documentation?
Risk management should connect with the manufacturer’s quality and product realization processes. For example, design reviews, supplier controls, production controls, complaint handling, and post-market surveillance can generate information that affects the risk analysis. The specific records and their format depend on the organization and the applicable requirements.
ISO 14971 calls for documented risk management activities and results. The records should make it possible to understand the device, the assumptions made, the hazards considered, the decisions reached, the controls selected, and the evidence that controls were implemented and reviewed. Related records are often kept together for traceability, but the standard does not require every record to sit in one physical document.
For IVD manufacturers, the same process applies, with analysis tailored to the test’s intended purpose, specimen types, users, workflow, and potential consequences of incorrect results. For software-containing devices, consider software-related hazards and foreseeable use conditions alongside the device’s other risks. Link risk decisions to the relevant development, verification, and post-market activities.
Common process problems to avoid
- Starting with a risk matrix alone: First define the intended use, foreseeable misuse, hazards, hazardous situations, and possible harms. A matrix cannot replace that reasoning.
- Treating risk management as a one-time submission task: New design, production, complaint, or post-market information can require reassessment.
- Using vague hazard statements: Describe the sequence of events and exposure that could lead to harm.
- Relying on warnings too early: Consider design and protective controls first, then provide information for remaining risks.
- Leaving criteria or assumptions unexplained: Document how acceptability decisions were reached and what evidence supports them.
- Failing to check for new risks from controls: A control can change the device or its use and may introduce another risk.
ISO 14971 risk management process: frequently asked questions
Does ISO 14971 define acceptable risk levels?
No. Manufacturers establish risk acceptability criteria appropriate to the device and its intended use, and document the rationale. Applicable regulatory requirements may also affect the assessment.
Does ISO 14971 apply to IVDs and medical device software?
Yes. ISO describes the standard as applicable to medical devices including software as a medical device and IVD medical devices. The analysis should reflect the product’s specific intended use and foreseeable use conditions. (ISO overview)
Is risk management finished when the device is released?
No. Production and post-production activities are part of the process. Manufacturers collect and review relevant information and reassess risks when new evidence may affect prior conclusions.
Is ISO 14971 certification required?
ISO 14971 specifies a risk management process; it does not itself create a product certification. Manufacturers should determine which conformity assessment and regulatory requirements apply in each market. In the United States, FDA maintains a database identifying recognized consensus standards and the extent of recognition. (FDA standards database)
Summary
The ISO 14971 risk management process is a life-cycle method: plan the work, analyze hazards and risks, evaluate them against defined criteria, implement and verify controls, review overall residual risk, and continue monitoring after release. Clear reasoning, traceable records, and feedback from production and post-production help manufacturers make and maintain safety decisions for medical devices and IVDs.
For practical examples of records and templates, see I3CGLOBAL’s medical device risk management report and plan and ISO 14971 risk management plan and benefit-risk assessment resources.


Residual risk is risk remaining after taking control measures. Overall residual risks are estimated by considering each individual residual risks which are further evaluated as per the benefits of the intended use of the medical device for acceptability.
Non-acceptable risks are reduced as much as possible using additional risk control measures.
Possible changes are proposed at design stage or therapeutic options are used to avoid exposure to that risk or reduce the overall risk.
Yes, the information on the residual risk passed to the customer, reduces the estimated risk. This passed information alert the user with information on risks inherent to device use and enable them to make informed decisions on whether to use this medical device in a particular situation or to choose a different medical device, considering condition of the individual patient.