Safety Systems & Partner Data Exchange
The infrastructure behind pharmacovigilance: databases, dictionaries, interfaces, partner agreements, reconciliation, timeline management, vendor oversight, and the evidence an inspector will ask for. Safety data arrive from partners, vendors and affiliates, and every exchange is a place where a case can be delayed or lost. Reconciliation is the control that finds those losses, and it only works when it is periodic and runs in both directions.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 23 LINKSCase data crossing an organisational boundary is where clocks are lost: the receiving party’s day one is the sending party’s day four, and the reconciliation that finds the gap runs monthly.
06 · QUALITY MATURITY — SAFETY SYSTEMS & PARTNER DATA EXCHANGE, REACTIVE TO ADAPTIVE
Partners send cases by email or spreadsheet. Duplicates and gaps are found when someone notices.
Safety data exchange agreements exist and transfers are structured, but reconciliation is periodic and discrepancies are corrected without cause analysis.
Exchange is in a defined electronic format with acknowledgement, clocks are defined from the earliest partner awareness, and reconciliation gaps are investigated rather than corrected.
Transfer is monitored continuously so a missing acknowledgement is an event, and partner performance is a supplier-quality measure rather than an annual conversation.
The safety system holds one authoritative case record across partners, so reconciliation is a check rather than a repair.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 5
Derived from the 5 standards SPEQ maps to this subject, across 4 regulatory bodies: FDA, EMA, ICH, EC.
RECORDS & OBJECTIVE EVIDENCE
- Safety data exchange agreements defining scope, format, timelines and clocks
- Transfer and acknowledgement records for exchanged cases
- Reconciliation records, with cause analysis for discrepancies
- Validation of the safety database and its interfaces
- Partner performance monitoring against agreed timelines
COMMON INSPECTION FINDINGS
- Day-one clocks measured from receipt by the sponsor rather than from earliest partner awareness
- Reconciliation discrepancies corrected without investigating why they occurred
- Case transfer by unstructured means with no acknowledgement
- Interfaces between safety systems unvalidated, so transfer integrity is assumed
- A partner consistently late with no consequence in the quality relationship
The safety database is a regulated record system
A pharmacovigilance database creates and maintains records that support regulatory submissions and safety decisions, so the electronic-records obligations apply in full: unique user access, audit trails that cannot be disabled, authority checks, and the ability to produce a case as it stood at a point in time. These are the same expectations any GxP system carries, and they are sometimes assessed more loosely here because the system is owned outside quality.
Coding dictionaries add a version dimension that is easy to underestimate. MedDRA is revised twice yearly, and case coding, signal detection and periodic reports must all be able to state which version was used — because a signal detected under one version may not reproduce under another, and an aggregate report spanning an upgrade has to handle the transition explicitly.
E2B is a contract about content, not just a format
ICH E2B(R3) specifies the electronic transmission of individual case safety reports, and treating it as a file format understates it: the standard defines the data elements, their structure and their required content, so a technically valid submission can still be substantively incomplete. Gateway acknowledgement means the message was accepted, not that the case was adequate.
The practical consequence is that transmission monitoring has to look past acknowledgement codes. A rejected case that nobody chased, a case accepted with missing fields the receiving authority will later query, and a partner sending in an older version each produce a downstream problem that the transmission log alone will not reveal.
Partner exchange is where the timeline is actually lost
Expedited reporting clocks start at the earliest awareness anywhere in the organisation or its partners — including licensing partners, distributors, contract call centres and affiliates. A case sitting for a week in a partner’s inbox has consumed most of a fifteen-day clock before the sponsor sees it, and the sponsor remains accountable for the deadline.
Safety data exchange agreements exist to fix this, and their quality varies enormously. The clauses that matter are specific: what constitutes awareness at the partner, the transfer timeline in calendar days, the required content, the acknowledgement mechanism, reconciliation frequency, and what happens on a missed transfer. A template agreement naming neither timelines nor reconciliation has allocated nothing.
SPEQ interpretation — reconciliation must run both ways
Most reconciliation programmes check that cases the partner sent were received. That direction finds transmission failures and is the easier half. The harder and more informative direction is whether everything that should have been sent was sent — comparing the partner’s complaint, medical information and call records against what arrived as cases.
Only the second direction detects under-recognition at the partner, which is the failure that produces systematically missed cases rather than late ones. It requires access the agreement has to grant in advance, which is why the reconciliation clause and the audit-rights clause belong in the same conversation as the transfer timeline.
FREQUENTLY ASKED
Do Part 11 and Annex 11 obligations apply to a safety database?
Yes, in full. It creates and maintains records supporting regulatory submissions and safety decisions, so unique user access, non-disableable audit trails, authority checks and point-in-time case reconstruction all apply. These are sometimes assessed loosely because the system is owned outside quality.
Why does MedDRA version matter?
Because a signal detected under one version may not reproduce under another, and dictionary revisions arrive twice yearly. Case coding, signal detection and aggregate reports must each be able to state which version was used, and a periodic report spanning an upgrade has to handle the transition explicitly rather than silently.
Does a gateway acknowledgement mean the case was adequate?
No — it means the message was accepted. ICH E2B(R3) defines data elements and required content, so a technically valid submission can be substantively incomplete. Monitoring has to look past acknowledgement codes for rejected cases nobody chased and accepted cases with missing fields the authority will later query.
What must a safety data exchange agreement actually specify?
What constitutes awareness at the partner, the transfer timeline in calendar days, required content, the acknowledgement mechanism, reconciliation frequency and the consequence of a missed transfer. Expedited clocks start at earliest awareness anywhere including partners, and the sponsor remains accountable for the deadline regardless of where the delay occurred.