Skip to content

What Do Inspectors Check for Safety Data Exchange Agreement Requirements?

Pharmacovigilance systems must operate under clear Safety Data Exchange Agreements (SDEAs) when safety responsibilities are shared with partners or service providers. Regulators expect defined roles, timelines, data exchange rules, reconciliation, escalation, and oversight.

For: Founders, CEOs & MDs·PV Leads·QA/Compliance·Scientists tasked with documentation

Alignment: Global pharmacovigilance principles (ICH-aligned) and inspection practices

Most useful when: Preparing for inspection, setting up a process, or closing a documentation gap

Key points

  • Pharmacovigilance responsibilities shared between companies or service providers must be governed by a defined Safety Data Exchange Agreement.
  • SDEAs must clearly allocate roles, responsibilities, and timelines for all relevant pharmacovigilance activities.
  • Agreements should cover ICSR exchange, aggregate reporting, signal management, literature monitoring, regulatory communication, and escalation pathways.
  • Data exchange processes must support timely, complete, and traceable transfer of safety information.
  • Oversight, reconciliation, audit rights, and record retention requirements must be documented.
  • Inspection-ready evidence should demonstrate that shared PV responsibilities are controlled through an active and current agreement.

What inspectors expect

Each point below should be supported by controlled documents and traceable records.

  • Shared pharmacovigilance activities must be governed by a defined written agreement.
  • Responsibilities and timelines must be allocated clearly and without ambiguity.
  • Case exchange and follow-up processes must support timely reporting compliance.
  • Reconciliation, escalation, and oversight mechanisms must be documented.
  • The MAH must retain oversight of outsourced or shared pharmacovigilance obligations.

Summary

Inspectors assess whether shared pharmacovigilance responsibilities are governed by a clear and current Safety Data Exchange Agreement. They typically review responsibility allocation, exchange timelines, reconciliation processes, escalation routes, audit provisions, and evidence that the agreement reflects actual operational practice.

Common questions

These are the questions this page is designed to answer directly.

  • What is a Safety Data Exchange Agreement in pharmacovigilance?
  • What do inspectors check for SDEAs?
  • When is an SDEA required?
  • What should a pharmacovigilance SDEA include?
  • How are safety responsibilities defined between partners?
  • What are SDEA requirements for vendors and license partners?
  • How do inspectors assess safety data exchange agreements?
  • What is the purpose of an SDEA?
  • What pharmacovigilance obligations should be covered in an SDEA?
  • How do companies manage shared PV responsibilities?

Evidence objects inspectors expect

Safety Data Exchange Agreement

  • Signed agreement between MAH and partner or service provider
  • Defined scope, product, and territory coverage
  • Allocation of pharmacovigilance roles and responsibilities
  • Defined timelines for case exchange and follow-up
  • Version control and effective date

Responsibility Matrix

  • Allocation of ICSR intake, processing, submission, and follow-up
  • Ownership of aggregate reporting activities
  • Responsibility for literature screening and signal management
  • Defined roles for regulatory communication and label updates

ICSR Exchange and Reporting Process

  • Agreed timelines for forwarding valid cases and follow-up information
  • Defined use of day zero across parties
  • Secure transfer mechanisms for case data
  • Acknowledgement and duplicate prevention controls

Reconciliation and Oversight Records

  • Periodic case reconciliation outputs
  • Documentation of discrepancy investigation and resolution
  • Joint safety committee or governance meeting records
  • Escalation logs for critical safety issues

Audit, Inspection, and Retention Provisions

  • Audit rights covering partner or vendor PV activities
  • Inspection notification obligations
  • Document retention requirements
  • Evidence of current contact lists and 24/7 safety coverage

Regulatory Basis (Primary Sources)

  • GVP Module I – MAH responsibility for pharmacovigilance systems and quality oversight
  • GVP Module VI – requirements for ICSR collection, exchange, and reporting responsibilities
  • ICH E2D – post-approval safety data management and reporting expectations
  • MHRA GPvP guidance – expectations for pharmacovigilance systems under shared responsibilities
  • FDA postmarketing safety reporting guidance – requirements for compliant safety reporting and partner coordination

Typical Inspection Questions (What Inspectors Ask)

  • Show me your current SDEA for this product or partner.
  • How are responsibilities allocated between the parties?
  • What timeline applies for forwarding valid ICSRs?
  • How do you reconcile cases between systems?
  • How do you ensure the agreement reflects actual practice?

Failure patterns

No SDEA is in place despite shared pharmacovigilance responsibilities.

Roles and responsibilities are vague, overlapping, or inconsistent with operational practice.

Case exchange timelines are missing or not aligned with reporting obligations.

Reconciliation is not performed or discrepancies are not resolved effectively.

The MAH cannot demonstrate effective oversight of the partner or vendor.

What good looks like

  • A current, signed SDEA covering all relevant pharmacovigilance activities.
  • Clear allocation of responsibilities for case handling, reporting, and oversight.
  • Defined timelines for exchanging valid cases and follow-up information.
  • Routine reconciliation and documented discrepancy resolution.
  • Demonstrable MAH oversight of shared or outsourced PV activities.

Operationalisation

  • Establish an SDEA before shared pharmacovigilance activities begin.
  • Define product scope, territories, contact points, and role allocation clearly.
  • Document ICSR exchange timelines, day zero rules, and submission responsibilities.
  • Implement reconciliation routines and escalation pathways.
  • Review and update the agreement when responsibilities, territories, or regulations change.
  • Maintain active oversight of partner or vendor performance against the agreement.

Need regulatory documentation today?

Save time and reduce inspection risk with structured, pre-built process-ready documentation.
Created by industry professionals, adaptable to your organisation.

Related pre-built documentation inside the app

FAQ

What is a Safety Data Exchange Agreement in pharmacovigilance?

A Safety Data Exchange Agreement is a written agreement that defines how pharmacovigilance responsibilities and safety information are managed between two parties, such as a marketing authorisation holder and a partner or service provider.

When is an SDEA required?

An SDEA is required whenever pharmacovigilance responsibilities or safety data handling activities are shared, delegated, or exchanged between separate organisations.

What should a pharmacovigilance SDEA include?

An SDEA should include scope, product and territory coverage, roles and responsibilities, ICSR exchange timelines, aggregate reporting responsibilities, signal management, reconciliation, escalation, audit rights, and document retention requirements.

What is the difference between a Safety Data Exchange Agreement and a Pharmacovigilance Agreement?

A Safety Data Exchange Agreement focuses on how safety data is exchanged between parties, including timelines and responsibilities, while a Pharmacovigilance Agreement defines the broader pharmacovigilance system framework, including oversight, processes, and compliance responsibilities.

Does the MAH remain responsible if PV activities are outsourced?

Yes. The MAH retains ultimate responsibility for pharmacovigilance compliance even where activities are outsourced or shared with a partner.

Do inspectors review Safety Data Exchange Agreements?

Yes. Inspectors frequently review SDEAs to confirm that shared pharmacovigilance responsibilities are controlled, current, and aligned with actual operational practice.

What are common SDEA inspection failures?

Common failures include missing agreements, unclear role allocation, missing timelines, poor reconciliation controls, and weak MAH oversight of the partner or vendor.

Sources

Primary guidance used to inform this map. This page is a structured interpretation layer; always validate against the original source documents.

European Medicines Agency (EMA)

  • Guideline on good pharmacovigilance practices (GVP) – Module I
    View source
  • Guideline on good pharmacovigilance practices (GVP) – Module VI
    View source

International Council for Harmonisation (ICH)

  • Post-Approval Safety Data Management: Definitions and Standards for Expedited Reporting (E2D)
    View source

U.S. Food and Drug Administration (FDA)

  • Postmarketing Safety Reporting for Human Drug and Biological Products
    View source

UK MHRA