Healthcare Quality Assurance

Medical device risk assessment isn’t just about what goes wrong but how it harms the patient/user ↴ Let's review some definitions: ✓ Harm = Injury or damage to the health of people, or damage to property or the environment. ✓ Hazard = Potential source of harm. ✓ Hazardous Situation = Circumstance in which people, property, or the environment is/are exposed to one or more hazards. ✓ Risk = Probability (P) of harm × Severity (S) of harm. Always remember: when answering ISO 14971, you're addressing this sequence: Hazard → Events → Hazardous Situation → Harm Note: One hazard can lead to multiple hazardous situations, which can lead to multiple harms. Don't forget that probability (P) can be split into: → P1 = Probability of a hazardous situation occurring. → P2 = Probability that situation causes harm. (This will be useful later.) Now, practical application: A device fails. A patient suffers. But was it direct harm… or indirect? That depends on your device.↴ Some devices fail, and the harm is immediate. Example: Hip prosthesis → A microcrack forms unnoticed. → The implant breaks inside the body. Direct Harm? ↳ Severe pain & immobility. ↳ Infection from broken implant fragments. Here's another example where the device isn’t the direct cause but still leads to harm. Example: Incorrect diagnostic output → A diagnostic device fails to detect a critical condition. → A clinician makes a wrong decision based on faulty data. → Outcome? Delayed/misguided treatment & more. To address indirect risks, I like to do this: → Assess risk across the entire system. → If multiple devices interact = System of Systems (SoS), analyze all interactions, sequence of events of your SoS (Device 1 ↔ Device 2 ↔ Patient) This is where splitting P1 & P2 can be a valuable strategy: → Helps understand event interactions. → Enables a combined risk approach for a comprehensive SoS risk assessment. I always ask myself this when evaluating an SoS: What is the probability of harm resulting from every hazardous situation? Need more for your medical device risk management ? Using our risk management template & methodology as a guide, you will be able to: → Use compliant process with ISO 14971 and MDR → Use a clear ISO 14971 methodology → Present your data clearly → Use tools proven in audits (our Hazard Traceability Matrix, RMP, and RMR). → Save time – no need to create templates from scratch. Our Risk Management bundle: https://lnkd.in/eTw2VVXp

Risk Management in Medical Devices: More Than a Checklist In medical devices, risk management is not a one-time activity—it’s a continuous process that directly impacts patient safety and product reliability. Under ISO 14971 and aligned with ISO 13485, risk management is integrated into every stage of the product lifecycle—from design to post-market use. At its core, risk management is about answering three simple but critical questions: What can go wrong? How likely is it? And what is the impact? The process typically begins with hazard identification. This involves identifying all possible sources of harm—electrical, mechanical, biological, usability-related, or even software failures. In daily work, this often happens during design discussions, failure analysis, or even while reviewing customer complaints. Once hazards are identified, the next step is risk analysis and evaluation. Here, risks are assessed based on severity and probability. Not all risks can be eliminated, but they must be reduced to an acceptable level. This is where teams often make a mistake—accepting risks without proper justification or documentation. The most critical step is risk control. Controls can include design changes, protective measures (like alarms or insulation), or clear instructions in labeling. The priority should always be to eliminate risk through design rather than relying only on warnings or user instructions. An important but often overlooked aspect is residual risk evaluation. Even after controls are applied, some level of risk remains. This must be evaluated to ensure it is acceptable when weighed against the device’s benefits. Risk management does not stop after product release. Through post-market surveillance, real-world data such as complaints, adverse events, and user feedback must be continuously reviewed. If new risks are identified, they should feed back into the risk management file and trigger updates. In practice, risk management is closely linked with CAPA, design changes, and regulatory compliance. A poorly maintained risk file is one of the most common findings during audits. A mature organization treats risk management not as documentation, but as a decision-making tool. It guides design choices, improves product safety, and builds confidence with regulators and users. Ultimately, effective risk management ensures that innovation does not come at the cost of safety—and that every device delivered performs reliably in real-world conditions.

One question that has become increasingly relevant over the last few years is how to apply ISO 14971 to machine learning-enabled medical devices 🤖 I’m happy to see the publication of ISO/TS 24971-2:2026, Medical devices — Guidance on the application of ISO 14971 — Part 2: Machine learning in artificial intelligence. This Technical Specification provides practical guidance for manufacturers developing ML-enabled medical devices, as well as regulators, notified bodies, and others responsible for assessing their safety and performance. Rather than introducing a new risk management process, ISO/TS 24971-2 provides guidance on how to apply the risk management process of ISO 14971 to ML-enabled medical devices (MLMD). Among the topics covered are: 🔹 Bias and representative training data 🔹 Transparency and explainability 🔹 Model retraining and performance drift 🔹 Varying levels of autonomy 🔹 Post-market monitoring 🔹 Practical examples of hazards, hazardous situations and risk control measures It has been a privilege to contribute to the development of this Technical Specification as part of ISO/IEC JWG1 alongside an exceptional group of international experts. My sincere thanks go to our convenor Jos van Vroonhoven, project leader Pat Baird, and every member of the working group for their expertise, dedication and collaboration throughout the project. Developing international standards is a collaborative effort built on technical debate, compromise and consensus, making this publication a particularly rewarding milestone 🎉 With the publication of ISO/TS 24971-2, attention now turns to the ongoing development of ISO/TS 24971-3, addressing the application of ISO 14971 to combination products. I also look forward to contributing to the newly initiated revision of ISO/TR 24971-1, which will further strengthen guidance on the application of ISO 14971. 📚 Further information and sources: ISO/TR 24971-1: https://lnkd.in/ezCQJT4q ISO/TS 24971-2: https://lnkd.in/eBBkXpFD ISO/TS 24971-3: https://lnkd.in/eM4CihaD

The Traceability Matrix Nobody Talks About 🔗 Everyone knows you need traceability in medical device development. User Needs → Requirements → Verification → Design Outputs But here's the traceability most teams forget: Requirements → Risks Why this matters: When a risk is mitigated through design (not procedures or training), you need a requirement to capture that mitigation. Example: Risk: "Patient data transmitted over network could be intercepted" Mitigation: Encryption Requirement: "The system must encrypt all patient data using AES-256 during transmission." Without this traceability, you can't prove your risk controls are implemented. ISO 14971 requires it. FDA expects it. But we see this missing all the time. The consequences: ❌ Risk analysis looks incomplete ❌ Requirements don't reflect mitigations ❌ FDA asks: "How did you implement this risk control?" ❌ Scramble to create documentation after the fact The fix: Create explicit links between your risk analysis and requirements. Every design-based mitigation should trace to at least one requirement. Simple. Often overlooked. Always important. 📖 Discover how proper traceability accelerates our FDA submissions: https://hubs.li/Q03MPfdV0 #RiskManagement #MedicalDevices #ISO14971 #FDA #MedTech #QualityManagement

At the heart of developing safe and effective products lies the integration of risk management and design inputs. According to ISO 13485, design inputs should consider the outputs of risk management. That means your risk controls, identified during early hazard analysis, should directly inform and shape your design inputs. When risk control measures are integrated early and iteratively into the design input process, they become more than theoretical mitigations. They drive real, traceable, and testable requirements that guide development and verification. Why is this critical? ✅ It ensures that risk controls are built into the product by design, not bolted on later.  ✅ It reduces the chance of late-stage surprises, redesigns, and delays.  ✅ It creates a clear traceability matrix from hazards to risk controls to design inputs to design verification.  ✅ And most importantly, it keeps patient safety at the forefront from day one. 🔗 This integration supports ISO 14971 and ISO 13485 expectations, strengthens your DHF, and provides a strong narrative for audits and submissions. How do you ensure your risk management outputs drive your design inputs? #MedicalDevices #CombinationProducts #RiskManagement #DesignControl #ISO14971 #ProductDevelopment