Ask five compliance leads at pharma companies whether the EU AI Act applies to their quality systems, and you'll get five different answers. That's not because the regulation is vague. Regulation (EU) 2024/1689 is actually fairly precise about what it covers. It's because most of the AI running inside a pharmaceutical quality operation today — a chatbot that drafts CAPA narratives, a model that flags anomalous batch trends, a copilot that helps write validation protocols — doesn't fit neatly into the categories the law was built around.
I'm Jared Clark. I advise regulated manufacturers on quality systems through Certify Consulting, and the question I get most often right now isn't "are we compliant" — it's "does this even apply to us." That's the right question to start with, because the honest answer is: it depends on what the AI does, not on the fact that your company makes drugs.
This guide walks through where the AI Act actually touches pharma operations, where it doesn't, and what a practical compliance program looks like given the timeline you actually have.
What the EU AI Act Regulates, in Plain Terms
The AI Act entered into force on August 1, 2024. It doesn't regulate "AI in pharma" as a category. It regulates AI systems based on the risk their intended purpose creates, and it sorts those systems into tiers: prohibited practices, high-risk systems, limited-risk systems subject to transparency duties, general-purpose AI models, and everything else.
The classification runs through two tracks. Article 6(2), paired with Annex III, lists specific standalone use cases the law treats as high-risk regardless of industry — biometric identification, employment screening, access to essential services, critical infrastructure management, and a handful of others. Article 6(1) takes a different route: an AI system is high-risk if it is a safety component of, or is itself, a product already subject to EU harmonization legislation listed in Annex I — and that Annex I list includes the Medical Devices Regulation (EU) 2017/745 and the In Vitro Diagnostic Regulation (EU) 2017/746.
That second track is the one that actually catches pharma and device makers. A quality management system, a document control platform, a training-record tracker — none of those are medical devices, and none of them show up in Annex III's use-case list. An AI-driven diagnostic algorithm embedded in an IVD instrument, or software that is itself a medical device under MDR, is a different story entirely. Same statute, completely different exposure.
The Compliance Timeline: Which Deadline Is Actually Yours
The Act phases in over roughly three years rather than landing all at once, and the phase that matters to you depends on which track above you're on.
- February 2, 2025 — Article 5's prohibited practices and the Article 4 AI literacy obligation took effect. This is the narrowest tier: manipulative subliminal techniques, exploitation of vulnerabilities, social scoring, and similarly banned practices. Very little pharma manufacturing or quality software touches this category, but HR-adjacent AI screening tools used in hiring can.
- August 2, 2025 — Obligations for providers of general-purpose AI (GPAI) models took effect, along with the governance structure: the AI Office, national market surveillance authorities, and the penalty framework itself. If your quality team is using a large language model to draft SOPs or search deviation records, the model provider's obligations under Article 53 sit here — your obligations as a deployer come later and are lighter.
- August 2, 2026 — This is the big one for most high-risk Annex III use cases. Full high-risk obligations — risk management, technical documentation, human oversight, conformity assessment — become enforceable.
- August 2, 2027 — Per Article 113(c), high-risk systems that are safety components of products under Annex I harmonization law (MDR, IVDR, machinery, and similar) get the longest runway, because their conformity assessment gets folded into the existing notified-body process those regulations already require.
If your AI use case is a QMS feature, a manufacturing analytics tool, or a documentation copilot, none of these deadlines force a conformity assessment on you today. If your AI use case is embedded in a regulated medical device or IVD, August 2, 2027 is your real deadline — but the groundwork for that assessment, especially data governance and technical documentation, needs to start well before then.
Risk Tiers and Where Pharma AI Actually Lands
| Risk Tier | Legal Basis | Typical Pharma/Device Example | Core Obligation |
|---|---|---|---|
| Prohibited | Article 5 | Manipulative AI screening candidates without disclosure | Banned outright since Feb 2, 2025 |
| High-risk (Annex III use case) | Article 6(2) | AI-based candidate screening for GMP roles; AI controlling access to critical infrastructure | Risk management, conformity assessment, human oversight — enforceable Aug 2, 2026 |
| High-risk (Annex I product) | Article 6(1) | AI algorithm inside an IVD instrument; AI-enabled Software as a Medical Device | Same obligations, folded into MDR/IVDR notified-body process — enforceable Aug 2, 2027 |
| Limited risk / transparency | Article 50 | Internal SOP chatbot; AI-drafted CAPA or deviation narratives | Disclose that content or interaction is AI-generated |
| GPAI model | Article 53 | Foundation model powering a documentation copilot | Provider-side technical documentation and copyright compliance — since Aug 2, 2025 |
| Minimal/no risk | Article 95 (voluntary) | Predictive maintenance on non-safety equipment; QC trend analysis | No mandatory obligation; voluntary codes of conduct encouraged |
Most of what a quality department deploys day-to-day — document control, training tracking, CAPA management, supplier risk scoring — lands in that bottom row or in the transparency row, not in the high-risk tiers. That's worth saying plainly, because a lot of vendor marketing right now leans on AI Act anxiety to sell "compliance" features nobody's obligations actually require yet.
Where the AI Act Meets GMP and Annex 11
The AI Act doesn't replace your existing computerized-systems obligations — it stacks on top of them. EudraLex Volume 4 Annex 11 already requires validation, audit trails, and access control for any computerized system used in a GMP process. 21 CFR Part 11 imposes the equivalent duties on the FDA side for electronic records and signatures. If you're deploying AI inside a GMP-regulated workflow, Annex 11 validation obligations don't go away because the tool is "AI" — they run in parallel with whatever AI Act tier applies.
There's a real synergy here, though. Article 12 of the AI Act requires high-risk systems to automatically generate logs across their lifetime. Article 26 requires deployers of high-risk systems to retain those logs for at least six months, unless a stricter EU or national retention rule already applies — and in GMP, it usually does. Article 17 requires providers of high-risk AI systems to maintain a documented quality management system covering the AI's entire lifecycle, which is a structural cousin of the pharmaceutical quality system you already run under ICH Q10. None of this is coincidental. The AI Act's drafters borrowed heavily from product-safety and quality-management logic that GMP-regulated industries already live inside.
The European Medicines Agency has been mapping this overlap directly. EMA's reflection paper on the use of artificial intelligence in the medicinal product lifecycle, published for public consultation in July 2023, sorts AI use into tiers roughly mirroring the AI Act's own logic: AI used in drug development and manufacturing that isn't part of the product itself, AI embedded in a diagnostic or treatment device, and AI that is itself part of a medicinal product's design. If you're building a compliance program, read the AI Act for the legal obligation and EMA's reflection paper for how the regulator expects to apply it to your specific submissions and inspections.
If you haven't validated your current QMS software against Part 11 and Annex 11 yet, that's the more urgent gap — an AI feature bolted onto an unvalidated system doesn't become compliant because you addressed the AI Act and ignored the underlying platform. My colleagues and I have written a detailed walkthrough of that validation process that's worth reading before you tackle AI-specific obligations on top of it.
Building a Compliance Program: What Actually Needs to Happen
Inventory first, classify second. You cannot assess risk tier for AI you haven't cataloged. List every AI-enabled tool touching quality, manufacturing, clinical, or regulatory workflows — including the ones your team adopted informally, like a general-purpose chatbot someone started using to draft investigation reports. That last category deserves particular scrutiny: pasting batch records or deviation data into a public LLM interface creates a data governance problem under Article 10 of the AI Act long before it creates a high-risk classification problem, and it creates a GMP data-integrity problem regardless of what the AI Act requires. I've written separately about why general-purpose chat tools are a bad fit for quality records — that risk exists independent of AI Act enforcement dates.
Classify against Article 6, not against fear. For each system, ask two questions: does it fall into an Annex III use case, and is it a safety component of a product under Annex I harmonization law? If the answer to both is no, you have a transparency or minimal-risk obligation, not a conformity assessment burden. Don't let a vendor's compliance messaging talk you into treating a QMS feature like a regulated medical device algorithm.
Assign provider vs. deployer roles honestly. Most pharma companies buying AI-enabled software are deployers under the Act, not providers. Deployers of high-risk systems have real but narrower duties: use the system per the provider's instructions, maintain human oversight, monitor for malfunction, retain logs, and inform the provider or authority of serious incidents. The heavier conformity-assessment and technical-documentation burden sits with whoever built and placed the system on the market — your software vendor, if you bought rather than built.
Fold AI governance into the quality system you already run. Article 17's QMS requirement for high-risk providers and Article 9's risk-management-system requirement both echo structures ICH Q9 and Q10 already expect from you. Don't build a parallel "AI compliance" program — extend your existing quality system's document control, CAPA, and risk-management processes to cover AI as a system category, the same way you'd extend them to cover a new piece of manufacturing equipment.
Penalties for Getting This Wrong
Article 99 sets a tiered penalty structure. Violations of the Article 5 prohibited practices carry fines up to €35 million or 7% of global annual turnover, whichever is higher — the steepest tier in the regulation. Violations of most other AI Act obligations, including high-risk system requirements, top out at €15 million or 3% of turnover. Supplying incorrect, incomplete, or misleading information to authorities or notified bodies carries penalties up to €7.5 million or 1% of turnover. These figures apply per Article 99(3)–(5) and scale by company size for SMEs, but the top-line exposure for a mid-size or large pharma manufacturer is real enough to justify getting the classification step right rather than guessing.
The Practical Takeaway
Most quality and manufacturing AI tools in a pharma operation today sit outside the AI Act's high-risk tiers — but that status depends entirely on staying outside Annex III use cases and Annex I product safety components, and vendors change what their tools do more often than compliance teams re-run the classification. Treat AI Act classification as a living assessment tied to your AI inventory, not a one-time memo, and you'll spend far less time reacting to each new deadline as it arrives.
If you're evaluating how an AI-native quality platform handles logging, human oversight, and audit-trail requirements that both the AI Act and Annex 11 expect, Nova QMS's platform page walks through how those controls are built into the system rather than bolted on afterward.
Frequently Asked Questions
Does the EU AI Act apply to pharmaceutical companies specifically? No — the Act doesn't single out pharma as an industry. It applies based on what a specific AI system does. A pharma company using AI in a way that matches an Annex III use case, or as a safety component of a device regulated under Annex I legislation like MDR or IVDR, takes on high-risk obligations. A pharma company using AI for document control or training tracking generally does not.
Is an AI feature inside our QMS or LIMS "high-risk" under the Act? Almost always no, unless that specific AI feature is itself a safety component of a regulated medical device or falls into one of the Annex III use cases (biometric ID, employment decisions, critical infrastructure, and similar). Most QMS and LIMS AI features — anomaly detection, document search, drafting assistance — fall into the transparency or minimal-risk tiers instead.
How does the AI Act interact with GMP Annex 11 and 21 CFR Part 11? It stacks on top rather than replacing them. Annex 11 and Part 11 validation, audit trail, and access control obligations apply to any computerized system used in a GMP process, AI-enabled or not. The AI Act adds AI-specific duties — logging, human oversight, data governance — on top of that existing validation baseline for systems that meet its risk thresholds.
What's the real deadline we need to plan around? It depends on your risk tier. Most high-risk Annex III obligations become enforceable August 2, 2026. High-risk systems that are safety components of Annex I products, like AI embedded in a medical device or IVD, get until August 2, 2027 because their conformity assessment routes through the existing MDR/IVDR notified-body process.
What happens if we misclassify or ignore an obligation? Penalties scale by violation type. Prohibited-practice violations reach up to €35 million or 7% of global turnover. Most other high-risk obligation violations top out at €15 million or 3% of turnover. Supplying misleading information to authorities carries penalties up to €7.5 million or 1% of turnover.
Last updated: 2026-09-20
Jared Clark
Principal Consultant, Certify Consulting
Jared Clark is the founder of Certify Consulting, helping organizations achieve and maintain compliance with international standards and regulatory requirements.