In pharmacovigilance, the quality and credibility of Individual Case Safety Reports (ICSRs) are critical for accurate signal detection and regulatory decision-making. Among the various attributes captured within an ICSR, the concept of “medically confirmed” status plays a subtle yet important role in determining the robustness of reported adverse reactions.

While often misunderstood or inconsistently applied in operational workflows, regulatory guidance—particularly EMA Good Pharmacovigilance Practices (GVP) Module VI and ICH E2B (R3)—provides clear direction on when and how a case (or specific adverse reaction) is considered medically confirmed.

What Does “Medically Confirmed” Mean?

According to GVP Module VI (VI.A.1.5), an adverse reaction is considered medically confirmed when there is involvement or validation by a healthcare professional (HCP), either directly or indirectly.

This includes scenarios such as:

  • A consumer report supported by medical documentation (e.g., lab results, diagnostic reports) indicating that an identifiable HCP suspects a causal relationship.
  • Cases reported by a medically qualified individual (e.g., physician, pharmacist, nurse).
  • Follow-up confirmation of a consumer-reported adverse reaction by a healthcare professional.

In such cases, even if the initial reporter is a consumer, the presence of medical validation elevates the report to “medically confirmed” status.

Key Nuances from GVP Guidance

  1. Not Limited to Initial Reporting Source

A common misconception is that only HCP-reported cases are medically confirmed. However:

  • Consumer cases can become medically confirmed retrospectively if validated by an HCP.
  • This highlights the importance of follow-up activities in pharmacovigilance.
  1. Granularity in ICH E2B (R3)

Under ICH E2B (R3):

  • Medical confirmation is captured at the adverse reaction level, not just at the case level.
  • This allows selective confirmation, where some events in a case may be medically confirmed while others are not.

GVP explicitly requires that:

  • Updates be reflected at case level (E2B R2) or
  • At reaction/event level (E2B R3) for each medically confirmed adverse reaction.

Why Does “Medically Confirmed” Status Matter?

  1. Data Reliability and Signal Detection

Medically confirmed cases are generally considered more reliable because:

  • They involve clinical judgment
  • They often include objective evidence (labs, diagnostics)

This enhances signal detection accuracy and reduces noise from poorly substantiated reports.

  1. Regulatory and Scientific Weight

Regulators and MAHs may:

  • Assign greater weight to medically confirmed cases during signal evaluation
  • Prioritize them in benefit-risk assessments
  1. Case Processing and Prioritization

Operationally, medically confirmed cases may influence:

  • Medical review prioritization
  • Follow-up strategy
  • Aggregate reporting narratives

Operational Challenges

Despite clear guidance, implementation challenges persist:

Ambiguity in Documentation

  • Not all reports clearly state whether an HCP assessed the reported events.
  • Medical documents may be incomplete or indirect.

System Limitations

  • Safety databases may not consistently capture event-level confirmation (as required by E2B R3).

Over-interpretation Risk

  • Teams may incorrectly assume:
    • “Presence of medical records = medically confirmed”

“Report from HCP = medically confirmed”

Best Practices for MAHs

To ensure compliance and consistency:

  • Establish clear SOP definitions aligned with GVP Module VI.
  • Train teams to distinguish between:
    • Medical information present vs
    • Medical confirmation of causality
  • Ensure proper coding at reaction level in E2B (R3).
  • Strengthen follow-up processes to obtain HCP confirmation when feasible.

Conclusion

The “medically confirmed” status is more than a technical data field—it reflects the clinical credibility of an adverse reaction. Proper interpretation and implementation, as outlined in GVP Module VI and ICH E2B (R3), are essential for maintaining data integrity and supporting meaningful pharmacovigilance activities.

In an era of increasing patient-reported data and digital reporting channels, the ability to accurately identify and document medically confirmed cases will remain a cornerstone of robust safety surveillance.