Why EDC↔PV Reconciliation Exists—and What Regulators Expect to See

Safety data reconciliation is the systematic comparison of safety facts recorded in the clinical database (EDC) against the pharmacovigilance (PV) safety system (e.g., Argus/ARISg). Its purpose is to ensure that every reportable safety event is captured, assessed, and—where required—submitted correctly and on time. Regulators including the U.S. FDA, the EMA, Japan’s PMDA, Australia’s TGA, and the harmonized expectations under the

Designing a Fit-for-Purpose Reconciliation Framework

Define the field crosswalk. Start with a reconciliation specification listing the exact variables to compare, their owners, and matching rules. Typical core elements include:

• Subject identifiers: study ID, subject/participant ID, site ID, country (ensure consistent formatting and de-duplication rules).
• Event keys: event term (coded in MedDRA), onset date/time, outcome, seriousness criterion, severity grade (e.g., CTCAE), hospitalization details, life-threatening flag, IME status.
• Causality & expectedness: investigator vs sponsor causality; RSI/label version reference; expected/unexpected determination.
• Treatment information: suspect product(s), batch/lot (if applicable), dose/regimen, start/stop/interruption dates, concomitant meds (WHO-DD coded).
• Administrative: PV case ID(s), EDC SAE form ID(s), day-0 date, submission date, E2B acknowledgment status, query status.

Matching logic that survives reality. One SAE can generate multiple PV updates (follow-ups), and a single clinical episode can be represented in EDC as several records (e.g., “pneumonia,” “hospitalization,” “fever”). Define linkage rules: use a composite key (subject + site + onset ± 1–2 days + primary PT family) and allow a configurable window for onset differences (time-zone entry, clock skew). Keep a case number crosswalk table to persist matches over time.

Frequency and timing. Establish a steady cadence (weekly/biweekly/monthly) and event-driven checks (e.g., 48 h after any SAE entry, pre-data lock, and pre-IB/RSI update). Hard-stop reconciliations are required at Data Lock Points (DLPs) for DSUR/PBRER cycles to ensure counts and narratives match aggregate reports.

Tools and automation. Build or buy a reconciliation utility that extracts deltas from EDC and PV, normalizes formats (dates, time zones, country codes), and compares fields with rule-based tolerances. The tool should generate exceptions with reason codes (missing in PV; missing in EDC; mismatch onset; mismatch seriousness; mismatch expectedness; duplicate risk) and route them to owners with due dates. Integrate dashboards to show open exceptions by site, age, and severity; export a rapid-pull log for inspectors.

Governance and RACI. Clarify who is Responsible (EDC data manager for clinical fields; PV operations for case facts; medical monitor/safety physician for adjudications), Accountable (study safety lead), Consulted (site, CRO), and Informed (QA). Define escalation rules (e.g., discrepancies > 7 days old → safety lead; > 14 days → governance committee) and document decision rights for changes to case classification (seriousness, expectedness, causality).

Dictionary discipline. Pin MedDRA versions in both systems; time-box upgrades and run impact analyses to quantify remaps and AESI retrieval changes. Ensure WHO-DD versions align for concomitant medications. Display versions and effective dates in reconciliation reports to prevent “silent drift.”

Privacy and traceability. Reconciliation outputs should exclude direct identifiers; keep linkable keys under access control and lawful bases (GDPR/UK-GDPR, HIPAA where applicable). Time-stamp every extraction and decision with local time + UTC offset to simplify multi-region audits by the FDA/EMA/PMDA/TGA and meet ICH documentation expectations.

Running the Engine: Matching, Queries, and Resolving the Hard Problems

Step-by-step execution.

1. Extract deltas since last run from EDC (SAE/AE pages, death log, pregnancy form, AESI modules) and PV (open/closed cases, follow-ups).
2. Normalize formats (dates/times, site codes, country) and map clinical fields to PV case fields using the crosswalk.
3. Auto-match with composite keys; flag unmatched and mismatched pairs with reason codes.
4. Route exceptions to owners with SLAs and pre-formatted site queries; include context (narrative, labs, hospitalization evidence).
5. Adjudicate with the safety physician for seriousness, expectedness (RSI version), and causality differences; document rationale.
6. Close items and update the crosswalk; archive the run log and metrics.

Classic discrepancy patterns—and what to do.

• Missing in PV: EDC SAE entered but no PV case created. Action: confirm minimum criteria; create PV case with day-0 as sponsor awareness date; assess for expedited reporting; perform late clock root-cause analysis if a SUSAR timeline is impacted.
• Missing in EDC: PV case (e.g., spontaneous/literature) not represented in EDC. Action: file as “external AE” per protocol if required; ensure the clinical narrative and exposure are visible to study teams while preserving blinding.
• Onset date mismatch: EDC onset differs from PV. Action: verify source (progress note, discharge summary); apply rules for symptom onset vs diagnosis; correct in both systems; maintain justification in audit trail.
• Seriousness mismatch: EDC non-serious; PV serious based on IME or hospitalization. Action: train site on criteria; update EDC; if PV serious was correct, confirm whether expedited clocks were met and institute CAPA if not.
• Severity vs seriousness confusion: EDC “severe” but not serious; PV marked serious. Action: re-educate on the distinction; correct records; update SOP quick-guides.
• Expectedness mismatch: PV unexpected (SUSAR) vs EDC “expected.” Action: align to the correct RSI version at onset; cite section/wording used; correct EDC annotation and site training.
• Causality mismatch: investigator “not related,” sponsor “possible.” Action: retain both; for expedited logic, treat “possible” as suspected; reflect in reconciliation notes.
• Duplicate risk: multiple EDC records describing a single clinical episode. Action: consolidate per coding convention; maintain child↔parent links; ensure PV retains one case with follow-ups.
• Death records: present in EDC disposition, absent from PV. Action: create PV case with cause of death; link autopsy/toxicology if available; verify whether death is disease-related or AE-related.
• Device malfunctions (combination products): captured as “device issue” in EDC but not routed to PV/device vigilance. Action: create PV case with device problem code; ensure parallel device reporting per regional rules.

Query management that respects timelines. Use templated, topic-specific queries (e.g., DILI/Hy’s Law, anaphylaxis, pregnancy). Set due dates that preserve expedited clocks; escalate non-responses; document all outreach attempts. For global trials, provide translated query text and maintain culturally clear instructions for sites.

Root-cause analysis (RCA) and CAPA. Trend discrepancies by site, CRO, and category. For systemic issues (e.g., onset date errors at multiple sites), conduct RCA: training gaps, confusing form design, or dictionary drift? Implement targeted training, form tweaks (e.g., tooltips explaining “first symptom vs diagnosis”), or system controls (mandatory fields, date validations). Track CAPA effectiveness (post-implementation error rate).

Synchronizing with aggregate reporting. Before DSUR/PBRER DLPs, perform hard-stop reconciliation; lock counts and narratives; record extraction timestamps (local time + UTC offset). Ensure MedDRA versions in tabulations match PV. Any post-DLP case updates should be described in the “events after DLP” section without retro-changing counts.

Blinded safety and arm-agnostic dashboards. Reconciliation reports used by blinded teams should omit treatment labels. Comparative or arm-level checks (e.g., EAIR differences) are run by the independent unblinded statistician/physician per charter; only decisions (continue/stop/enrich) flow back.

Proof of Control: Evidence, KPIs, Pitfalls, and a One-Page Checklist

Inspection-ready evidence bundle. Keep a “rapid-pull” index that surfaces within minutes:

• Reconciliation SOP/WI with scope, frequency, field crosswalk, SLAs, and escalation paths.
• Run logs with extraction timestamps (local time + UTC offset), exception lists, owners, due dates, and closures.
• Case number crosswalk (EDC SAE form IDs ↔ PV case IDs) with history of merges/splits and rationale.
• Dictionary governance: MedDRA and WHO-DD version histories and migration impact reports.
• RSI/label library with effective dates per protocol/country and examples of expectedness decisions citing sections.
• Training records for sites, CRO, and internal teams; targeted refreshers after CAPA.
• Metrics dashboards and trend analyses; CAPA logs with effectiveness checks.
• Alignment proofs to DSUR/PBRER (counts at DLP match PV snapshots; “events after DLP” handling documented).
• Blinding safeguards and DSMB/IDMC interfaces describing who can see unblinded data, with access logs.

Program-level KPIs that matter.

• Coverage: % of in-scope sites reconciled on schedule; % of in-scope event classes included.
• Discrepancy rate: exceptions per 100 subjects (overall and by category: missing in PV/EDC, onset mismatch, seriousness, expectedness, causality).
• Aging: median days open for exceptions; % > 7 days; % > 14 days.
• Expedited impact: number of SUSARs identified via reconciliation; % submitted within clocks after identification.
• Dictionary alignment: % of records where EDC and PV are on the same MedDRA/WHO-DD versions at reconciliation.
• CAPA effectiveness: post-CAPA reduction in a targeted discrepancy category (e.g., onset mismatches down ≥50%).
• Pre-DLP integrity: % studies with zero unexplained count differences at DLP.

Common pitfalls—and durable fixes.

• Unclear day-0 ownership causing late SUSARs → Define “who starts the clock,” automate alerts at minimum criteria, and stamp day-0 in PV with audit trail.
• Field definition drift between EDC and PV (e.g., “hospitalization date” vs “admission date”) → Publish a harmonized data dictionary; add EDC tooltips; validate mapping.
• MedDRA/WHO-DD version drift → Centralize dictionary governance; time-box upgrades; run impact reports; annotate trend breaks.
• Reconciliation too infrequent for expedited risk → Increase cadence to weekly or rolling; prioritize IME/AESI queues.
• Weak blinding hygiene → Keep arm-agnostic reports; segregate unblinded analyses to independent lanes; log access and exports.
• Manual, error-prone processes → Introduce automated comparison tools with reason codes; require structured site queries; track discrepancy aging.
• Inconsistent RSI anchoring → Attach RSI version/section to every expectedness decision; train after IB changes; update ICFs where needed.

One-page checklist (study-ready reconciliation).

• Approved reconciliation SOP with RACI, cadence, and exception workflows; tools validated for intended use.
• Field crosswalk covering IDs, event keys, seriousness, severity, causality, expectedness (with RSI version), treatment, and admin fields.
• Composite matching logic and case number crosswalk implemented; duplicate-prevention rules active.
• Weekly/biweekly cadence (risk-based) plus pre-DLP hard-stop; extraction timestamps recorded (local time + UTC offset).
• Templated, topic-specific site queries (DILI, anaphylaxis, pregnancy, device) with multilingual support and SLAs.
• MedDRA/WHO-DD versions pinned and aligned; migration impact reports archived.
• RSI/label library with effective dates; expectedness decisions cite section/wording used.
• Dashboards for discrepancy rate/aging and expedited impact; CAPA program with effectiveness checks.
• Blinding safeguards in place; DSMB/IDMC interfaces documented; arm-level views restricted to independent personnel.
• Alignment with FDA, EMA, PMDA, TGA, and ICH expectations evident in logs, SOPs, and outputs; public-health alignment with the WHO.

Bottom line. Reconciliation is not an administrative chore; it is a regulatory control that protects participants, ensures accurate expedited reporting, and underpins credible aggregate submissions. With clear specifications, disciplined cadence, robust tools, and documented adjudication, sponsors can demonstrate sustained control to authorities across the FDA, EMA, PMDA, and TGA, consistent with ICH principles and the WHO’s public-health mission.