eduKateSG · Why Science?
Write down what is known, what remains uncertain and exactly how the next evidence will be gathered
Read FDA’s final April 2005 ICH E2E guidance through the safety specification, identified and potential risks, missing information, routine surveillance, targeted studies, signal evaluation and plan updates.
Approval is not the end of safety science. It is the point when use expands to people, settings and durations that development programmes may have represented only partly. A good plan turns those known gaps into specific questions and feasible ways to answer them.
FDA’s final April 2005 ICH E2E guidance focuses on a safety specification and pharmacovigilance plan, especially for the early postmarketing period of a new medicine. The plan is proportionate: routine activities may be enough for some products, while important concerns need targeted work.
Did you know? “Missing information” is not simply missing paperwork. It can mean a clinically important population or use pattern for which safety knowledge is limited, such as pregnancy, organ impairment or long-term exposure.
For students, E2E is applied scientific planning. Every surveillance method should match a question, a population, a timeline and a decision.
Chapter index
Chapters 1–9: April 2005 final guidance, safety specification, identified risks, potential risks and missing information
- 1. E2E prepares for early postmarketing learning
- 2. The April 2005 FDA guidance is final
- 3. The safety specification is a structured summary
- 4. Important identified risks have supporting evidence
- 5. Important potential risks remain plausible
- 6. Missing information names consequential gaps
- 7. Disease epidemiology provides the background
- 8. Routine pharmacovigilance is the baseline
- 9. Targeted follow-up can deepen case information
Chapters 10–17: routine pharmacovigilance, targeted methods, feasibility, milestones, signal evaluation and plan revision
- 10. Registries follow defined populations
- 11. Observational studies can test safety hypotheses
- 12. Clinical studies may answer focused uncertainties
- 13. Method choice depends on the safety question
- 14. Feasibility belongs in the plan
- 15. Milestones make learning accountable
- 16. Signals should update the specification and plan
- 17. A complete E2E receipt joins question to action
CHAPTER 1 OF 17 · Frame the safety picture
1. E2E prepares for early postmarketing learning
The guidance helps sponsors plan pharmacovigilance activities before and around approval, when wider use may expose rare events, longer latency and populations underrepresented in trials. It applies to chemical entities, biotechnology-derived products and vaccines.
The planning discipline in e2e prepares for early postmarketing learning is to connect each uncertainty with a method and decision. The guidance helps sponsors plan pharmacovigilance activities before and around approval, when wider use may expose rare events, longer latency and populations underrepresented in trials. It applies to chemical entities, biotechnology-derived products and vaccines. Keep this boundary visible: The plan complements ongoing clinical safety obligations and regional risk-management requirements.
Try this
Build a safety-specification table for e2e prepares for early postmarketing learning. State the lifecycle stage, planned indications, populations and decisions the plan must support. Add evidence strength and residual uncertainty. Keep this limit: The plan complements ongoing clinical safety obligations and regional risk-management requirements.
A strong science note separates observation from interpretation. State the lifecycle stage, planned indications, populations and decisions the plan must support. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
State the lifecycle stage, planned indications, populations and decisions the plan must support. Keep this boundary visible: The plan complements ongoing clinical safety obligations and regional risk-management requirements.
FDA lists E2E as final guidance dated April 2005 under docket FDA-2004-D-0245, issued by CDER and CBER. It can support a stand-alone regional document or relevant sections incorporated into the Common Technical Document.
For the april 2005 fda guidance is final, naming a risk category is the start of inquiry rather than its conclusion. FDA lists E2E as final guidance dated April 2005 under docket FDA-2004-D-0245, issued by CDER and CBER. It can support a stand-alone regional document or relevant sections incorporated into the Common Technical Document. Preserve this guardrail: Current regional formats may organise the same principles differently.
Try this
Choose a method for one question in the april 2005 fda guidance is final. Create a source receipt with title, date, final status, docket, issuing centres and regional implementation. Explain why two alternatives are weaker. Respect this boundary: Current regional formats may organise the same principles differently.
A strong science note separates observation from interpretation. Create a source receipt with title, date, final status, docket, issuing centres and regional implementation. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Create a source receipt with title, date, final status, docket, issuing centres and regional implementation. Keep this boundary visible: Current regional formats may organise the same principles differently.
CHAPTER 3 OF 17 · Frame the safety picture
3. The safety specification is a structured summary
The specification synthesises important nonclinical and clinical safety findings, limitations of the human safety database, populations not studied sufficiently, identified and potential risks, interactions, epidemiology and possible class effects.
A useful plan for the safety specification is a structured summary evolves as the evidence changes. The specification synthesises important nonclinical and clinical safety findings, limitations of the human safety database, populations not studied sufficiently, identified and potential risks, interactions, epidemiology and possible class effects. Remember: A long list is not useful unless it distinguishes evidence strength and importance.
Try this
Audit the milestones in the safety specification is a structured summary. For each item, record evidence, population, consequence, uncertainty and current action. Separate activity completion from question resolution. Preserve this caution: A long list is not useful unless it distinguishes evidence strength and importance.
A strong science note separates observation from interpretation. For each item, record evidence, population, consequence, uncertainty and current action. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
For each item, record evidence, population, consequence, uncertainty and current action. Keep this boundary visible: A long list is not useful unless it distinguishes evidence strength and importance.
CHAPTER 4 OF 17 · Frame the safety picture
4. Important identified risks have supporting evidence
An identified risk has adequate evidence of association with the product. Planning considers frequency, seriousness, preventability, reversibility, mechanism, risk factors and how well routine data can monitor it.
The planning discipline in important identified risks have supporting evidence is to connect each uncertainty with a method and decision. An identified risk has adequate evidence of association with the product. Planning considers frequency, seriousness, preventability, reversibility, mechanism, risk factors and how well routine data can monitor it. Keep this boundary visible: “Identified” does not imply that every reported case was caused by the product.
Try this
Build a safety-specification table for important identified risks have supporting evidence. Define the evidence establishing the association and the residual question. Add evidence strength and residual uncertainty. Keep this limit: “Identified” does not imply that every reported case was caused by the product.
A strong science note separates observation from interpretation. Define the evidence establishing the association and the residual question. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Define the evidence establishing the association and the residual question. Keep this boundary visible: “Identified” does not imply that every reported case was caused by the product.
A potential risk has a scientific basis for suspicion but the association is not confirmed. Nonclinical findings, pharmacology, class experience or limited clinical patterns can create such concerns.
For important potential risks remain plausible, naming a risk category is the start of inquiry rather than its conclusion. A potential risk has a scientific basis for suspicion but the association is not confirmed. Nonclinical findings, pharmacology, class experience or limited clinical patterns can create such concerns. Preserve this guardrail: Plausibility should not be presented as established incidence or causality.
Try this
Choose a method for one question in important potential risks remain plausible. State the hypothesis, competing explanations and evidence that would strengthen or weaken it. Explain why two alternatives are weaker. Respect this boundary: Plausibility should not be presented as established incidence or causality.
A strong science note separates observation from interpretation. State the hypothesis, competing explanations and evidence that would strengthen or weaken it. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
State the hypothesis, competing explanations and evidence that would strengthen or weaken it. Keep this boundary visible: Plausibility should not be presented as established incidence or causality.
Limited study in pregnancy, paediatrics, older adults, organ impairment, diverse ancestries, comorbidity, interactions or long-term use may be important when those exposures are expected. The category focuses attention on decisions that lack adequate evidence.
A useful plan for missing information names consequential gaps evolves as the evidence changes. Limited study in pregnancy, paediatrics, older adults, organ impairment, diverse ancestries, comorbidity, interactions or long-term use may be important when those exposures are expected. The category focuses attention on decisions that lack adequate evidence. Remember: Not every absent subgroup analysis is important missing information.
Try this
Audit the milestones in missing information names consequential gaps. Link each gap to expected use, plausible consequence and a realistic evidence route. Separate activity completion from question resolution. Preserve this caution: Not every absent subgroup analysis is important missing information.
A strong science note separates observation from interpretation. Link each gap to expected use, plausible consequence and a realistic evidence route. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Link each gap to expected use, plausible consequence and a realistic evidence route. Keep this boundary visible: Not every absent subgroup analysis is important missing information.
Incidence, prevalence, mortality, comorbidities, concomitant treatment and natural history help distinguish product-associated patterns from events expected in the treated population. Background rates also inform study feasibility and signal interpretation.
The planning discipline in disease epidemiology provides the background is to connect each uncertainty with a method and decision. Incidence, prevalence, mortality, comorbidities, concomitant treatment and natural history help distinguish product-associated patterns from events expected in the treated population. Background rates also inform study feasibility and signal interpretation. Keep this boundary visible: Population averages may not represent the product’s actual users or the relevant observation window.
Try this
Build a safety-specification table for disease epidemiology provides the background. Specify population, geography, calendar time, outcome definition and data source for every background rate. Add evidence strength and residual uncertainty. Keep this limit: Population averages may not represent the product’s actual users or the relevant observation window.
A strong science note separates observation from interpretation. Specify population, geography, calendar time, outcome definition and data source for every background rate. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Specify population, geography, calendar time, outcome definition and data source for every background rate. Keep this boundary visible: Population averages may not represent the product’s actual users or the relevant observation window.
Spontaneous case collection, expedited reporting, periodic reports, literature review, signal detection and follow-up form the routine system. For products without special concerns, well-run routine activities may address the safety specification.
For routine pharmacovigilance is the baseline, naming a risk category is the start of inquiry rather than its conclusion. Spontaneous case collection, expedited reporting, periodic reports, literature review, signal detection and follow-up form the routine system. For products without special concerns, well-run routine activities may address the safety specification. Preserve this guardrail: Routine systems have under-reporting, stimulated reporting and limited denominators.
Try this
Choose a method for one question in routine pharmacovigilance is the baseline. Map each safety issue to the routine data that can inform it and the blind spots that remain. Explain why two alternatives are weaker. Respect this boundary: Routine systems have under-reporting, stimulated reporting and limited denominators.
A strong science note separates observation from interpretation. Map each safety issue to the routine data that can inform it and the blind spots that remain. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Map each safety issue to the routine data that can inform it and the blind spots that remain. Keep this boundary visible: Routine systems have under-reporting, stimulated reporting and limited denominators.
CHAPTER 9 OF 17 · Choose the methods
9. Targeted follow-up can deepen case information
Structured questionnaires or focused follow-up can improve information on important events, exposures or special populations. Questions should gather clinically useful detail without overwhelming reporters or delaying essential action.
A useful plan for targeted follow-up can deepen case information evolves as the evidence changes. Structured questionnaires or focused follow-up can improve information on important events, exposures or special populations. Questions should gather clinically useful detail without overwhelming reporters or delaying essential action. Remember: A questionnaire cannot create an unbiased denominator or control group.
Try this
Audit the milestones in targeted follow-up can deepen case information. Design the shortest form that resolves the safety decision and pilot it with case processors. Separate activity completion from question resolution. Preserve this caution: A questionnaire cannot create an unbiased denominator or control group.
A strong science note separates observation from interpretation. Design the shortest form that resolves the safety decision and pilot it with case processors. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Design the shortest form that resolves the safety decision and pilot it with case processors. Keep this boundary visible: A questionnaire cannot create an unbiased denominator or control group.
A product or disease registry can collect longitudinal exposure and outcomes in pregnancy, rare disease or other priority groups. Disease registries may provide treated and untreated comparisons, while product registries focus on exposed people.
The planning discipline in registries follow defined populations is to connect each uncertainty with a method and decision. A product or disease registry can collect longitudinal exposure and outcomes in pregnancy, rare disease or other priority groups. Disease registries may provide treated and untreated comparisons, while product registries focus on exposed people. Keep this boundary visible: Selection, loss to follow-up and incomplete comparison can limit inference.
Try this
Build a safety-specification table for registries follow defined populations. Define entry, comparator, outcome ascertainment, follow-up and retention measures before launch. Add evidence strength and residual uncertainty. Keep this limit: Selection, loss to follow-up and incomplete comparison can limit inference.
A strong science note separates observation from interpretation. Define entry, comparator, outcome ascertainment, follow-up and retention measures before launch. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Define entry, comparator, outcome ascertainment, follow-up and retention measures before launch. Keep this boundary visible: Selection, loss to follow-up and incomplete comparison can limit inference.
CHAPTER 11 OF 17 · Choose the methods
11. Observational studies can test safety hypotheses
Cohort, case-control and database studies estimate associations using real-world data. Design should match the question and address confounding, bias, exposure definition, outcome validation and adequate sample size.
For observational studies can test safety hypotheses, naming a risk category is the start of inquiry rather than its conclusion. Cohort, case-control and database studies estimate associations using real-world data. Design should match the question and address confounding, bias, exposure definition, outcome validation and adequate sample size. Preserve this guardrail: A large database does not automatically make a study valid or clinically relevant.
Try this
Choose a method for one question in observational studies can test safety hypotheses. Write a target question before selecting the data source and analysis. Explain why two alternatives are weaker. Respect this boundary: A large database does not automatically make a study valid or clinically relevant.
A strong science note separates observation from interpretation. Write a target question before selecting the data source and analysis. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Write a target question before selecting the data source and analysis. Keep this boundary visible: A large database does not automatically make a study valid or clinically relevant.
CHAPTER 12 OF 17 · Choose the methods
12. Clinical studies may answer focused uncertainties
Additional trials or extensions can provide controlled exposure, laboratory monitoring or data in particular populations. They may be appropriate when the question cannot be resolved through passive surveillance or observational data alone.
A useful plan for clinical studies may answer focused uncertainties evolves as the evidence changes. Additional trials or extensions can provide controlled exposure, laboratory monitoring or data in particular populations. They may be appropriate when the question cannot be resolved through passive surveillance or observational data alone. Remember: Trials can still be too small or selective for rare or long-latency outcomes.
Try this
Audit the milestones in clinical studies may answer focused uncertainties. Match design, endpoint, duration and population to the unresolved safety question. Separate activity completion from question resolution. Preserve this caution: Trials can still be too small or selective for rare or long-latency outcomes.
A strong science note separates observation from interpretation. Match design, endpoint, duration and population to the unresolved safety question. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Match design, endpoint, duration and population to the unresolved safety question. Keep this boundary visible: Trials can still be too small or selective for rare or long-latency outcomes.
Signal detection, incidence estimation, causal evaluation and risk-factor identification require different data. E2E encourages choosing activities because they address a specified concern rather than because a method is fashionable or readily available.
The planning discipline in method choice depends on the safety question is to connect each uncertainty with a method and decision. Signal detection, incidence estimation, causal evaluation and risk-factor identification require different data. E2E encourages choosing activities because they address a specified concern rather than because a method is fashionable or readily available. Keep this boundary visible: One activity rarely answers every dimension of a complex risk.
Try this
Build a safety-specification table for method choice depends on the safety question. Create a question-method-decision matrix and expose gaps between them. Add evidence strength and residual uncertainty. Keep this limit: One activity rarely answers every dimension of a complex risk.
A strong science note separates observation from interpretation. Create a question-method-decision matrix and expose gaps between them. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Create a question-method-decision matrix and expose gaps between them. Keep this boundary visible: One activity rarely answers every dimension of a complex risk.
A useful plan states data availability, eligible population, expected events, operational responsibilities, timelines and analysis. Unfeasible commitments delay learning and may create false assurance.
For feasibility belongs in the plan, naming a risk category is the start of inquiry rather than its conclusion. A useful plan states data availability, eligible population, expected events, operational responsibilities, timelines and analysis. Unfeasible commitments delay learning and may create false assurance. Preserve this guardrail: Feasibility should not be used to avoid an important safety question without proposing an alternative.
Try this
Choose a method for one question in feasibility belongs in the plan. Estimate recruitment, events, follow-up and data latency before committing milestones. Explain why two alternatives are weaker. Respect this boundary: Feasibility should not be used to avoid an important safety question without proposing an alternative.
A strong science note separates observation from interpretation. Estimate recruitment, events, follow-up and data latency before committing milestones. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Estimate recruitment, events, follow-up and data latency before committing milestones. Keep this boundary visible: Feasibility should not be used to avoid an important safety question without proposing an alternative.
Protocol dates, study starts, interim analyses, reporting points and decision gates allow regulators and teams to see whether the plan is progressing. Milestones can be revised when assumptions change, with reasons documented.
A useful plan for milestones make learning accountable evolves as the evidence changes. Protocol dates, study starts, interim analyses, reporting points and decision gates allow regulators and teams to see whether the plan is progressing. Milestones can be revised when assumptions change, with reasons documented. Remember: A completed activity is not necessarily a resolved safety issue.
Try this
Audit the milestones in milestones make learning accountable. Define both delivery milestones and evidence-based stopping or escalation criteria. Separate activity completion from question resolution. Preserve this caution: A completed activity is not necessarily a resolved safety issue.
A strong science note separates observation from interpretation. Define both delivery milestones and evidence-based stopping or escalation criteria. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Define both delivery milestones and evidence-based stopping or escalation criteria. Keep this boundary visible: A completed activity is not necessarily a resolved safety issue.
CHAPTER 16 OF 17 · Learn and revise
16. Signals should update the specification and plan
New cases, studies, literature or class information can create, refine or refute a concern. The safety specification and pharmacovigilance plan should evolve as evidence changes, with urgent issues acted on outside routine cycles.
The planning discipline in signals should update the specification and plan is to connect each uncertainty with a method and decision. New cases, studies, literature or class information can create, refine or refute a concern. The safety specification and pharmacovigilance plan should evolve as evidence changes, with urgent issues acted on outside routine cycles. Keep this boundary visible: An annual update cadence must not delay action on an immediate threat.
Try this
Build a safety-specification table for signals should update the specification and plan. Set triggers for escalation, protocol change, communication and new investigation. Add evidence strength and residual uncertainty. Keep this limit: An annual update cadence must not delay action on an immediate threat.
A strong science note separates observation from interpretation. Set triggers for escalation, protocol change, communication and new investigation. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Set triggers for escalation, protocol change, communication and new investigation. Keep this boundary visible: An annual update cadence must not delay action on an immediate threat.
CHAPTER 17 OF 17 · Learn and revise
17. A complete E2E receipt joins question to action
The receipt records product and population, identified and potential risks, missing information, epidemiology, routine activities, targeted methods, feasibility, milestones, signal criteria, outputs, decisions and revision history. It makes the plan testable.
For a complete e2e receipt joins question to action, naming a risk category is the start of inquiry rather than its conclusion. The receipt records product and population, identified and potential risks, missing information, epidemiology, routine activities, targeted methods, feasibility, milestones, signal criteria, outputs, decisions and revision history. It makes the plan testable. Preserve this guardrail: A detailed plan has value only when data are reviewed and decisions follow.
Try this
Choose a method for one question in a complete e2e receipt joins question to action. Give the receipt to an independent safety scientist and ask which important uncertainty lacks a credible path. Explain why two alternatives are weaker. Respect this boundary: A detailed plan has value only when data are reviewed and decisions follow.
A strong science note separates observation from interpretation. Give the receipt to an independent safety scientist and ask which important uncertainty lacks a credible path. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Give the receipt to an independent safety scientist and ask which important uncertainty lacks a credible path. Keep this boundary visible: A detailed plan has value only when data are reviewed and decisions follow.
E2E pharmacovigilance planning map
| Question | Evidence to capture | Boundary to retain |
|---|---|---|
| What is known? | Important identified risks and evidence | Association is not every-case causality |
| What is plausible? | Potential risks and hypotheses | Plausibility is not incidence |
| What is missing? | Consequential population or use gaps | Prioritise expected use |
| How will we learn? | Routine and targeted methods, milestones and decisions | Revise when evidence changes |
Science learning becomes useful when a student can show where a claim came from, why it applies and where it stops. Continue with the eduKate Science Learning Hub, compare choices in the Education Hub, and connect these habits to career pathways built from subject capabilities.
E2E turns uncertainty into a responsible research agenda. By naming the most important risks and gaps, choosing methods that can actually answer them and revising the plan as evidence arrives, pharmacovigilance becomes active learning rather than passive paperwork.
Primary sources and verification date
Source status checked 26 October 2026. FDA guidance describes the agency’s current thinking and does not replace applicable statutes, regulations or product-specific communication with FDA.
- FDA: ICH E2E Pharmacovigilance Planning — Final guidance, April 2005; docket FDA-2004-D-0245.
- FDA: Full ICH E2E guidance PDF — Official safety-specification and pharmacovigilance-planning principles.
- FDA: Good Pharmacovigilance Practices and Pharmacoepidemiologic Assessment — FDA guidance on signal identification, assessment and pharmacovigilance plans.
