How to Read and Cite EU Pharmaceutical Legislation: Regulations, Directives, Decisions and Guidance

1. Why Reading the Right Source Matters

EU medicines regulation is unusually document-rich. A single regulatory question may lead to a Treaty provision, a Regulation or Directive, an implementing or delegated act, an Official Journal publication, a Commission decision, an EMA scientific document, a guideline, a CMDh document and national legislation.

These documents are related, but they are not interchangeable.

A sound regulatory answer therefore begins with a source question:

What is the legal instrument that creates the requirement, and what document explains or applies it?

This distinction is more important than the volume of references in an answer. Ten secondary sources do not compensate for citing the wrong primary legal instrument.

The European Commission describes Volume 1 of EudraLex as the collection of EU pharmaceutical legislation and Volume 2 as Notice to Applicants and regulatory guidance. The Commission also expressly notes that the Notice to Applicants has no legal force and that, in case of doubt, the appropriate Union Directives and Regulations should be consulted. urlEuropean Commission — EudraLex Volume 2https://health.ec.europa.eu/medicinal-products/eudralex/eudralex-volume-2_en

2. Start With the Legal Question, Not the Search Term

Before searching for a document, define what needs to be established.

There is a major difference between questions such as:

• What is the legal basis for an Article 31 referral?
• How is an Article 31 referral normally conducted?
• What happened in a particular referral?
• What does the final decision require the marketing-authorisation holder to do?
• How should a particular submission be prepared?

The first question primarily requires legislation.

The second may require legislation plus current procedural guidance.

The third requires procedure-specific documents.

The fourth requires the operative legal decision and its annexes.

The fifth may require legislation, procedural guidance, templates and authority-specific instructions.

The same subject can therefore require different sources depending on the question being asked.

3. Article 288 TFEU: The Starting Point for Legal Instruments

Article 288 of the Treaty on the Functioning of the European Union identifies the principal EU legal acts: regulations, directives, decisions, recommendations and opinions.

EUR-Lex summarises their basic characteristics as follows:

• regulations are binding in their entirety and directly applicable;
• directives are binding as to the result to be achieved, leaving Member States choice as to form and methods;
• decisions are binding in their entirety, with addressee-specific decisions binding on those to whom they are addressed;
• recommendations and opinions have no binding force. citeturn0search2turn0search3

For medicines regulation, this classification provides the foundation for reading the legislative framework correctly.

It is also the reason why the words “EU guidance” should never automatically be substituted for “EU law”.

4. A Regulation Is More Than a Document Called a Regulation

A regulation is a legal instrument with a defined Treaty-based meaning.

Under Article 288 TFEU, a regulation is of general application, binding in its entirety and directly applicable in all Member States. citeturn0search11

The word directly applicable is particularly important.

It means that the regulation operates in the national legal orders without requiring Member States to transpose the regulation itself into national legislation.

This does not mean that national administrative measures disappear. Member States may still have authorities, procedures and enforcement arrangements through which EU law is administered.

Nor does every document containing the word “regulation” have the same legislative status. A regulation can itself be a legislative act, a delegated act or an implementing act.

The title therefore needs to be read together with the legal basis and adoption procedure.

5. A Directive Works Differently

A directive binds the Member States to the result that must be achieved while leaving them discretion as to the form and methods of implementation, within the requirements of EU law. citeturn0search2

This distinction is fundamental to medicines regulation because major elements of the framework for nationally authorised human medicines are contained in Directive 2001/83/EC.

The practical consequence is that the EU directive and the relevant national implementing legislation may both need to be considered.

A citation to Directive 2001/83/EC can establish the Union legal framework, but it may not by itself answer a question about the exact wording of a national administrative or enforcement requirement.

6. Decisions Must Be Read According to Their Addressee and Function

A decision is binding in its entirety. It may be addressed to specific parties or, depending on its form and legal basis, have broader application. citeturn0search8

This matters in regulatory work because “Commission decision” can describe very different legal situations.

A decision may establish the outcome of a particular Union procedure. It may implement legislation. It may be addressed to particular parties. Or it may form part of a broader legislative or non-legislative framework.

The citation should therefore identify the decision precisely rather than referring vaguely to “an EU decision”.

7. Legislative Acts and Non-Legislative Acts

The terms legislative act and non-legislative act are not synonyms for “important” and “less important”.

Under Article 289 TFEU, legislative acts are adopted through the ordinary or a special legislative procedure. Delegated and implementing acts are non-legislative acts adopted under powers provided by a legislative act. citeturn0search2turn0search6

This distinction becomes particularly useful when a medicines regulation has been supplemented or technically updated.

A regulatory professional should ask:

1. What is the basic legislative act?
2. What power does it confer?
3. Is the subsequent act delegated or implementing?
4. What precisely may that act change or establish?

8. Delegated Acts

Article 290 TFEU permits the EU legislator to delegate to the Commission the power to adopt non-legislative acts that supplement or amend certain non-essential elements of a legislative act. citeturn0search4

The basic legislative act must define the objectives, content, scope and duration of the delegation.

A delegated act cannot alter the essential elements of the basic act.

For a regulatory reader, the important point is that the delegated act must be read with its enabling act.

The delegated regulation or delegated decision does not exist in isolation. Its legal authority comes from the legislative act that delegated the power.

9. Implementing Acts

Article 291 TFEU concerns implementing powers where uniform conditions for implementing legally binding Union acts are needed. citeturn0search7turn0search14

Implementing acts are therefore concerned with the practical implementation of an existing legislative framework rather than the same type of supplementation or amendment performed by delegated acts.

The distinction can be expressed simply:

Basic legislative act
        │
        ├── Delegation under Article 290
        │        ↓
        │   Delegated act
        │
        └── Implementing power under Article 291
                 ↓
            Implementing act

The precise authority must always be checked in the enabling legislation.

10. Why the Distinction Matters in Medicines Regulation

Medicines legislation contains technical requirements that can change as science, technology and regulatory practice develop.

A reader may therefore encounter a principal Regulation or Directive alongside later delegated or implementing measures.

Treating all of these documents simply as “the regulation” obscures the legal structure.

When preparing a regulatory position, record the basic act and the subsequent act separately.

This makes it possible to answer a basic but important question:

Which instrument actually creates the requirement I am relying on?

11. Recommendations and Opinions

Recommendations and opinions are different from binding legal acts under Article 288 TFEU.

EUR-Lex identifies them as non-binding instruments. citeturn0search2turn0search12

This does not make every opinion irrelevant.

In EU medicines regulation, scientific committee opinions can be an important stage in a regulatory procedure and can have substantial procedural consequences. Their legal effect must nevertheless be understood in the context of the legislation governing the particular procedure.

A CHMP opinion, for example, should not automatically be described as though it were the European Commission's final legal decision.

12. Guidance Occupies a Different Layer

Guidance is one of the most frequently misunderstood parts of the EU medicines framework.

The European Commission states that EudraLex Volume 2 contains Notice to Applicants and regulatory guidelines and expressly notes that the Notice to Applicants has no legal force. It directs readers to the appropriate Union Directives and Regulations where doubt exists. citeturn0search0

This does not mean that guidance is unimportant.

Guidance can explain the regulator's expectations, provide procedural detail, standardise submissions and facilitate consistent application of the legislation.

Its practical importance can therefore be very high even when its formal legal status differs from legislation.

13. The Correct Way to Use Guidance

A useful regulatory sequence is:

Legal requirement
       ↓
Applicable procedure
       ↓
Current guidance
       ↓
Procedure-specific instructions
       ↓
Scientific / technical justification

The guidance should help answer how the legal and procedural framework is normally applied.

It should not be used to silently replace the underlying legal requirement.

Where a guideline appears to impose something not readily traceable to legislation or an applicable regulatory requirement, the basis should be investigated rather than assumed.

14. EudraLex: Useful, but Not a Single Legal Instrument

EudraLex is a collection, not one law.

The European Commission describes Volume 1 and Volume 5 as containing the body of EU pharmaceutical legislation for human and veterinary medicines respectively, while other volumes contain different categories of guidance. citeturn0search1

For human medicines, Volume 1 is therefore a primary navigation point for legislation.

Volume 2 contains Notice to Applicants and regulatory guidelines.

Volume 3 contains scientific guidelines.

Other volumes cover specialised areas and their current applicability should be checked because the status of particular volumes can change over time. citeturn0search1

A citation should therefore identify the underlying document, not merely say “EudraLex”.

15. EUR-Lex and EudraLex Serve Different Purposes

The two resources are complementary.

EUR-Lex is the authoritative Union-law portal through which legislation, legal acts, consolidated texts, publication details and related legal information can be retrieved.

EudraLex is the Commission's pharmaceutical-sector collection of legislation and supporting regulatory and scientific guidance.

For a legal citation, EUR-Lex is often the most useful source for identifying the formal legal act, its Official Journal reference, consolidated versions and amendments.

For medicines-specific navigation, EudraLex provides a practical regulatory structure around the pharmaceutical acquis. citeturn0search1turn0search3

16. Read the Official Journal Citation

A formal EU legal citation should normally allow the reader to identify the act unambiguously.

For legislation, that generally means recording:

• the type of act;
• the number;
• the year;
• the adopting institutions where relevant;
• the subject or short title;
• the Official Journal reference;
• and, when relevant, the applicable consolidated version.

For example, Directive 2001/83/EC is much more precise than “the EU medicines directive”.

Similarly, Regulation (EC) No 726/2004 is preferable to “the centralised procedure regulation”.

The precise citation is not cosmetic. It allows another professional to retrieve the same legal instrument.

17. Consolidated Text Versus Original Act

A consolidated text incorporates subsequent amendments into a readable version.

It is extremely useful for understanding the law currently in force.

But a consolidated text is not necessarily the document that originally created the provision.

When analysing a historical regulatory event, the original act and the amendments that were applicable at the relevant date may need to be identified separately.

When answering a current question, the current consolidated version may be the most efficient starting point.

The key is to state which version has been used.

18. Temporal Accuracy in Legal Citation

A legal citation can be technically correct and still produce the wrong answer if the wrong version is used.

Consider a referral procedure initiated several years ago.

If the relevant article has subsequently been amended, a current consolidated text may describe the law today but not necessarily the precise legal framework that governed the historical procedure.

A historical analysis should therefore ask:

What was the applicable law on the date the relevant regulatory event occurred?

This is especially important when reconstructing old referrals, authorisations, variations or safety decisions.

19. Amendments Are Part of the Legal History

When an EU pharmaceutical instrument has been amended, the amendment should not be treated merely as an editorial update.

It may change:

• the legal basis for a procedure;
• the responsibilities of institutions;
• the scope of a provision;
• procedural timelines;
• terminology;
• pharmacovigilance obligations;
• transitional arrangements.

For a live regulatory question, the current applicable text matters. For a historical question, the amendment history matters.

Both are legitimate forms of regulatory research, but they answer different questions.

20. Annexes Are Part of the Legal Instrument

A common reading error is to focus on the main articles while overlooking annexes.

An annex can contain substantive technical requirements, lists, categories, specifications or other material that is legally connected to the instrument.

The reader should therefore check whether the provision being interpreted refers to an annex and whether later amendments have changed that annex.

A citation to the article alone may be incomplete if the operative detail sits in an annex.

21. Cross-References Must Be Followed

EU pharmaceutical legislation contains extensive cross-referencing.

A provision may refer to another article, another legislative instrument, an annex, a delegated act or an implementing measure.

Stopping at the first cited provision can produce an incomplete interpretation.

A practical reading rule is:

Follow every cross-reference that is necessary to determine the legal condition, exception, definition or procedure being applied.

This is particularly important for provisions that contain exceptions or refer to detailed implementing rules.

22. Definitions Can Control the Meaning

Definitions are easy to overlook because they often appear far from the operational provision.

A defined term can determine the scope of an obligation.

Regulatory terms such as “medicinal product”, “marketing authorisation”, “pharmacovigilance”, “risk”, “variation” or “applicant” may have specific legal meanings in the applicable framework.

Before applying ordinary-language meaning to a technical regulatory term, check whether the legislation defines it.

23. Read the Scope Provision First

When opening a Regulation or Directive, do not immediately search for the phrase that appears in the question.

First establish:

1. the purpose or subject of the act;
2. its scope;
3. relevant definitions;
4. the operative provision;
5. exceptions and transitional rules.

This prevents a provision from being applied outside the class of products, persons, procedures or circumstances to which it legally applies.

24. A Four-Layer Reading Method

A reliable method for reading an EU medicines provision is:

Layer 1 — Text

What does the provision actually say?

Layer 2 — Context

What section, chapter, definitions and cross-references surround it?

Layer 3 — Legal status

What type of act is it and how was it adopted?

Layer 4 — Application

What procedure, product or regulatory event is being assessed?

Only after all four layers are understood should the provision be translated into a practical compliance conclusion.

25. A Good Regulatory Citation Is Reproducible

A useful citation should allow another professional to find the same source without relying on the writer's interpretation.

For legislation, a strong citation usually identifies:

Act → provision → version/date → Official Journal or EUR-Lex record.

For guidance:

Issuing body → document title → version/date → official source.

For a procedure-specific document:

Authority → procedure/reference number → document title → date/version.

For a regulatory decision:

Decision-maker → decision number/reference → date → subject/product → applicable annexes.

26. Avoid Citation by Institution Alone

“EMA guidance says…” is often insufficient.

The reader needs to know which guidance document.

Likewise:

• “the Commission decided…”;
• “CMDh states…”;
• “PRAC recommended…”;
• “EU law requires…”

are incomplete statements unless the relevant document or legal provision can be identified.

Institutional attribution tells the reader who said something. A regulatory citation should also tell the reader where and with what authority it was said.

27. Avoid Citation by Search Result

Search engines are useful for finding sources but should not become the source itself.

A search result may point to:

• an outdated version;
• a secondary summary;
• a national mirror;
• an archived document;
• a page whose title has changed;
• or a current page containing several historical documents.

Once the relevant source is located, open the underlying official document and cite that document.

28. The Primary-Source Test

Before relying on a regulatory statement, ask:

Can I trace this statement to a primary legal or regulatory source?

If yes, cite that source.

If no, determine whether the statement is:

• a scientific interpretation;
• a procedural explanation;
• established regulatory practice;
• or the writer's own analysis.

Then label it appropriately.

This is one of the simplest ways to prevent accidental overstatement.

29. Distinguish Law, Guidance and Interpretation in Prose

Compare these statements:

“EU law requires X.”

“The current EMA guidance recommends X.”

“Regulators commonly expect X in practice.”

“A reasonable interpretation is X.”

They do not have the same evidentiary status.

A textbook-quality regulatory article should preserve those distinctions rather than collapsing them into one category called “requirements”.

30. How to Handle an Apparent Conflict

If legislation and guidance appear inconsistent, do not immediately conclude that one source is wrong.

First check:

1. whether the documents concern the same product category;
2. whether they concern the same procedure;
3. whether the same version/date applies;
4. whether an amendment has changed the legislation;
5. whether the guidance is addressing an operational detail rather than changing the legal rule.

If a genuine conflict remains, the applicable legal instrument takes precedence over non-binding guidance.

The discrepancy should be documented and, where appropriate, clarified with the competent authority.

31. The Regulatory Source Record

For important regulatory assessments, maintain a source record containing at least:

This makes the reasoning reproducible when the regulatory environment changes.

32. Why Retrieval Dates Matter

Web-based regulatory documents can change without the page address changing.

A guidance page may be updated while retaining a familiar URL.

A consolidated legal text may incorporate amendments after the original research was performed.

Recording the retrieval date therefore helps distinguish:

• what the source says now;
• what it said when the assessment was performed;
• and what legal version governed the underlying event.

For regulated organisations, that distinction can be important during audits, inspections and retrospective regulatory review.

33. A Practical Citation Template

For a legal provision:

[Instrument], [Article], [consolidated version/date if relevant], [Official Journal/EUR-Lex reference].

For guidance:

[Issuing authority], [document title], [version/date], [official publication source].

For a procedure-specific document:

[Authority], [procedure/reference number], [document title], [date/version].

For a decision:

[Decision-maker], [decision/reference number], [date], [subject], including applicable annexes.

The exact bibliographic convention can vary, but the source should always be uniquely identifiable.

34. What Not to Do

Avoid these common shortcuts:

• citing “EU law” without identifying the instrument;
• citing “EMA guidance” without naming the document;
• using an old consolidated text for a current question without checking its status;
• using a current consolidated text to reconstruct a historical event without checking historical amendments;
• treating an EMA opinion as automatically equivalent to a Commission decision;
• treating guidance as legislation;
• assuming every document in EudraLex has the same legal force;
• relying on a secondary article when the primary source is readily available.

These errors are avoidable with a disciplined source-review process.

35. The Working Principle

The most reliable way to read EU pharmaceutical legislation is to move from authority to application:

Treaty / legal basis
        ↓
Basic EU legislative act
        ↓
Relevant provision and definitions
        ↓
Amendments / consolidated version
        ↓
Delegated or implementing measures
        ↓
Current regulatory guidance
        ↓
Procedure-specific documents
        ↓
Practical regulatory conclusion

The order is not absolute for every research task, but it is a strong default.

It keeps the legal requirement visible while allowing guidance and procedure-specific documents to explain how that requirement operates in practice.

36. Final Principle

The goal of regulatory citation is not to produce the longest reference list.

It is to make the reasoning traceable, current, legally accurate and reproducible.

A reader should be able to move from the conclusion back to the exact legal provision, then forward through the relevant guidance and procedure-specific documents to understand how the conclusion was reached.

That is the standard that makes a regulatory document useful beyond the day on which it was written.

41. How to Cite an EU Regulation

A useful citation should allow another person to identify the instrument without ambiguity.

For a regulation, record at least:

• the institution(s) adopting it;
• the regulation number;
• the year;
• the subject or short title where useful;
• the relevant article, paragraph or annex;
• and the version or date when historical accuracy matters.

For example, a regulatory record may identify Regulation (EC) No 726/2004 and then specify the particular article relied upon.

The purpose is reproducibility: another regulatory professional should be able to retrieve the same provision and verify the conclusion.

42. How to Cite a Directive

For a directive, the citation should identify the directive and the provision being relied upon.

Where the issue concerns a nationally authorised product, the citation may need to continue to the national implementing legislation.

This is especially important when the question concerns an operational national requirement rather than the EU-level legislative objective alone.

A strong regulatory citation can therefore contain two linked sources:

EU Directive provision
        ↓
national implementing provision
        ↓
practical regulatory requirement

The two should not be silently conflated.

43. How to Cite a Commission Decision

A Commission decision should be cited as the specific legal act rather than merely as an EMA event.

Where available, record the decision date, title or subject, identification number and the relevant operative provision or annex.

For a centralised medicinal product, this can be particularly important because the Commission decision represents the legally operative outcome of the Union authorisation procedure.

An EMA scientific assessment can explain why the decision was reached, but it is not necessarily the decision itself.

44. How to Cite EMA Committee Outputs

EMA committee documents should be identified according to their document type.

Examples include:

• CHMP opinions;
• PRAC recommendations;
• assessment reports;
• meeting minutes or highlights;
• procedural documents;
• questions and answers.

Do not describe all of these simply as “EMA decisions.”

The distinction matters because the document's institutional origin and legal function may differ substantially.

45. How to Cite Guidance

For guidance, identify:

1. the issuing body;
2. the title;
3. the version or revision date;
4. the relevant section or chapter;
5. and, where useful, the publication or effective date.

For frequently revised guidance, a version date is particularly valuable.

A citation to “current EMA guidance” without identifying the document can become impossible to reproduce after the guidance is revised.

46. EUR-Lex and the Official Journal

EUR-Lex is the principal EU legal information service and provides access to EU legislation, the Official Journal and other legal material.

The Official Journal of the European Union is the authoritative publication source for EU legal acts.

For legal research, EUR-Lex is often the most practical route to the underlying Official Journal text and subsequent consolidated versions.

The distinction is important because a website displaying a legal text and the underlying publication of that legal act are not conceptually the same thing.

47. Why the Official Journal Matters

EU legislation becomes legally significant through the procedures established by EU law, including publication requirements.

When establishing the historical legal position, the Official Journal publication is therefore an important primary source.

A later consolidated text may be easier to read, but the original publication can be necessary to establish:

• the original wording;
• publication date;
• entry into force;
• amendment history;
• transitional provisions.

48. Consolidated Legislation Is a Research Tool, Not a Time Machine

A consolidated regulation or directive is extremely useful because amendments are incorporated into a single readable text.

But it does not eliminate the need for temporal analysis.

If an event occurred in 2018 and the law was substantially amended in 2023, the current consolidated text cannot automatically be used as evidence of what the law required in 2018.

Historical regulatory reconstruction requires the version applicable at the relevant date.

49. Entry Into Force and Application

Two dates should not be assumed to mean the same thing:

• entry into force;
• date of application.

A legislative act may enter into force on one date while its substantive provisions apply from a later date.

Transitional provisions can create additional complexity.

A regulatory timeline should therefore record the legally relevant date rather than simply the publication date.

50. Transitional Provisions

Transitional provisions determine how a new legal regime interacts with situations that began under an earlier regime.

They may address matters such as:

• applications already submitted;
• existing authorisations;
• ongoing procedures;
• deadlines;
• previously established rights or obligations.

When legislation changes, checking the transitional provisions should be a standard part of regulatory impact assessment.

51. Definitions Are Legally Important

Definitions sections are often underestimated.

A defined term can determine the scope of a legal provision and can differ from ordinary clinical or commercial usage.

Terms such as “medicinal product,” “marketing authorisation,” “active substance,” “risk” or “pharmacovigilance” should therefore be interpreted according to the applicable instrument where the legislation provides a definition.

The regulatory professional should not substitute a colloquial meaning for a defined legal term without justification.

52. Cross-References Need to Be Followed

EU legislation frequently uses cross-references.

A provision may establish an obligation while another article specifies the procedure, an annex defines technical requirements, and a separate instrument supplies implementation details.

Reading only the first article encountered can therefore produce an incomplete interpretation.

A practical rule is:

Follow every cross-reference that is necessary to understand the condition, scope, exception or consequence of the provision being applied.

53. Annexes Are Part of the Legal Instrument

Annexes should not be treated as optional background material.

Depending on the instrument, an annex may contain substantive requirements, classifications, technical information or procedural details that are essential to interpreting the operative articles.

A regulatory review that cites the main article while ignoring an applicable annex can therefore be incomplete.

54. Exceptions and Special Rules

A broad legal rule may be followed by exceptions, special provisions or conditions.

This is common in medicines legislation because different categories of products and procedures can have different requirements.

A reliable reading method is therefore:

General rule
    ↓
Scope
    ↓
Definitions
    ↓
Exceptions
    ↓
Special provisions
    ↓
Procedure
    ↓
Consequence

The conclusion should only be drawn after this chain has been checked.

55. Guidance Often Explains the “How”

Legislation may establish that a regulatory activity must occur without explaining every operational detail.

Guidance frequently provides the practical framework for carrying out that activity.

For example, legislation may establish a pharmacovigilance obligation while GVP describes detailed expectations concerning system operation, processes and documentation.

This is why guidance can be indispensable without becoming legislation.

56. When Deviation From Guidance Is Considered

A deviation from guidance is not automatically unlawful.

The correct analysis depends on the underlying legal requirement, the status of the guidance and the circumstances of the deviation.

Where a company follows an alternative scientifically justified approach, the regulatory record should make clear:

• what legal requirement is being satisfied;
• what guidance expectation differs;
• why the alternative is appropriate;
• what evidence supports it;
• and whether regulatory agreement or notification is required.

The phrase “we did not follow the guideline” is therefore not, by itself, a complete compliance assessment.

57. The Difference Between “Must,” “Should” and “May”

Regulatory wording matters.

Words such as shall, must, may, should and can can have different legal or procedural significance depending on the instrument and context.

A guidance document using “should” should not automatically be read as imposing the same legal obligation as a legislative provision using binding language.

Conversely, a repeated “should” expectation can represent an important regulatory standard even when it is not itself statutory wording.

The document's legal status must therefore be considered alongside its vocabulary.

58. Scientific Conclusions Are Not Automatically Legal Conclusions

A scientific assessment may establish that a risk exists, that evidence supports an association, or that a benefit-risk balance has changed.

The legal consequence may then require a separate regulatory act.

This distinction is particularly important in pharmacovigilance:

Scientific evidence
       ↓
Scientific assessment
       ↓
Committee conclusion
       ↓
Regulatory procedure
       ↓
Legally operative action

The exact sequence depends on the procedure.

A scientific conclusion should not be described as a legal obligation unless the applicable legal framework gives it that effect.

59. How to Resolve an Apparent Conflict

When two regulatory sources appear inconsistent, use a structured approach.

First: verify that they concern the same subject, product category and date.

Second: establish their legal status.

Third: identify the legal basis of the lower-level document.

Fourth: check amendments, transitional provisions and procedure-specific rules.

Fifth: determine whether the apparent conflict is actually a difference in scope or terminology.

Only after these checks should a genuine conflict be recorded.

60. A Practical Evidence Table

For important regulatory questions, a simple evidence table can prevent source confusion.

This format is particularly useful during inspections, audits and regulatory intelligence reviews.

61. Regulatory Citations Should Be Reproducible

A citation is not merely a decoration at the end of a paragraph.

Its purpose is to allow the reader to verify the proposition.

A strong citation should answer:

• What document?
• Which version?
• Which provision?
• What date?
• Where can it be retrieved?

For high-consequence regulatory conclusions, the underlying primary source should normally be retained in the regulatory record according to applicable document-management procedures.

62. Avoid Citing Search Results as Regulatory Authority

Search engines are discovery tools, not legal authorities.

A search result may point to an outdated copy, a secondary explanation or a document whose context is unclear.

Use search to locate the source, then verify the actual source.

This distinction becomes especially important when regulatory terminology is reused across commercial websites, consultancy material and agency publications.

63. Avoid Treating Secondary Summaries as Primary Sources

Secondary sources can be excellent for orientation.

They can explain a complex procedure quickly and can help identify relevant legislation.

But when the conclusion matters, return to the primary source.

A useful workflow is:

Secondary explanation
        ↓
Identify legislation / procedure
        ↓
Retrieve primary source
        ↓
Verify proposition
        ↓
Cite primary source

This is both more defensible and easier to audit.

64. The Same Principle Applies to AI-Generated Summaries

An AI-generated explanation can help locate concepts or documents, but it should not be treated as the legal source.

The model's wording is an interpretation.

For regulatory work, the underlying legislation, guidance or procedure-specific document should be checked directly before relying on the conclusion.

This is particularly important for dates, thresholds, procedural rights, legal obligations and changes in legislation.

65. Regulatory Intelligence Requires Version Control

Regulatory intelligence should record when information was retrieved and which version was reviewed.

A useful minimum record includes:

• source title;
• issuing authority;
• document identifier;
• publication/revision date;
• retrieval date;
• applicable effective date;
• relevant provision;
• regulatory conclusion.

Without version control, an otherwise accurate regulatory assessment can become difficult to reproduce months later.

66. What a Good Legal Citation Looks Like

A good citation is specific enough that another professional can find the same source without guessing.

For example, rather than writing:

“According to EMA guidance...”

write a citation that identifies the exact guidance document, version/date and relevant section.

Likewise, rather than writing:

“EU law requires this...”

identify the instrument and provision that establishes the requirement.

Precision improves both credibility and reviewability.

67. What a Poor Citation Looks Like

Common weak forms include:

• “EU regulations say...”;
• “EMA requires...”;
• “According to GVP...”;
• “The Commission decided...”;
• a bare website homepage;
• an undated PDF;
• an old guidance document cited as current;
• a secondary article cited instead of the legislation.

Each may point toward a correct proposition, but none adequately establishes the source without further investigation.

68. A Regulatory Source Checklist

Before finalising an important EU regulatory statement, ask:

1. Have I identified the legal instrument?
2. Have I checked the applicable date?
3. Have I checked whether the text is consolidated?
4. Have I followed relevant cross-references?
5. Have I checked definitions and annexes?
6. Have I distinguished legislation from guidance?
7. Have I checked the procedure-specific document?
8. Have I identified the legally operative outcome?
9. Have I checked national implementation where relevant?
10. Can another person reproduce my conclusion from the citation?

If several answers are “no,” the regulatory assessment is probably incomplete.

69. The Regulatory Professional's Mental Model

A useful mental model is to treat every regulatory statement as a chain of evidence:

Proposition
    ↓
Primary source
    ↓
Legal status
    ↓
Applicable date
    ↓
Relevant provision
    ↓
Interpretation
    ↓
Regulatory conclusion

This prevents a common error in regulatory writing: jumping directly from a general statement on a website to a definitive legal conclusion.

70. Conclusion

Reading EU pharmaceutical legislation well requires more than finding the right article number.

The reader must understand the type of legal instrument, its legal status, its date, its relationship with other instruments and the difference between the legislation itself and the guidance used to apply it.

For practical regulatory work, the safest method is straightforward:

identify the source, establish its legal status, establish the applicable version, follow its cross-references, distinguish law from guidance, and confirm the procedure-specific outcome.

That method makes regulatory conclusions more accurate, reproducible and defensible.

References

1. Treaty on the Functioning of the European Union, including Article 288 and provisions governing delegated and implementing acts.
2. European Parliament and Council. Directive 2001/83/EC, as amended, on the Community code relating to medicinal products for human use.
3. European Parliament and Council. Regulation (EC) No 726/2004, as amended, establishing Union procedures for the authorisation, supervision and pharmacovigilance of medicinal products and establishing a European Medicines Agency.
4. European Commission. EUR-Lex: Access to European Union law and the Official Journal of the European Union.
5. European Commission. EudraLex, Volume 1: Pharmaceutical legislation for medicinal products for human use.
6. European Commission. EudraLex, Volume 2: Notice to Applicants and guidelines for medicinal products for human use.
7. European Commission. Guidance and information concerning delegated and implementing acts under the Treaties.
8. European Medicines Agency. Scientific and procedural guidance for medicinal products for human use.
9. European Medicines Agency. Good Pharmacovigilance Practices (GVP).

Regulatory Note

This article is an educational guide to reading and citing EU pharmaceutical legislation. It is not legal advice.

The article deliberately distinguishes legislation, legally operative decisions, scientific regulatory documents and guidance. The precise legal effect of a document must be determined from the applicable legal framework and the document itself.

EU medicines legislation is amended over time. A current consolidated text should be used for current questions, while historical assessments may require the original Official Journal text, historical amendments and transitional provisions applicable on the relevant date.

Where an individual regulatory procedure is involved, procedure-specific documents and the applicable legally operative decision take precedence over general explanatory material.

Where this article uses general descriptions of EU legal instruments, those descriptions should not be interpreted as creating obligations beyond those contained in applicable EU law.