Your source for AI, quality, and compliance updates, insights and best practices across the life sciences industry.

Most discussions about the MDR and IVDR transition focus on deadlines, delays, and notified body bottlenecks. But for many manufacturers, the real, lasting effect has emerged elsewhere. The transition has not just changed when  things need to be done—it has changed how  regulatory scope must be defined, structured, and defended. For the first time in years, the question is no longer just whether requirements have been identified, but whether the very structure for managing th

Most regulatory teams believe they have control over their Applicable List. It exists. It gets updated now and then. It has worked so far. But audit exposure rarely arises from obvious omissions—a forgotten regulation, an overlooked standard. It emerges more subtly. It begins when confidence in the list's reliability gradually erodes, without anyone really noticing. As regulatory scope expands—across markets, product variations, and new domains such as cybersecurity and AI—ma

Regulatory failures rarely start with a warning letter, a rejected submission, or a failed audit. They usually start much earlier, with small assumptions, unclear ownership, or requirements that nobody realised they were responsible for. The following cases are based on real patterns observed in audits, MDR reviews, and industry practice. The companies are anonymous and composite, but the situations are entirely realistic. Case 1: The Requirement Nobody Owned The situation A

Most Applicable Lists are built around a single primary framework. For medical device manufacturers, that framework is often MDR or IVDR. The structure reflects the regulation: articles, annexes, essential requirements. Applicability decisions are made within that defined scope, documented, and maintained accordingly. This model works as long as regulatory obligations are treated as largely self-contained. Increasingly, they are not. When scope no longer fits inside one regul

Traceability problems in applicability rationales Most organisations can point to an Applicable List and say, “This is where our applicability decisions live.” On paper, that suggests control. In practice, many teams find that while decisions are documented, the reasoning behind them is far less robust. The decision is there, but the path that led to it is harder to follow. Over time, rationales fade, fragment, or become tied to specific individuals. What remains is an applic

What a regulatory update actually is — and how it is typically consumed A regulatory update is rarely one clear, isolated event. In practice, it shows up in many different ways: a revised guidance document, a new interpretation from an authority, an updated standard, a position paper from a notified body, or a clarification buried in a Q&A or raised through supervisory expectations. Together, these updates add up to a steadily growing layer of regulatory material that sits al

Auditors keep finding the same applicability problems When auditors identify issues related to applicability, they are rarely isolated mistakes. Instead, the same types of observations surface repeatedly, even in organisations with mature quality systems and experienced RA teams. Requirements are marked as non-applicable without a clear legal anchor, rationales cannot be traced back to regulatory text, or applicability decisions differ between products and markets without a d

REACH obligations escalating toward 2026 introduce direct manufacturing risk for Life Science companies using PPP-related substances, biocides and intermediates. This document translates regulatory exposure into concrete RA/QA checkpoints, decision gates and accountability models to ensure manufacturing continuity, GMP compliance and audit-ready control of substance dependencies.

Explore top AI platforms transforming RAQA processes, from regulatory tracking to clinical trials and document automation.

The Compliance Matrix Isn’t Optional – Building a Defensible List of Applicable Requirements Theme:  ISO 13485:2016 §4.2.1, §4.1.6 · MDR Annex II §4 · IVDR Annex II §4 · PRRC Oversight · FDA QMSR Alignment Introduction Most regulatory teams can show you a list of “applicable regulations and standards.”Far fewer can show how  that list was built, why  each item is included or excluded, and what process  keeps it current. In 2025, that’s a problem — and auditors know it. The r

This edition provides a structured framework to build an audit-ready justification system that aligns technical, clinical, and regulatory evidence into a coherent and defensible chain of reasoning.

Hoodin is pleased to announce a new partnership with Tenax Enterprises , a Pretoria-based regulatory and quality consultancy with a...

Theme: ISO 13485 §4.1.3 • MDR Article 10.9 • Annex II Section 4 This Month’s Focus Traceability is not just about knowing what changed....

Establishing full regulatory control and QMS integration Under Article 15  of the MDR and IVDR, the Person Responsible for Regulatory...

We’re excited to announce that as of today , Hoodin’s Smart Compliance List (SCL)  has expanded to cover North America  – including US...

One of the top reasons Technical Files fail audits is lack of traceability and version control. Article 10.9, Annex II & III, and ISO 13485 §4.1.3 all demand that: If your Applicable List of Regulations is static, undocumented, or unclear, you will not be able to defend your legacy position — nor demonstrate that you have system-level regulatory control.

Linking GSPR claims to current regulations, standards, and common specifications.

Closing Legacy Gaps Starts with a Traceable, Auditable Applicable List Most RA/QA teams are now in the middle of Article 120-based legacy...

System-level execution for MDR, IVDR, and ISO 13485 §4.1.3 You’re likely knee-deep in technical documentation updates, legacy device...

Missed the webinar or want to revisit key insights? Access the full recording, presentation slides, and practical AI tools for transforming your compliance strategy.