# How to research an EU regulatory question without being misled by AI

> Fix the context first: product, procedure, member states and date. Then find the governing source, check that it is current and final, read the conditions around the passage, and verify every material claim against it — whether the claim came from a colleague, a consultant or an AI tool. AI is fast at finding and comparing candidate sources. It is unreliable at knowing which one applies today.

Canonical: https://rafihive.com/insights/research-eu-regulatory-question-ai  
Author: RafiHive Regulatory Team, RafiHive  
Category: AI in Regulatory Affairs  
Published: 2026-10-16  
Last reviewed: 2026-10-16

## Start with the question, not the search

Most regulatory research goes wrong before the first search. 'What do we need to submit for a new batch release site?' has no single answer. It depends on the product, how it was authorised, where it is marketed and when the change will be implemented. An answer that ignores any of those can be correct in general and wrong for you.

Write the context down before searching, and give it to any AI tool you use. A tool that is not told the procedure will assume one, usually without saying so.

- Product: chemical or biological active substance, generic or reference product, and any special category such as an advanced therapy or an orphan medicine.
- Authorisation route: centralised, mutual recognition, decentralised or purely national.
- Member states concerned, and which one is the reference member state for an MRP or DCP product.
- Lifecycle stage: development, initial application, post-authorisation or renewal.
- The date that matters: when the change is implemented or the application is submitted, not the day you happen to be researching.

## Which source actually governs the answer?

EU regulatory sources are not equal. Legislation binds. A Q&A answer explains how an authority applies it. A consultancy article or an AI answer is at most a pointer to where to look. Before relying on anything, place it in this order.

| Level | Examples | How to use it |
| --- | --- | --- |
| EU legislation | Directive 2001/83/EC, Regulation (EC) No 726/2004, the Variations Regulation (EC) No 1234/2008 as amended | Legally binding. A directive applies through national transposition, so check the national law where it matters. |
| Commission guidelines and the Notice to Applicants | Variations Guidelines C/2025/5045, EudraLex Volume 2 | The Commission's reference interpretation of procedures and dossier content. Not legislation, but departing from it needs a justification. |
| EMA guidance | Scientific guidelines; procedural guidance and Q&As for centralised products | Scientific guidelines are relevant whatever the authorisation route. Procedural Q&As describe how EMA runs centralised procedures. |
| CMDh guidance | Best practice guides, Q&As, Article 5 recommendations | How the mutual recognition and decentralised procedures work in practice, as agreed between national authorities. |
| National authority guidance | Fees, language requirements, national forms, national-only procedures | What one member state requires on top of the EU baseline. |
| Secondary sources | Consultancy articles, training material, conference slides, AI answers | A lead to a primary source. Never the evidence itself. |

Two traps sit inside this table. A lower-level document is often more specific and more current than the one above it, so it is frequently the right place to read, but it cannot override the level above. And the same topic can be covered at three levels in slightly different words. When they differ, the difference is the finding.

## Is the source current, final and the version you think it is?

Superseded regulatory documents rarely disappear. Old guideline PDFs stay online, are linked from other pages and are quoted in the text AI models were trained on. Status therefore needs checking separately from content.

The EU variations framework is the clearest recent example. The Commission's 2013 variations guidelines were replaced by C/2025/5045, which applies from 15 January 2026, and the classification codes changed with them. A document that still uses the old structure is not wrong about history. It is wrong about today.

The wider framework is moving too. The Council adopted the new EU pharmaceutical package on 28 September 2026 and Parliament's vote is pending. Until the new Directive and Regulation are published and apply, Directive 2001/83/EC and Regulation (EC) No 726/2004 remain the law. A source that discusses the new rules describes what is coming, not what applies now.

- Is it adopted, or a concept paper or draft released for consultation? Drafts show direction, not requirements.
- Does it state a date of coming into effect, and has that date passed?
- Has it been revised or replaced? Check the authority's current page, not the PDF already on your drive.
- Does it carry a revision number, and is it the one your colleagues and the authority are using?
- Was it written under a framework that has since changed?

## Read the conditions, not only the matching sentence

Search, by a person or by an AI tool, finds the sentence that matches the question. In regulatory text the answer is usually in what surrounds it: the conditions that must all be met, the documentation that must be supplied, the footnote that narrows the scope, the definition two pages earlier.

A variation classification entry is a good test. The entry that looks like your change applies only if every listed condition is fulfilled. When one is not, the change belongs in a different category. An answer that quotes the entry without checking each condition against your facts has not answered the question.

## Where AI helps, and where it misleads

Used well, an AI tool removes the slowest part of research. Used carelessly, it removes the checking. The difference is knowing which tasks it does reliably.

| Task | Where AI helps | Where it misleads |
| --- | --- | --- |
| Finding candidate sources | A fast first pass across many documents | Proposes documents that are superseded, or that do not exist |
| Summarising a long guideline | Quick orientation to structure and scope | Drops conditions, exceptions and footnotes |
| Comparing two versions | Lists differences a reader would miss | Misses changes in parts it did not retrieve |
| Applying a rule to your product | Sets out which facts matter | Fills missing facts with assumptions it does not state |
| Keeping to the jurisdiction | Separates EU, national and other regions when told to | Mixes FDA terms, other regions or other procedures into an EU answer |
| Citing the source | Links each statement to a passage when built on retrieval | Produces well-formatted references to the wrong version or location |

The last row is serious enough to have its own article, linked below: in regulatory work a citation is the audit trail, and a confident reference to the wrong version tends to pass straight into a draft.

## A verification routine for every material claim

A material claim is one a decision rests on: a classification, a timeline, a document requirement, a condition. Each one gets the same check, whoever or whatever produced it.

1. List the material claims in the answer. Skip the background; check what the decision depends on.
2. For each claim, open the primary source it relies on, not a summary of it.
3. Confirm the version, status and date against the authority's current page.
4. Find the passage and read the conditions, definitions and footnotes around it.
5. Check the legal weight: legislation, guideline, Q&A, recommendation or draft.
6. Check that it applies to your context: this product, this procedure, these member states, this date.
7. Record the source, version, location and the date you checked, so the next reviewer does not repeat the search.
8. Mark what is still uncertain instead of resolving it silently.

## When should you stop searching and decide, or ask?

Research ends in one of three places. The sources answer the question, and you document it. The sources conflict or are silent, and someone has to make a judgment and record why. Or the question needs the authority: a change no classification entry covers, a national divergence, a procedure where the view of EMA or the reference member state decides the outcome.

For changes the classification annex does not foresee, the framework has its own mechanism: a classification recommendation under Article 5 of the Variations Regulation. EMA and CMDh publish the recommendations already given. Checking those first often answers the question, and if it does not, it shows what a request needs to contain.

None of these endings is for an AI tool to choose. An agent can show that the sources are silent. A professional decides what to do about it.

## How RafiHive fits into this routine

RafiHive is built for the middle of the routine: finding the sources, checking their status and laying out the evidence. It answers from a reviewed knowledge base of EU/EEA official sources with version and status metadata, cites the sources it used so each claim can be opened and checked, and returns a not-found result when the sources do not support an answer. It does not know your product's facts unless you provide them, and it does not make the final call. The verification routine above applies to its output too, and every output requires qualified review.

## Official sources

- [Directive 2001/83/EC on the Community code relating to medicinal products for human use](https://eur-lex.europa.eu/eli/dir/2001/83/oj)
- [Regulation (EC) No 726/2004 (centralised procedure and EMA)](https://eur-lex.europa.eu/eli/reg/2004/726/oj)
- [Commission Regulation (EC) No 1234/2008 (Variations Regulation), consolidated version](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02008R1234-20250101)
- [Commission Guidelines C/2025/5045 on the categories of variations and the procedures](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52025XC05045)
- [European Commission: EudraLex Volume 2, Notice to Applicants](https://health.ec.europa.eu/medicinal-products/eudralex/eudralex-volume-2_en)
- [EMA: Scientific guidelines](https://www.ema.europa.eu/en/human-regulatory-overview/research-development/scientific-guidelines)
- [EMA: Classification of changes — questions and answers](https://www.ema.europa.eu/en/human-regulatory-overview/post-authorisation/classification-changes-questions-answers)
- [CMDh: Procedural guidance on variations](https://www.hma.eu/human-medicines/cmdh/procedural-guidance/variation.html)
- [EMA and HMA: Guiding principles on the use of large language models in regulatory science and for medicines regulatory activities](https://www.ema.europa.eu/en/documents/other/guiding-principles-use-large-language-models-regulatory-science-medicines-regulatory-activities_en.pdf)

## Changes since first publication

- 2026-10-16: First published. A source-first routine for researching EU regulatory questions with or without AI tools.

This content supports research and preparation. Confirm current source versions and have a qualified regulatory professional review decisions before use.