Risk assessments under ISO 14971 and ISO 12100 require systematic hazard identification, risk estimation, and mitigation documentation. Vespper helps you build traceable risk assessments that connect hazards to mitigations to verification evidence.
ISO 14971:2019 (Medical devices — Application of risk management to medical devices) is the internationally recognized standard that establishes the framework for managing risks associated with medical devices throughout their entire lifecycle, from initial concept through design, manufacturing, post-market surveillance, and eventual decommissioning. The standard is harmonized with both the EU Medical Device Regulation (MDR 2017/745) and the U.S. FDA's regulatory framework, making compliance with ISO 14971 effectively mandatory for medical device manufacturers seeking market access in all major jurisdictions. The FDA explicitly recognizes ISO 14971 as a consensus standard, and manufacturers can declare conformity to it as part of their premarket submissions (510(k), PMA, and De Novo). Under the EU MDR, Annex I General Safety and Performance Requirements (GSPRs) require a risk management system that aligns with ISO 14971 principles.
The standard defines risk as the 'combination of the probability of occurrence of harm and the severity of that harm,' where harm encompasses physical injury, damage to health, damage to property, or damage to the environment. ISO 14971 requires manufacturers to establish a documented risk management process that includes risk analysis (systematic identification and estimation of risks), risk evaluation (determining whether risk reduction is required based on defined acceptability criteria), risk control (implementing measures to reduce risks to acceptable levels), and evaluation of residual risk (assessing whether the overall residual risk is acceptable after all controls are applied). The process must be iterative and applied throughout the product lifecycle, not treated as a one-time design phase exercise.
A critical requirement of ISO 14971 is the establishment of a risk management plan before initiating risk management activities. This plan must define the scope of the risk management activities, assignment of responsibilities and authorities, requirements for review of risk management activities, criteria for risk acceptability (including how the manufacturer will determine when risks are acceptable, considering the state of the art and recognized standards), verification activities for risk control measures, and methods for collecting and reviewing post-production information. The risk management file — the compilation of all records and documents produced by the risk management process — must be maintained and updated throughout the product's market life. AI risk assessment writers support compliance by generating structured risk management documentation that maintains traceability from identified hazards through risk estimation, evaluation, control, and verification, ensuring that the risk management file meets the exacting requirements of notified body audits and FDA inspections.
Risk assessment and risk management are related but distinct concepts within the ISO 14971 framework, and understanding their relationship is essential for proper medical device documentation. Risk assessment is one component within the broader risk management process and encompasses three specific activities: risk analysis, risk evaluation, and the overarching assessment of whether identified risks are acceptable. Risk analysis involves systematically identifying hazards, analyzing the sequence of events that could lead to a hazardous situation, and estimating the risk (probability and severity) associated with each hazardous situation. Risk evaluation then compares each estimated risk against the manufacturer's predefined acceptability criteria to determine whether risk reduction is needed. Together, these activities constitute the risk assessment — the analytical process of understanding and characterizing the risks.
Risk management, by contrast, is the comprehensive, lifecycle-spanning process that includes risk assessment but extends far beyond it. ISO 14971 defines risk management as the 'systematic application of management policies, procedures and practices to the tasks of analyzing, evaluating, controlling and monitoring risk.' In addition to risk assessment, risk management encompasses risk control (selecting and implementing measures to reduce unacceptable risks), verification that risk controls are effective and do not introduce new risks, assessment of overall residual risk acceptability, and post-production monitoring to ensure that the risk profile does not change as real-world use data accumulates. Risk management is a continuous process, while risk assessment may occur at specific milestones.
The practical distinction matters significantly for regulatory compliance and documentation. A risk assessment document or report is a snapshot — it captures the identified hazards, estimated risks, and evaluation against acceptability criteria at a point in time. The risk management file, however, is the living compilation of all risk-related documentation that grows and evolves throughout the product lifecycle. Regulatory bodies like the FDA and EU notified bodies expect to see both: the risk assessment demonstrating that hazards were systematically identified and evaluated, and the broader risk management file demonstrating that the manufacturer has an ongoing process for managing those risks. Common audit findings include organizations that perform initial risk assessments during design but fail to update them after design changes, field corrective actions, or receipt of adverse event reports. AI risk assessment tools help bridge this gap by maintaining dynamic risk documentation that can be efficiently updated as new information becomes available.
Hazard identification is the foundational step in the ISO 14971 risk analysis process, and several systematic techniques have been developed to ensure comprehensive identification of potential hazards. Failure Mode and Effects Analysis (FMEA) is the most widely used method in the medical device industry, applied by an estimated 85-90% of device manufacturers according to industry surveys. FMEA works 'bottom-up' by systematically examining each component, subsystem, or process step, identifying the ways it could fail (failure modes), determining the effects of each failure on the system and the patient, and assessing the severity, probability of occurrence, and probability of detection. The result is a Risk Priority Number (RPN) or equivalent risk ranking for each failure mode. Design FMEA (dFMEA) analyzes product design failures, while Process FMEA (pFMEA) analyzes manufacturing and production process failures. IEC 60812:2018 provides the international standard methodology for FMEA.
Fault Tree Analysis (FTA) takes the opposite approach — it is a 'top-down' deductive method that starts with an undesired top event (such as 'patient receives incorrect drug dose' or 'device delivers unintended electrical shock') and systematically traces backward through the logical combinations of component failures, human errors, and environmental conditions that could cause that event. FTA uses Boolean logic gates (AND, OR, NOT) to model the causal relationships, producing a graphical tree structure that can be analyzed both qualitatively (identifying all minimal cut sets — the smallest combinations of failures that cause the top event) and quantitatively (calculating the probability of the top event from component failure probabilities). FTA is particularly valuable for analyzing safety-critical systems where redundancy and independence of safety barriers must be verified. IEC 61025:2006 provides the standard methodology for FTA.
Hazard and Operability Study (HAZOP) is a structured brainstorming technique originally developed for the chemical process industry but increasingly applied to medical devices, particularly those involving fluid handling, gas delivery, or complex process flows. HAZOP uses guide words (No, More, Less, Reverse, Part of, As well as, Other than) applied to process parameters (flow, temperature, pressure, concentration, time) to systematically identify deviations from the intended design and operating conditions. For each deviation, the team identifies potential causes, consequences, existing safeguards, and recommendations for additional risk controls. HAZOP is governed by IEC 61882:2016. ISO 14971 does not mandate any specific hazard identification technique but requires that the chosen method(s) be appropriate for the device and its intended use. In practice, most manufacturers use a combination — typically FMEA as the primary method supplemented by FTA for critical safety functions and HAZOP for process-related hazards. AI risk assessment writers can generate structured templates for all three methods and help ensure consistency in hazard identification across techniques.
Risk estimation under ISO 14971:2019 requires manufacturers to assign both a probability of occurrence and a severity of harm to each identified hazardous situation. The standard allows manufacturers to choose between qualitative, semi-quantitative, and quantitative approaches to risk estimation, depending on the availability of data and the nature of the risk. Qualitative estimation uses descriptive categories (e.g., 'Negligible,' 'Minor,' 'Serious,' 'Critical,' 'Catastrophic' for severity; 'Incredible,' 'Remote,' 'Occasional,' 'Probable,' 'Frequent' for probability), while semi-quantitative approaches assign numerical ranges to these categories. Fully quantitative estimation, which assigns specific numerical probabilities and severity values, is preferred when sufficient data exists but is often impractical for novel devices without predicate performance data. The choice of estimation approach must be documented in the risk management plan.
Risk evaluation is the process of comparing each estimated risk against the manufacturer's predefined acceptability criteria to determine whether risk reduction is required. ISO 14971:2019 made a significant change from the 2007 edition by removing the informative annex that previously described the ALARP (As Low As Reasonably Practicable) concept and the three-zone risk acceptability matrix (broadly acceptable, ALARP region, intolerable). The current edition requires manufacturers to define their own acceptability criteria based on applicable national or regional regulations, relevant standards, and consideration of the generally acknowledged state of the art. In practice, most manufacturers still use a risk matrix approach with defined acceptability zones, but they must now explicitly justify their criteria rather than defaulting to a generic framework. The EU MDR Annex I, Section 2 reinforces this by requiring that risks be reduced 'as far as possible' and evaluated against the benefit to the patient.
A common challenge in risk estimation is distinguishing between the probability of a hazardous situation occurring and the probability that the hazardous situation leads to actual harm. ISO 14971 Clause 5.5 allows manufacturers to consider both the probability of the hazardous situation (P1) and the probability that the hazardous situation leads to harm (P2), where the overall probability of harm is a function of P1 × P2. This decomposition is particularly relevant for medical devices where hazardous situations may arise relatively frequently but the probability of actual harm may be low due to operator intervention, patient variability, or other mitigating factors. However, manufacturers must exercise caution in relying on P2 reductions — overestimating the effectiveness of human intervention or patient resilience is a common audit finding. The estimation must be based on objective evidence, including clinical data, published literature, field experience with predicate devices, and engineering analysis, not optimistic assumptions. AI risk assessment tools facilitate rigorous risk estimation by maintaining databases of severity and probability categories, ensuring consistent application across the product risk analysis, and flagging instances where estimation assumptions may require additional justification.
ISO 14971:2019 Clause 7 establishes a mandatory hierarchy of risk control measures that manufacturers must follow when implementing risk reduction. The hierarchy prioritizes controls in the following order of preference: (1) inherent safety by design, (2) protective measures in the medical device itself or in the manufacturing process, and (3) information for safety, including training of users and maintenance personnel. This hierarchy is not optional — manufacturers must demonstrate that they have considered and, where feasible, implemented controls at each level before relying on controls at a lower level. The underlying principle is that design-level controls are more reliable than protective measures, which in turn are more reliable than relying on human behavior in response to warnings or training.
Inherent safety by design means eliminating the hazard entirely or reducing the risk through design choices that remove or minimize the source of harm. Examples include selecting biocompatible materials that eliminate toxicity hazards, designing electrical systems with low energy levels that preclude harmful shock, using inherently safe mechanical designs that prevent pinch or crush hazards, and incorporating fail-safe defaults that place the device in a safe state upon failure. When inherent safety by design cannot adequately reduce the risk, protective measures provide the second line of defense. These include physical barriers, guards, and interlocks (e.g., a safety interlock that prevents X-ray emission when the chamber door is open), alarm systems that alert users to hazardous conditions, automatic shutdown mechanisms, and software safety features such as input validation and range checking. For software-driven devices, IEC 62304:2006+A1:2015 provides the lifecycle requirements for software safety, with software safety classification determining the rigor of the development process.
Information for safety — the lowest tier of the hierarchy — includes labeling, instructions for use (IFU), warnings, precautions, contraindications, and user training programs. While essential, information-based controls are the least reliable because they depend on the user reading, understanding, and consistently following the information provided. Human factors research consistently demonstrates that warning compliance rates decrease over time and vary significantly based on presentation format, user experience level, and environmental conditions. IEC 62366-1:2015 (Medical devices — Application of usability engineering to medical devices) requires manufacturers to apply usability engineering processes to validate that safety-critical information is effectively communicated to and understood by users. When the risk management process results in residual risks that must be communicated through information for safety, the manufacturer must include these in the accompanying documentation per ISO 14971 Clause 7.4 and evaluate whether users can be expected to recognize and manage these residual risks. AI risk assessment writers help maintain traceability between identified risks and their controls at each hierarchy level, ensuring auditors can verify that the hierarchy was properly applied.
The risk management file is the comprehensive collection of all records and other documents produced by the risk management process, and its completeness is one of the most scrutinized elements during regulatory audits and submissions. ISO 14971:2019 Clause 4.5 specifies that the risk management file must provide traceability for each identified hazard to the risk analysis, risk evaluation, implementation and verification of risk control measures, and assessment of residual risks. The file is not necessarily a single physical document — it may be a collection of documents, databases, and records distributed across multiple systems — but there must be a master index or roadmap that enables auditors to locate all relevant information. Under the EU MDR, the risk management file is part of the technical documentation required by Annex II and must be available for review by notified bodies and competent authorities.
The required contents of the risk management file include: the risk management plan (defining scope, responsibilities, acceptability criteria, and review requirements), the risk analysis records (hazard identification, hazardous situations, harm identification, and risk estimation for each identified hazard), the risk evaluation records (comparison of each estimated risk to acceptability criteria and decision on whether risk reduction is required), the risk control records (identification of risk control measures, implementation evidence, and verification of effectiveness including evidence that controls do not introduce new unacceptable risks), the evaluation of overall residual risk (demonstrating that the totality of residual risks is acceptable when considered collectively, not just individually), the risk management review report (a formal review confirming that the risk management process was executed according to the plan and that results are acceptable), and production and post-production information collection procedures.
A critical and often overlooked requirement is the traceability matrix that links each identified hazard through the complete chain: hazard → hazardous situation → harm → risk estimation → risk evaluation → risk control measure → verification of risk control → residual risk assessment. This end-to-end traceability is what enables regulators and auditors to verify that no hazard has been identified but left without appropriate evaluation and control. The FDA's guidance document 'Factors to Consider Regarding Benefit-Risk in Medical Device Product Availability, Compliance, and Enforcement Decisions' emphasizes the importance of documented benefit-risk analysis as part of the risk management file. Common audit nonconformities include incomplete traceability (hazards identified but not carried through to risk control), absence of risk control verification evidence, failure to assess whether risk controls introduced new risks, and lack of post-market surveillance feedback into the risk management process. AI risk assessment writers maintain this traceability automatically, generating the complete documentation chain from hazard identification through residual risk assessment and flagging any gaps in the traceability matrix.
Post-production risk monitoring is the systematic process of collecting, reviewing, and acting upon information about a medical device after it has been released to the market, with the specific purpose of maintaining the validity and currency of the risk management file. ISO 14971:2019 Clause 10 requires manufacturers to establish, document, and maintain a process for collecting and reviewing production and post-production information relevant to the device's safety. This is not a passive activity — it requires proactive surveillance systems and defined triggers for risk management file updates. The EU MDR further strengthens this requirement through Article 83 (Post-Market Surveillance system), Article 84 (Post-Market Surveillance plan), and Article 86 (Periodic Safety Update Report — PSUR), creating a comprehensive framework for ongoing safety monitoring that is explicitly linked to risk management.
The scope of post-production information that must be monitored includes: adverse event reports and complaints (including data from the FDA's MAUDE database, EU Eudamed, and the manufacturer's own complaint handling system), field corrective actions and recalls (both the manufacturer's own and those of similar devices), published literature and clinical studies relevant to the device or its technology, evolving standards and regulatory requirements, changes in the state of the art for the device's therapeutic area, and user feedback including usability observations. The FDA's 2023 guidance on 'Postmarket Management of Cybersecurity in Medical Devices' adds cybersecurity vulnerability monitoring to this list for connected devices. Each piece of post-production information must be evaluated for its potential impact on the device's risk profile, and where new hazards are identified or existing risk estimates change, the risk management file must be updated accordingly.
The practical challenge of post-production monitoring lies in the volume of data and the need for systematic evaluation. A large medical device manufacturer may have thousands of products on the market, each requiring ongoing surveillance across multiple data sources in multiple jurisdictions. The EU MDR requires that PSUR frequency be proportionate to risk classification — at least annually for Class IIa and higher devices, and at least biennially for Class I devices (Article 86). Failure to maintain adequate post-production surveillance has direct regulatory consequences: the FDA's Quality System Regulation (21 CFR 820.198) requires complaint handling procedures, and inadequate complaint analysis is consistently among the top 5 FDA inspection citations. In the EU, notified bodies verify post-market surveillance effectiveness during annual surveillance audits, and deficiencies can result in certificate suspension. AI risk assessment platforms streamline post-production monitoring by integrating with adverse event databases, automating literature surveillance, and providing structured workflows for evaluating new information against existing risk assessments — ensuring that the risk management file remains a living document rather than a design-phase artifact that gathers dust after market launch.
ISO 14971:2019 defines the risk management framework that medical device manufacturers must follow throughout the product lifecycle.
Different device types require hazard identification methods appropriate to their specific risk profile.
After risk controls are applied, residual risk must be evaluated and the overall residual risk must be acceptable.
Risk management is a lifecycle activity that must incorporate post-market data into ongoing risk assessment.
Build risk assessments where every hazard traces to its risk control measures and verification evidence — no broken links.
Generate risk assessments following ISO 14971 or ISO 12100 process requirements with proper documentation structure.
Upload design specs, test reports, FMEA outputs, and field data. Vespper connects risk findings to the evidence that supports them.
When design changes occur, update your risk assessment with AI assistance and review only the affected hazard-mitigation chains.
Connect design specifications, FMEA outputs, test reports, field complaint data, and applicable standards.
Vespper drafts your risk assessment with hazard identification, risk estimation, and mitigation measures traced to source evidence.
Walk through hazard-mitigation chains, verify risk levels, confirm mitigation adequacy, and export for quality review.
Build traceable, standards-compliant risk assessments connected to your design evidence.
Sign in