Table of contents
At a glance
What should a PV data exchange agreement specify?
Define products, territories, information types, responsible parties, handover deadlines, data formats and handling of queries or outages. Specify how both parties reconcile receipt and the correct case version. Proof of technical transmission alone does not show complete processing. The marketing authorisation holder remains responsible for its pharmacovigilance system when activities are outsourced.
- The agreed data pathway must also capture incomplete cases and subsequent information.
- Case number, information status, and relevant entry date are interrelated.
- Alignment means clarifying specific outstanding transfers; identical total numbers are insufficient.
Define partner roles prior to data exchange.
The focus lies on pharmacovigilance of authorized human medicinal products in the EU. Distribution cooperation, licensing agreements, and outsourced case management represent different types of arrangements. Describe which party holds the marketing authorization and which entity performs activities on behalf of the marketing authorization holder. Not every business partner acts on behalf of the same marketing authorization holder in all activities.
GVP Module I describes current, sufficiently detailed agreements and appropriate controls for outsourced activities. ICH E2D(R1) addresses exchange of safety data between contractual partners. Neither prescribes a universal template or a single allocation of roles. The agreement must enable each party to meet its legal obligations in practice.
Assign all information types and products completely.
A pure product list is insufficient. Clarify whether the partner receives initial information, amendments, literature references, medical inquiries with a safety relevance, or information from monitored programs. Incomplete reports also require a defined evaluation pathway, including targeted follow-up when necessary.
Additionally, agree on the transfer of prior case numbers and previously reported notifications. A new appendix to an existing case must not be inadvertently processed as an independent initial case. The agreement should specify who queries the original reporter regarding missing information and how the results are communicated back. Professional assessment shall not be substituted by a file name or a transport status.
A handover matrix for agreement establishment
The following internal support document associates each transition with a verifiable outcome. Enter specific point of contacts, representations, and timeframes for your partnership. The table does not establish a uniform legal partnership deadline.
| Transition | To agree | Expected completion |
|---|---|---|
| First information | Product, region, recipient, required information scope and entry time | Receipt and responsibility transfer clearly identifiable |
| Addendum | Previous case number, updated information status, original entry | Assigned to the appropriate case; time-dependent effect evaluated |
| Inquiry | Responsible Reporting Contact, Inquiry, Recall and Representation | Response or documented open status |
| Faulty transfer | Error notice, corrective responsible party, additional supply | Correction available, accepted, and reconciled |
| Failure or substitution | Contact path, open procedures, alternate methods | Further processing and re-comparison are governed. |
Separate time stamp from receipt confirmation
If a third party acting on behalf of the marketing authorization holder provides the required minimum information, the reporting deadline begins at that point. A subsequent import into the central safety database does not extend this timing. Agree on the time information to be provided and how uncertainties regarding receipt, time zone, or fulfillment of minimum criteria will be resolved.
Distinguish three types of feedback: receipt confirmed, content technically readable, and content professionally assigned. A partner portal may acknowledge the first step even in the absence of an attachment. An email receipt may be fully complete, while assignment to a case number may still be pending. The required type of feedback depends on the agreed procedure; it must enable the next responsible action.
Incident: Follow-up is missing despite identical number of cases
Example: Partner Nord manages three known cases for a marketing authorization holder. In the shared case list, three case numbers are listed on both sides. However, at the scheduled reconciliation meeting, the comparison of current information reveals that a new hospital discharge report should be transmitted for case N-02. The recipient list still contains the previous version.
The number of cases is on both sides 3; completely matching information stands exist initially only for 2 out of 3 cases. A new copy of N-01 increases the number of files received, but does not remove the missing supplement to N-02. Therefore, the comparison takes place according to case and agreed information stand, not only by file number.
The responsible parties shall clarify the original receipt, the missing onward transmission, and any potential time-bar effect. Upon receipt, the follow-up action shall be assessed technically and assigned to the appropriate case. The process shall only be considered closed when the required processing and confirmation response are documented; mere retransmission is insufficient.
| Case | Partner's version | Recipient's version | Required action |
|---|---|---|---|
| N-01 | V2 completely | V2 completely plus renewed copy | Copy assignment; do not create a new case |
| N-02 | V3 with discharge report | V2 without addendum | Transfer missing report; clarify receipt and expiry effect |
| N-03 | V1 completely | V1 completely | Document concordance |
Plan changes, representation, and contract termination
A new service provider, a modified portal, or a changed product responsibility may disrupt existing handovers. Prior to any transition, verify which open first-time reports, inquiries, and corrections are affected. The handover should have a clear and identifiable status to prevent any party from erroneously assuming a process has been assigned to the other.
Manage availability and representation even during absences. For the termination of collaboration, open tasks, accessible documentation, and additional follow-up actions related to prior cases must be resolved. This does not imply a blanket requirement to fully copy all data holdings from each party. Key considerations include the respective responsibilities, the necessary scope of information, and appropriate protective measures.
Practical inspections for small teams
Start with transfers involving high urgency or information impact. A concise list of clear, defined actions can be more effective than an extensive dashboard lacking verifiable closure status. The frequency and depth of reconciliation must align with data volume, task distribution, and observed error risk.
Use this checklist when setting up or changing the process. Assess the actual case and the contractual relationship separately.
- Is product, region, and partner role clearly defined?
- Are initial information, amendments, and open queries distinguished?
- Are entry time and case identifiers included?
- Does the feedback indicate missing or unreadable contents?
- Are individual case instances being compared instead of just total numbers?
- Are representation, failure, and partner changes addressed?
- Are open items with responsible party and outcome traceable?
When is the agreement operationally feasible?
A portable agreement also addresses the challenging scenario: the partner has received information but cannot fully transfer it; the deadline reference is unclear; a prior action must be corrected. If responsibility, temporary preservation, and clarification pathway can be derived from this, the agreement is significantly more useful for operations than a simple description of the normal case.
To implement the process, you require specific technical PV responsibility, point of contact for both parties, and IT involvement for electronic data transfers. The effort increases with product and geographic diversity, varied data formats, and unclear historical data mappings. Supplier documentation and existing interface proof-of-concept may assist, but must fully cover the actually agreed-upon data transfers.
Project experience and collaboration
Preserve the date of first awareness and the case identity at handover
With Pharmacovigilance and system owners, we trace a prepared case through the agreed partner exchange. We examine the content, attachments, first relevant date of awareness, case identifiers and acknowledgements. A small regular handover may suit a different process from a large automated feed. We plan reconciliation and escalation so missing or conflicting deliveries are detected in time. Import into the database must preserve visibility of the original receipt relevant to the reporting deadline.
Frequently asked questions about Pharmacovigilance data exchange with partners
Is a Safety Data Exchange Agreement the same for each partnership?
No. Roles, products, territories, and assumed responsibilities differ. A case handling service provider requires different operational definitions compared to a licensed partner with its own reporting responsibility. Assess the specific relationship and describe the associated information flows. A reusable template is only useful if its assumptions align with the partnership context.
Is an email address considered an approved transfer pathway?
An address alone does not indicate responsibility, representation, or processing status. Additionally specify who monitors incoming submissions, what information is expected, how missing attachments are detected, and when an unclear handover escalates. Email may constitute part of an appropriate procedure; its mere availability does not establish the procedure's suitability.
Does Day Zero begin only upon import by the marketing authorization holder?
No. If a service provider or other contractor acting on behalf of the marketing authorization holder obtains the required minimum information, the reporting deadline begins on that day (GVP VI.B.7; ICH E2D(R1) 5.2). Any subsequent import into the safety database is a processing step and does not constitute a new deadline start. Clarify in the agreement in particular for whom the contractor acts and how this initial knowledge date is transferred.
Must incomplete reports also be exchanged?
For such information, an appropriate pathway for evaluation and traceability must exist. An agreement that solely accepts cases that have already been fully evaluated may create gaps. Therefore, describe which information is shared, who requests missing data, and how new insights are fed back. Not every incomplete information constitutes a reportable ICSR.
Are equivalent case numbers sufficient for a proper comparison?
No. Identical numbers can mask different cases or different information states. Compare appropriate identifiers and the expected status. In the example of this article, three cases are present on both sides, but a relevant update is missing. Whether further content needs to be reconciled depends on the assigned tasks and the risk of error.
Sources: [2]
Who reviews a rejected or illegible file?
This must arise from the operational agreement. Identify who detects the error, notifies the sender, provides the correction, and verifies the successful follow-up receipt. A technically rejected file does not fulfill the underlying technical responsibility. During investigation, the receipt and potential deadline implications must still be assessed.
Must each partner use the same safety software?
No. Different systems are possible, but they must use clear formats, unambiguous identifiers, and controlled mapping. Review the entire agreed data pathway including attachments and feedback mechanisms. The existence of an existing standard interface does not confirm that all required information is received correctly.
How frequently should partners reconcile their cases?
A fixed frequency is not specified by GVP Module VI and ICH E2D(R1). However, E2D(R1) 6.5 anticipates such a short exchange period that the marketing authorisation holder can meet its reporting deadlines. Establish criteria for alignment based on reporting deadlines, data volume, transfer method, and previous issues. Open or conflicting transfers must be identified in a timely manner prior to deadline expiry.
Does the service provider assume full responsibility?
Delegation does not remove the marketing authorisation holder's responsibility for its pharmacovigilance system. Describe the work actually delegated and suitable controls in the agreement. The partner's own responsibilities follow its particular role. The title “service provider” alone does not determine them.
Sources: [1]
What should be assessed prior to a partner change?
Resolve open cases, inquiries, information status, access rights, and future follow-ups for prior cases. Define a clear handover baseline and assign responsibilities on both sides. Technical data transfer is only sufficient when the information and processing contexts required for the accepted tasks are actually usable.
Sources and review date
Source date: 7 October 2026. GVP Module I and VI will be aligned together with ICH E2D(R1) and the EU Implementation Strategy 2026. Contractual processes and tables are to be treated as separate reference documents; specific regional reporting obligations remain to be determined individually.
- EMA: GVP Module I – Pharmacovigilance Systems and Quality Management SystemsEMA/541760/2011; applicable from 02.07.2012; I.C.1.5, p. 18–19; I.B.10–11, p. 9–12
- EMA: GVP Module VI – Collection, Processing, and Reporting of Suspected CasesRev. 2, dated 28.07.2017; applicable from 22.11.2017; VI.B.2–B.5 and B.7, pages 14–18 and 21–22
- EMA/ICH: E2D(R1) – Post-approval safety dataStep 5, 18.09.2025; EU Efficacy 18.03.2026; §§ 5.2, 6.4–6.6, pp. 18–22
- EMA: EU Implementation Strategy for ICH E2D(R1)EMA/11141/2026, 26.02.2026; PRAC 20.02.2026; §§ 2–4, S. 2–5
Sources checked: .
Concreteise PV-partner transfers together
We support you in translating agreements into traceable data flows, responsibilities, and review cases. The focus lies on your actual transfers and outstanding proof requirements.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

