How EU Pharmaceutical Legislation Is Structured
- How EU Pharmaceutical Legislation Is Structured
- 1. Why the Structure of EU Pharmaceutical Law Matters
- 2. The Starting Point: EU Primary Law
- 3. Secondary Legislation
- 4. Regulations
- 5. Directives
- 6. Regulation and Directive: The Practical Difference
- 7. Directive 2001/83/EC
- 8. Regulation (EC) No 726/2004
- 9. Why the Two Instruments Are Often Read Together
- 10. Decisions
- 11. Delegated Acts
- 12. Implementing Acts
- 13. Implementing Regulation and Implementing Decision
- 14. EudraLex
- 15. EudraLex Volume 1
- 16. EudraLex Volume 2
- 17. Guidelines Are Not Automatically Legislation
- 18. EMA Guidance
- 19. Good Pharmacovigilance Practices
- 20. National Legislation
- 21. EU Law and National Law Are Not Two Separate Systems
- 22. The Legal Basis Comes Before the Guidance
- 23. Why Article Numbers Matter
- 24. Consolidated Texts
- 25. Current Law Versus Historical Law
- 26. The Role of Commission Decisions
- 27. Assessment Reports
- 28. Product Information as a Regulatory Document
- 29. Notices, Questions and Answers and Explanatory Material
- 30. A Source Hierarchy for EU Regulatory Work
- 31. When Guidance and Legislation Appear to Conflict
- 32. Why Legal Status Should Be Recorded in Regulatory Documents
- 33. The Most Important Practical Habit
- 34. A Worked Example: Article 31 Referral
- 35. A Worked Example: A Variation
- 36. A Worked Example: Pharmacovigilance Compliance
- 37. Why the Framework Changes Over Time
- 38. A Practical Regulatory Research Workflow
- 39. What This Means for Regulatory Professionals
- 40. The Core Principle
- 41. The Legislative Basis of the EU Medicines Network
- 42. The Legal Basis for EMA
- 43. Scientific Committees and Legal Authority
- 44. The European Commission's Role
- 45. National Competent Authorities
- 46. The Importance of the Product's Authorisation Route
- 47. National, Mutual-Recognition and Decentralised Procedures
- 48. Reference Member State and Concerned Member States
- 49. Harmonisation Does Not Mean Identical Institutions
- 50. The Legal Basis of a Procedure Should Be Identified Explicitly
- 51. Procedure Rules and Substantive Rules
- 52. Scientific Guidance and Legal Requirements
- 53. When Scientific Standards Evolve
- 54. The Difference Between “Binding” and “Expected”
- 55. Templates and Standard Formats
- 56. Questions and Answers
- 57. Notices to Applicants
- 58. The Importance of Version Control
- 59. Effective Dates Matter
- 60. Transitional Provisions
- 61. Legal Interpretation Requires Context
- 62. Definitions Are Often the Hidden Key
- 63. Annexes Can Have Regulatory Importance
- 64. Cross-References Are Deliberate
- 65. Why Regulatory Citations Should Be Precise
- 66. A Minimum Citation Standard
- 67. Primary Sources and Secondary Sources
- 68. Regulatory Intelligence Is Source Management
- 69. A Practical Document-Review Record
- 70. The Practical Test
- 71. A Final Distinction: Law, Procedure and Science
- 72. Conclusion
- References and Regulatory Note
1. Why the Structure of EU Pharmaceutical Law Matters
EU pharmaceutical regulation is not contained in one document.
The legal framework consists of Union legislation, implementing measures, scientific and procedural guidance, national legislation and procedure-specific regulatory documents. These sources perform different functions and do not all have the same legal status.
A regulatory professional who treats a guidance document as if it were legislation can reach the wrong conclusion. The opposite error is also possible: assuming that because a requirement appears in a guidance document it has no regulatory significance.
The first skill, therefore, is not memorising documents. It is learning to identify what kind of document is being read, who adopted it, what legal authority it has and how it relates to other sources.
2. The Starting Point: EU Primary Law
At the highest level, the European Union operates under the Treaties.
The Treaties establish the competences and institutional framework within which the Union can legislate.
For medicines regulation, the practical regulatory professional will rarely need to begin with Treaty provisions when interpreting an ordinary marketing-authorisation or pharmacovigilance question. Nevertheless, the Treaties provide the constitutional foundation for the Union's legislative powers.
Below that level sits the body of EU secondary legislation that directly structures the medicines system.
3. Secondary Legislation
The principal forms of EU secondary legislation relevant to medicines include:
- regulations;
- directives;
- decisions;
- and, where authorised by the underlying legislation, delegated acts and implementing acts.
These instruments should not be treated as interchangeable.
Their legal effects, adoption procedures and relationship with Member States differ.
Understanding those differences is essential when determining whether a provision is directly applicable, requires national implementation, or has a more specific procedural function.
4. Regulations
An EU regulation is binding in its entirety and is directly applicable in the Member States from the date and under the conditions specified by the instrument.
A regulation therefore does not generally require a Member State to enact a national law simply to transform the regulation itself into national law.
In medicines regulation, Regulation (EC) No 726/2004 is a major example. It establishes Union procedures for the authorisation, supervision and pharmacovigilance of medicinal products and establishes EMA.
A regulation can nevertheless coexist with national legislation and national administrative measures. Direct applicability does not mean that every regulatory activity surrounding a medicine is performed by an EU institution.
5. Directives
An EU directive is binding as to the result to be achieved while leaving the national authorities the choice of form and methods, subject to the requirements of EU law.
The principal EU pharmaceutical directive for human medicines is Directive 2001/83/EC, which establishes the Community code relating to medicinal products for human use.
Member States implement directives through national measures.
This is why a regulatory professional dealing with a nationally authorised medicine may need to consider both the EU directive and the national legislation implementing it.
6. Regulation and Directive: The Practical Difference
The distinction can be summarised simply:
| Instrument | Basic legal characteristic | Practical implication |
|---|---|---|
| Regulation | Binding in its entirety and directly applicable | Operates directly within the EU legal order, subject to its own terms |
| Directive | Binding as to the result | Implemented through Member-State measures |
| Decision | Binding in accordance with its terms | Legal effect depends on the decision and its addressees/context |
This table is a starting point rather than a substitute for reading the actual instrument.
The detailed legal effect of a provision depends on its wording, legal basis and applicable EU law.
7. Directive 2001/83/EC
Directive 2001/83/EC is central to the regulatory framework for human medicines authorised through national systems.
It contains provisions concerning areas including:
- marketing authorisation;
- mutual recognition and decentralised procedures;
- product information;
- manufacturing and wholesale distribution;
- pharmacovigilance;
- regulatory supervision;
- referral procedures.
The Directive has been amended repeatedly.
Consequently, citing “Directive 2001/83/EC” without checking the current consolidated text can be insufficient for a live regulatory question.
8. Regulation (EC) No 726/2004
Regulation (EC) No 726/2004 establishes the Union system for centralised authorisation and supervision of medicinal products within its scope and establishes the European Medicines Agency.
It also contains important provisions concerning pharmacovigilance and the roles of EMA committees.
The Regulation and Directive 2001/83/EC should often be read together.
A product's regulatory route determines which provisions are relevant, but post-authorisation questions can bring provisions from both instruments into consideration.
9. Why the Two Instruments Are Often Read Together
The EU medicines framework is deliberately interconnected.
A nationally authorised medicine may be governed primarily through the Directive and national implementing law, while a centrally authorised medicine is governed directly through the Regulation and the relevant Union procedures.
At the same time, common concepts such as pharmacovigilance, product information, variations and referral mechanisms can involve provisions across the broader framework.
The correct approach is therefore to identify the legal status of the product and the procedure being performed before deciding which legislative instrument controls the question.
10. Decisions
EU decisions are binding in accordance with their terms.
A regulatory decision can therefore have a different legal role from the legislation that created the underlying procedure.
For example, a European Commission decision granting or changing a centralised marketing authorisation is an operative regulatory act concerning a particular product.
It should not be confused with the Regulation that establishes the legal framework under which the decision is made.
This distinction between framework legislation and procedure-specific legal acts is fundamental to regulatory-history analysis.
11. Delegated Acts
EU legislation can empower the European Commission to adopt delegated acts under specified conditions and within defined limits.
Delegated acts supplement or amend certain non-essential elements of the legislative act, subject to the conditions established by the Treaty and the enabling legislation.
In medicines regulation, delegated acts may therefore form part of the legal framework without being equivalent to the basic Regulation or Directive that granted the delegation.
When a delegated act is relevant, the enabling provision and the delegated act itself should both be checked.
12. Implementing Acts
Implementing acts are used where uniform conditions for implementing legally binding Union acts are required, within the framework established by EU law.
They are distinct from delegated acts.
The distinction is not merely terminological. The two mechanisms have different legal bases, purposes and institutional procedures.
A regulatory professional should therefore verify whether an instrument is a delegated act or an implementing act before describing its legal status.
13. Implementing Regulation and Implementing Decision
An implementing measure can itself take the form specified by EU law, including an implementing regulation or implementing decision.
The legal effect depends on the instrument and its provisions.
This illustrates a broader principle: the title of a document should not be interpreted in isolation. The legal basis, adoption mechanism, content and addressees determine its precise role.
14. EudraLex
EudraLex is the European Commission's collection of EU pharmaceutical legislation and related guidance.
It is an essential navigation tool for regulatory professionals, but it should not be treated as though every document within EudraLex has identical legal force.
Different volumes and documents contain legislation, notices, guidelines and other material.
The regulatory professional must therefore distinguish the underlying legal instrument from explanatory or procedural material published alongside it.
15. EudraLex Volume 1
EudraLex Volume 1 contains EU pharmaceutical legislation.
For human medicines, this includes major legislative instruments such as Directive 2001/83/EC and Regulation (EC) No 726/2004, together with amendments and related legislation.
When a question concerns the legal basis for a regulatory requirement, Volume 1 is often an appropriate starting point.
The current consolidated legislation should nevertheless be checked rather than relying on an old standalone copy.
16. EudraLex Volume 2
EudraLex Volume 2 contains notices to applicants and guidelines for medicinal products for human use.
These materials are highly important in practical regulatory work.
They explain how regulatory requirements and procedures are interpreted and applied.
Their legal status, however, is not automatically equivalent to that of the underlying legislation.
This distinction should remain explicit when writing a regulatory assessment or advising on a compliance question.
17. Guidelines Are Not Automatically Legislation
A guideline can be authoritative and highly influential without being an EU legislative act.
Guidelines often describe the scientific, technical or procedural expectations used by regulators.
A company departing from a guideline may need to justify the approach scientifically and explain how the relevant legal requirements are nevertheless met.
It is therefore incorrect to conclude:
“It is only guidance, so it can be ignored.”
It is equally incorrect to say:
“It appears in guidance, therefore it is itself a statutory requirement.”
The correct question is what legal requirement the guidance interprets or operationalises, and what the consequences of divergence are in the particular context.
18. EMA Guidance
EMA publishes extensive scientific and procedural guidance.
Examples include guidance concerning:
- marketing-authorisation applications;
- pharmacovigilance;
- risk-management plans;
- variations;
- referrals;
- post-authorisation studies;
- scientific advice;
- product information.
EMA guidance is an important part of the practical regulatory environment.
Its legal status should nevertheless be distinguished from the EU legislation under which EMA operates.
19. Good Pharmacovigilance Practices
The Good Pharmacovigilance Practices (GVP) framework illustrates the relationship between legislation and guidance particularly well.
EU pharmacovigilance legislation establishes legal obligations. GVP provides detailed guidance on how pharmacovigilance systems and activities should operate within that legal framework.
For a QPPV or pharmacovigilance professional, GVP is therefore operationally indispensable.
But a compliance assessment should still identify the underlying legal provision where the question concerns a binding statutory obligation.
20. National Legislation
EU pharmaceutical law does not eliminate national medicines legislation.
Directives require Member-State implementation, and national authorities retain important regulatory powers and responsibilities.
National legislation can therefore govern matters such as:
- national competent-authority powers;
- national administrative procedures;
- enforcement;
- certain fees and administrative requirements;
- national implementation of Union legislation.
The exact relationship depends on the subject and the applicable EU instrument.
A regulatory analysis concerning a nationally authorised product may therefore require both EU and national sources.
21. EU Law and National Law Are Not Two Separate Systems
It is tempting to describe EU medicines law and national medicines law as two independent rulebooks.
That model is too simple.
EU legislation establishes common legal requirements and procedures, while national law implements directives and provides the national institutional and administrative framework.
The European medicines regulatory network operates through this interaction.
Understanding that relationship is particularly important when determining who has legal authority to act and what form a regulatory action must take.
22. The Legal Basis Comes Before the Guidance
When faced with a regulatory question, begin by identifying the legal basis.
For example:
Regulatory question
↓
Identify the procedure
↓
Identify the legal basis
↓
Read the applicable legislation
↓
Identify implementing measures
↓
Read current guidance
↓
Check procedure-specific documents
This sequence reduces the risk of treating a secondary explanation as though it were the source of the legal obligation.
23. Why Article Numbers Matter
EU medicines legislation is frequently discussed by article number: Article 20, Article 30, Article 31, Article 107i and so on.
An article number has meaning only when the instrument is also identified.
“Article 31” is not a complete legal citation.
The reader needs to know which Directive or Regulation contains Article 31, the version of the instrument and, where relevant, the applicable amendments.
This is particularly important because different instruments can contain articles with the same number.
24. Consolidated Texts
A consolidated text incorporates amendments into a readable version of the underlying legislation.
Consolidated texts are extremely useful for understanding the law as it currently reads.
However, when reconstructing historical regulatory events, the date of the relevant legal provision matters.
The wording applicable in 2015 may not be identical to the wording applicable in 2026.
A historical regulatory analysis should therefore establish which version of the legislation applied at the relevant time.
25. Current Law Versus Historical Law
This distinction is particularly important for long-lived medicines.
A product may have been authorised under one version of EU legislation and subsequently subject to procedures under amended legislation.
A current consolidated text is appropriate for answering a current question, but it may be inappropriate for reconstructing the exact legal basis of a historical decision without checking the historical version.
Regulatory history is therefore partly a problem of temporal legal accuracy.
26. The Role of Commission Decisions
Commission decisions can provide the operative legal outcome of centralised regulatory procedures.
They should be distinguished from:
- CHMP opinions;
- assessment reports;
- EMA summaries;
- press releases;
- guidance documents.
A regulatory history that says “CHMP approved the medicine” may therefore obscure the actual legal sequence.
For a centralised authorisation, the Commission decision is the key legal act establishing the authorisation.
27. Assessment Reports
Assessment reports explain the scientific and regulatory reasoning behind an assessment.
They can be extremely valuable for understanding:
- the evidence considered;
- questions raised by assessors;
- applicant responses;
- the benefit-risk reasoning;
- the basis for regulatory conclusions.
An assessment report is not automatically the same thing as the legally operative regulatory decision.
Its evidentiary and explanatory value can be considerable even though its legal function differs from the final decision.
28. Product Information as a Regulatory Document
The SmPC, labelling and package leaflet are not merely informational publications.
For an authorised medicinal product, they form part of the regulatory product information established through the applicable legal and procedural framework.
Changes to product information therefore need to be understood in relation to the regulatory procedure that authorises those changes.
This is one reason a label change should not be described simply as an editorial update.
29. Notices, Questions and Answers and Explanatory Material
Regulatory agencies publish many documents designed to help applicants understand procedures.
These can include:
- questions and answers;
- procedural notices;
- explanatory pages;
- implementation guidance;
- templates.
Such documents can be extremely useful for practical work.
Their legal status must nevertheless be assessed separately from legislation and legally operative decisions.
30. A Source Hierarchy for EU Regulatory Work
A useful working hierarchy is:
- EU Treaties and applicable primary legal principles;
- current applicable EU legislation;
- delegated and implementing acts where applicable;
- legally operative Commission or national regulatory decisions;
- procedure-specific regulatory documents and adopted scientific outputs;
- current Commission, EMA and CMDh guidance;
- secondary explanations and educational sources.
The hierarchy is not a claim that a lower-level source is unimportant. It is a method for determining which source should control when two explanations appear inconsistent.
31. When Guidance and Legislation Appear to Conflict
The first step is to check whether there is actually a conflict.
Often the apparent conflict arises because the guidance is addressing a narrower procedural question while the legislation states the broader legal requirement.
If a genuine conflict remains, the legally authoritative instrument takes precedence over non-binding guidance.
The practical response is not simply to ignore the guidance. The discrepancy should be documented and, where necessary, clarified with the competent regulatory authority.
32. Why Legal Status Should Be Recorded in Regulatory Documents
A regulatory assessment is stronger when it records not only the source but its status.
For example:
| Source | What it provides | Typical status |
|---|---|---|
| Directive | EU legislative framework requiring national implementation | Binding EU law as to result |
| Regulation | Directly applicable legislative framework | Binding and directly applicable, subject to its terms |
| Commission decision | Procedure-specific legal act | Binding according to its terms |
| CHMP opinion | Scientific regulatory conclusion | Legal effect depends on procedure |
| EMA guidance | Scientific/procedural expectations | Guidance, not automatically legislation |
| GVP | Pharmacovigilance guidance framework | Operationally important guidance |
| Assessment report | Scientific reasoning and assessment record | Explanatory/procedural document |
The precise status of any document should be confirmed from the relevant legal framework.
33. The Most Important Practical Habit
When reading a regulatory document, record four things immediately:
Instrument: What is it?
Authority: Who adopted or issued it?
Legal basis: Under what legislation was it created?
Effect: What does it legally or procedurally do?
This four-part check is often more useful than memorising long lists of regulatory documents.
34. A Worked Example: Article 31 Referral
Suppose a regulatory professional is assessing an Article 31 referral.
The correct approach is not to begin with a general EMA webpage.
First identify the relevant provision of Directive 2001/83/EC and determine whether the referral is a pharmacovigilance or non-pharmacovigilance pathway.
Then review the procedure-specific documents, scientific opinion or recommendation as applicable, and any subsequent legally operative decision.
EMA guidance can then be used to understand the procedural context.
The sources answer different questions:
- legislation explains the legal basis;
- procedure documents explain what happened;
- scientific outputs explain the assessment;
- the final decision explains the legal outcome;
- guidance explains how the system generally operates.
35. A Worked Example: A Variation
For a variation, begin with the legislation governing variations and the applicable variation classification framework.
Then establish the type of variation and the applicable procedural requirements.
The relevant guidance explains submission and assessment expectations.
The procedure-specific regulatory record establishes what was actually approved.
Again, legislation, guidance and the individual regulatory record perform different functions.
36. A Worked Example: Pharmacovigilance Compliance
Suppose a QPPV needs to determine whether a pharmacovigilance activity meets EU requirements.
The analysis should begin with the applicable legislation, followed by the relevant GVP module and any current procedural guidance.
If the issue concerns a specific regulatory request or inspection finding, the procedure-specific correspondence and applicable national requirements may also be necessary.
A sound compliance assessment therefore rarely comes from citing GVP alone.
37. Why the Framework Changes Over Time
EU pharmaceutical law is not static.
Legislation is amended, new implementing measures are adopted, guidance is revised and regulatory procedures evolve.
A document that accurately described a procedure several years ago may no longer describe the current process.
This is why regulatory references should include dates or versions where they materially affect the conclusion.
38. A Practical Regulatory Research Workflow
For a live EU medicines question:
Define the regulatory question
↓
Identify the product status
↓
Identify the procedure
↓
Identify the legal basis
↓
Retrieve current legislation
↓
Check delegated / implementing measures
↓
Review current EMA / Commission / CMDh guidance
↓
Retrieve procedure-specific documents
↓
Confirm the legally operative outcome
↓
Record source, date and legal status
This workflow is deliberately conservative.
It reduces the risk of answering a legal or regulatory question from a secondary summary when the primary source is available.
39. What This Means for Regulatory Professionals
The structure of EU pharmaceutical legislation affects daily work.
It determines how regulatory teams:
- interpret legal obligations;
- prepare submissions;
- assess procedural requirements;
- document regulatory decisions;
- communicate with authorities;
- interpret safety actions;
- maintain product information;
- defend compliance positions.
The ability to distinguish law from guidance is therefore not an academic exercise. It is a core regulatory competence.
40. The Core Principle
EU pharmaceutical regulation is best understood as a layered system:
EU constitutional framework
↓
EU legislation
↓
Delegated / implementing measures
↓
Regulatory decisions and procedure-specific acts
↓
Scientific and procedural guidance
↓
National implementation and administration
The layers interact, but they are not interchangeable.
The central practical rule is:
Identify the legal instrument, its authority, its legal basis and its effect before relying on what it says.
That habit provides the foundation for accurate interpretation of the EU medicines regulatory system.
41. The Legislative Basis of the EU Medicines Network
The European medicines regulatory network is built on a division of responsibilities between the Union and the Member States.
The legal framework does not simply place all medicines regulation in Brussels. Nor does it leave the entire field to national authorities.
Instead, EU legislation establishes common rules, Union procedures and institutional responsibilities while Member-State authorities retain substantial responsibilities for nationally authorised medicines, enforcement and implementation of Union law.
This division explains why the same medicine can appear in several regulatory systems at once: EU legislation, national legislation, EMA procedures and national competent-authority processes may all be relevant, but for different reasons.
42. The Legal Basis for EMA
The European Medicines Agency is a Union agency created by EU legislation.
Its powers and responsibilities therefore derive from the legal framework rather than from an independent legislative mandate of its own.
This distinction matters when interpreting EMA documents. An EMA webpage, scientific committee opinion or procedural document should be read within the legal powers conferred by the applicable legislation.
EMA is a central part of the European regulatory network, but it is not itself the source of the Union's pharmaceutical legislation.
43. Scientific Committees and Legal Authority
EU medicines legislation assigns scientific functions to committees such as the Committee for Medicinal Products for Human Use (CHMP) and the Pharmacovigilance Risk Assessment Committee (PRAC).
Their scientific conclusions can be decisive within the procedures established by legislation.
However, a scientific opinion should not automatically be described as equivalent to a final legally operative decision.
The distinction is particularly important in centralised procedures and referral procedures, where the legislation specifies the relationship between scientific assessment and the subsequent legal act.
A regulatory history should therefore identify the committee output and the later legal outcome separately.
44. The European Commission's Role
The European Commission has important legal responsibilities within the centralised medicines system.
In centralised procedures, the Commission adopts the legally binding decision granting, varying, suspending or otherwise acting upon a Union marketing authorisation in accordance with the applicable legislation.
The Commission's role should therefore be distinguished from EMA's scientific and procedural functions.
A simplified description such as “EMA approved the product” can conceal this institutional distinction.
A more precise description identifies the scientific assessment, the applicable procedure and the legally operative Commission decision.
45. National Competent Authorities
National competent authorities remain essential to the EU medicines system.
They perform functions established by EU and national law, including responsibilities relating to nationally authorised medicines, inspections, enforcement, manufacturing and distribution oversight, pharmacovigilance and participation in Union procedures.
A national competent authority therefore should not be viewed simply as a local branch of EMA.
It is a national public authority operating within the EU legal framework and exercising powers derived from applicable Union and national law.
46. The Importance of the Product's Authorisation Route
The first question in many EU regulatory assessments should be:
How is this product authorised?
The answer can determine which legal provisions, institutions and procedures are relevant.
A centrally authorised medicine operates within the centralised Union framework. A nationally authorised medicine may be subject to a national authorisation and may have entered the market through a mutual-recognition or decentralised procedure.
The regulatory route is therefore not merely historical information. It is part of the legal context of later regulatory activity.
47. National, Mutual-Recognition and Decentralised Procedures
The EU medicines framework provides several routes for medicines that are not authorised through the centralised procedure.
In a national procedure, a Member State assesses and authorises the medicine for its national territory under the applicable legal framework.
In a mutual-recognition procedure (MRP), an existing national authorisation in one Member State is used as the basis for recognition in other Member States.
In a decentralised procedure (DCP), an application is submitted simultaneously in several Member States when the product has not yet received a national marketing authorisation in the participating Member States.
The details of these procedures are addressed in later articles in this series. Here, the important point is that the legal framework differentiates the procedures because they allocate assessment and decision-making responsibilities differently.
48. Reference Member State and Concerned Member States
The MRP and DCP use the concepts of Reference Member State (RMS) and Concerned Member State(s) (CMSs).
The RMS performs defined functions in the procedure, including preparation or maintenance of the relevant assessment documentation.
The CMSs participate in the procedure and recognise or rely upon the assessment within the applicable legal framework.
These terms are procedural roles, not permanent classifications of national authorities.
A Member State can occupy different roles in different procedures.
49. Harmonisation Does Not Mean Identical Institutions
EU medicines legislation seeks a high degree of harmonisation, but the institutional structures of Member States remain national.
Each Member State has its own competent authority, legal system and administrative arrangements.
EU law therefore creates common regulatory obligations and procedures without requiring every national authority to have an identical organisational structure.
This distinction is important when comparing regulatory practice across Member States.
A difference in administrative organisation does not necessarily mean that the underlying EU legal requirement differs.
50. The Legal Basis of a Procedure Should Be Identified Explicitly
A regulatory document should ideally identify the legal basis for the procedure it describes.
For example, an assessment concerning a referral should identify the relevant provision of the applicable legislation rather than merely stating that “EMA initiated a referral”.
Likewise, a variation assessment should identify the applicable variation framework and procedure rather than describing the change only as a “regulatory update”.
This makes the document auditable and allows another professional to reconstruct the reasoning.
51. Procedure Rules and Substantive Rules
It is useful to distinguish between substantive requirements and procedural requirements.
A substantive provision may establish what a marketing authorisation must satisfy, what obligations an authorisation holder has, or what regulatory standard applies.
A procedural provision may establish who acts, how a submission is made, what consultation occurs, what assessment is performed and how a decision is adopted.
The two are closely related but answer different questions.
A regulatory assessment should not cite a procedural provision as though it were the substantive legal standard unless that is actually what the provision does.
52. Scientific Guidance and Legal Requirements
Scientific guidance often translates broad legal requirements into practical expectations.
For example, legislation may require an applicant to demonstrate an appropriate quality, safety and efficacy profile, while scientific guidelines provide detailed expectations concerning study design, analytical methods, clinical evidence or statistical evaluation.
The guideline does not replace the legislation.
It provides the scientific framework through which compliance with the legislative requirement may be demonstrated.
This distinction becomes particularly important where scientific development changes faster than legislation.
53. When Scientific Standards Evolve
Pharmaceutical science develops continuously.
New analytical methods, clinical methodologies, statistical approaches and pharmacovigilance techniques can emerge faster than legislation can be amended.
Guidance provides regulators with a mechanism for communicating current scientific expectations without repeatedly rewriting primary pharmaceutical legislation.
This is one reason why guidance can be highly consequential in regulatory practice despite having a different legal status from legislation.
54. The Difference Between “Binding” and “Expected”
Regulatory language can be subtle.
A legislative provision may impose a binding obligation.
A guideline may describe what regulators normally expect applicants or marketing-authorisation holders to provide.
A departure from guidance may therefore require scientific justification, additional explanation or discussion with the competent authority, even where the guidance itself is not the source of the statutory obligation.
The practical strength of a regulatory expectation and its formal legal status are related but not identical concepts.
55. Templates and Standard Formats
Templates occupy another layer of the regulatory system.
A template may standardise the presentation of information without itself creating the underlying legal requirement.
Examples include templates for regulatory submissions, product information or procedural correspondence.
The correct interpretation is usually that the template describes how information should be presented, while the underlying legislation or guidance establishes what information is required and why.
56. Questions and Answers
Questions-and-answers documents are particularly useful where a regulatory system has recurring practical uncertainties.
They can clarify how an authority interprets or administers an existing procedure.
However, the reader should still identify whether the answer is:
- explaining legislation;
- explaining guidance;
- describing administrative practice;
- or announcing a specific procedural position.
A Q&A should not automatically be cited as though it were a legislative provision.
57. Notices to Applicants
Notices to applicants provide practical information about regulatory procedures and requirements.
They can be particularly useful when preparing submissions because they bring together procedural expectations that may otherwise be distributed across several sources.
They should nevertheless be read alongside the underlying legislation.
If a notice and legislation appear inconsistent, the legal instrument must be examined directly and the apparent discrepancy resolved rather than assuming that the notice changes the law.
58. The Importance of Version Control
Regulatory documents should be version-controlled where changes could affect the conclusion.
A good regulatory reference may therefore contain:
- the document title;
- the issuing authority;
- the version or revision date;
- the relevant legal provision;
- the date accessed where appropriate.
This is particularly important for guidance, because guidance can be revised without changing the underlying legislation.
59. Effective Dates Matter
A regulatory requirement can have different consequences depending on when it became applicable.
When legislation is amended, the amendment may contain provisions concerning its entry into force, transitional arrangements or dates of application.
The publication date of a document is therefore not necessarily the same as the date from which a requirement applies.
A historical or implementation assessment should distinguish:
publication date → entry into force → date of application → transitional provisions.
60. Transitional Provisions
Transitional provisions determine how a new legal framework applies to products, applications or procedures that began under an earlier framework.
They can be critical when legislation changes.
A regulatory professional should therefore avoid assuming that a newly published legislative amendment automatically applies to every existing product or procedure on the same day.
The transitional provisions must be checked.
61. Legal Interpretation Requires Context
Individual sentences in legislation should not normally be interpreted in isolation.
The meaning of a provision can depend on:
- its definitions;
- related provisions;
- the legal basis of the act;
- implementing measures;
- transitional provisions;
- relevant case law;
- and the particular regulatory procedure.
This is why a reliable regulatory assessment often requires reading several provisions together rather than extracting one sentence from a long regulation or directive.
62. Definitions Are Often the Hidden Key
EU medicines legislation contains defined terms that can materially affect interpretation.
Terms such as “medicinal product”, “marketing authorisation”, “pharmacovigilance system” and “risk” may have specific legal or regulatory meanings.
Before interpreting an operative provision, check whether the relevant term is defined in the instrument.
A common regulatory error is to apply ordinary-language meaning where the legislation provides a more specific definition.
63. Annexes Can Have Regulatory Importance
Annexes to EU legislation and regulatory instruments should not be dismissed as supplementary reading.
An annex can contain technical requirements, classifications, procedural details or other material that is part of the applicable legal instrument.
The status of an annex depends on the instrument to which it belongs.
When a legal requirement refers to an annex, the annex should be read as part of the regulatory framework rather than treated as optional explanatory material.
64. Cross-References Are Deliberate
EU pharmaceutical legislation contains extensive cross-references.
A provision may refer the reader to another article, an annex, another Union instrument or a defined procedure.
These cross-references are often essential to understanding the full requirement.
Stopping at the first cited article can therefore produce an incomplete interpretation.
A good regulatory reading follows the chain of cross-references until the operative requirement is clear.
65. Why Regulatory Citations Should Be Precise
Compare these two statements:
“EU law requires a variation.”
and:
“The applicable variation framework requires the proposed change to be handled through the relevant variation procedure.”
The second statement is more useful only if it is supported by the correct legal and procedural sources.
Good regulatory writing should allow a reader to move from the conclusion back to the source without guessing which document was intended.
66. A Minimum Citation Standard
For an important regulatory conclusion, a practical minimum is to record:
- the instrument or guidance title;
- the article, section or relevant provision;
- the issuing authority;
- the applicable version or date where material;
- the regulatory conclusion supported by the source.
For high-consequence legal interpretations, the primary legal text should be cited rather than relying solely on an agency summary.
67. Primary Sources and Secondary Sources
A primary source is the legal or regulatory document that directly establishes, records or expresses the relevant rule or decision.
A secondary source explains, summarises or analyses primary material.
Secondary sources are useful for orientation and teaching.
Primary sources should normally control the final answer where the question concerns an exact legal requirement, regulatory decision or procedural status.
This distinction is especially important in regulatory intelligence, where a summary may omit a qualification contained in the underlying legal text.
68. Regulatory Intelligence Is Source Management
Regulatory intelligence is not simply collecting large numbers of regulatory documents.
Its value comes from identifying:
- what changed;
- what source changed it;
- when the change applies;
- which products or procedures are affected;
- what action is required;
- and what evidence supports the interpretation.
The legal structure of EU pharmaceutical regulation therefore directly affects the quality of regulatory intelligence.
69. A Practical Document-Review Record
For a significant regulatory issue, a simple source record can be useful:
| Field | Example content |
|---|---|
| Question | What regulatory obligation is being assessed? |
| Product status | Centrally or nationally authorised |
| Procedure | Variation, referral, renewal, etc. |
| Legal basis | Applicable EU article/instrument |
| Current legislation | Consolidated or current official text |
| Guidance | Current relevant EMA/Commission guidance |
| Decision | Applicable regulatory decision |
| Effective date | Date the requirement applies |
| Transitional provisions | Applicable or not applicable |
| Conclusion | Action or interpretation supported by the sources |
This record can become part of the regulatory evidence trail.
70. The Practical Test
When confronted with a regulatory statement, ask five questions:
Who says this?
Under what authority?
Where is the legal basis?
When did it become applicable?
What exactly does it require or establish?
If those five questions can be answered, most basic source-status errors disappear.
71. A Final Distinction: Law, Procedure and Science
EU pharmaceutical regulation can be viewed through three interacting dimensions.
Law establishes authority, obligations, rights and legal procedures.
Procedure explains how those legal powers and obligations are operationalised in a regulatory process.
Science provides the evidence and methods used to assess whether the regulatory standards are met.
A high-quality regulatory assessment keeps these dimensions connected without confusing them.
A scientific conclusion is not automatically a legal decision. A procedural document is not automatically legislation. And legislation often cannot be applied intelligently without understanding the scientific evidence to which it refers.
72. Conclusion
The EU pharmaceutical framework is a layered legal and regulatory system rather than a single rulebook.
Regulations, directives, decisions, delegated acts, implementing acts, national legislation, scientific guidance and procedure-specific documents each have distinct functions.
The central practical skill is to identify the status and role of each source before relying upon it.
For regulatory professionals, that discipline provides a reliable foundation for interpreting marketing-authorisation procedures, referrals, variations, pharmacovigilance obligations and post-authorisation decisions.
The most useful question is rarely simply “What does this document say?”
It is:
“What is this document, who issued it, what is its legal basis, when does it apply, and what effect does it have?”
That is the foundation of sound EU regulatory interpretation.
References and Regulatory Note
This article is an educational explanation of the structure of EU pharmaceutical regulation. It should not be used as a substitute for reviewing the current applicable legislation, implementing measures, regulatory decisions or national law for a specific regulatory determination.
Key primary and institutional sources include:
- Treaty on the Functioning of the European Union, including Articles 288–291 concerning Union legal acts and implementing/delegated powers.
- Directive 2001/83/EC on the Community code relating to medicinal products for human use, as amended.
- Regulation (EC) No 726/2004 laying down Union procedures for the authorisation, supervision and pharmacovigilance of medicinal products and establishing a European Medicines Agency, as amended.
- European Commission EudraLex collection of pharmaceutical legislation and guidance.
- European Medicines Agency scientific and procedural guidance, including Good Pharmacovigilance Practices.
For a live regulatory question, the current official text and applicable national implementation should always be verified.