The Critical Role of Data Managers in Reviewing Adverse Events

Introduction: Why Data Managers Are Key to AE Review

In clinical trials, the accurate documentation and review of adverse events (AEs) is a cornerstone of patient safety and regulatory compliance. While investigators are responsible for recording AEs in electronic case report forms (eCRFs), data managers play a pivotal role in reviewing, cleaning, and reconciling this data to ensure its integrity. Regulatory authorities such as the FDA, EMA, and MHRA consistently emphasize the importance of clean, complete, and consistent AE data as part of safety monitoring and inspection readiness.

Data managers act as the bridge between clinical site documentation and sponsor pharmacovigilance systems. Their oversight ensures that AE information is not only captured but also validated, reconciled, and aligned with global reporting requirements. This article explores the role of data managers in AE review, their responsibilities, regulatory expectations, case studies, and best practices for inspection readiness.

Core Responsibilities of Data Managers in AE Review

Data managers’ responsibilities in AE review extend beyond data entry checks. Their role includes:

• Completeness checks: Ensuring mandatory fields such as onset, resolution, severity, causality, and outcome are captured.
• Consistency checks: Validating that AE data aligns with related modules such as concomitant medications, dosing, and labs.
• Query generation: Issuing queries for ambiguous, missing, or inconsistent AE documentation.
• Reconciliation: Comparing AE entries in eCRFs with safety databases to ensure consistency.
• Audit readiness: Maintaining clean AE datasets and documentation trails for regulatory inspections.

For example, if an investigator enters “Recovered” as an outcome but leaves the resolution date blank, data managers are responsible for generating queries to resolve the inconsistency before database lock.

Case Study: Missing Seriousness Criteria in SAE Documentation

In a Phase II cardiovascular trial, data managers identified multiple serious adverse events (SAEs) where the seriousness criteria field had not been completed. Without this information, the events were misclassified as routine AEs, delaying expedited reporting. Data managers raised queries to sites, obtained the missing data, and corrected the classification. This intervention prevented a potential regulatory finding during inspection and reinforced the critical role of data managers in safety data integrity.

Regulatory Expectations for Data Manager Oversight

Regulators view data managers as a critical part of the quality system for clinical data management. Expectations include:

• FDA: Expects AE data in IND safety reports to reconcile with eCRFs and narratives.
• EMA: Requires consistency between eCRF AE entries and EudraVigilance submissions.
• MHRA: Audits data manager oversight processes to ensure completeness and audit trails.
• ICH E6(R2): Highlights the role of data management in ensuring accurate and verifiable trial data.

Inspection findings often cite missing AE causality, delayed resolution updates, or discrepancies between eCRFs and safety databases. Data managers are expected to prevent these issues through proactive oversight. Databases like ClinicalTrials.gov emphasize the importance of accurate AE information in trial transparency, underscoring the need for robust review systems.

Challenges Faced by Data Managers in AE Review

AE review is complex and often hampered by challenges such as:

• Incomplete entries: Missing seriousness, causality, or action taken fields.
• Ambiguity: Vague free-text AE terms that hinder MedDRA coding.
• Delayed updates: Ongoing AEs not updated at follow-up visits.
• Discrepancies: Mismatches between AE eCRF data and safety databases.

These challenges require continuous vigilance by data managers, supported by SOPs, edit checks, and escalation pathways to ensure timely resolution.

Best Practices for Data Managers in AE Review

To ensure high-quality AE datasets, data managers should apply the following best practices:

• Develop data management plans (DMPs) with AE-specific review procedures.
• Use real-time edit checks in eCRFs to prevent incomplete data entry.
• Reconcile AE data with pharmacovigilance systems at regular intervals.
• Perform trend analysis to identify systemic issues across sites.
• Maintain audit trails to demonstrate oversight during inspections.

For example, a sponsor may include in their DMP that all SAEs must be reconciled weekly between eCRFs and the safety database, with discrepancies escalated to the medical monitor.

Role in Database Lock and Trial Close-Out

Before database lock, data managers perform a final reconciliation of AE data. Tasks include:

• Ensuring all AE queries are resolved.
• Confirming consistency between CRFs, narratives, and safety databases.
• Verifying ongoing AEs are updated with final status.

Failure to reconcile AE data before lock can delay trial close-out, regulatory submissions, and even lead to inspection findings. Thus, data managers are integral to ensuring that safety data are complete, consistent, and ready for submission.

Key Takeaways

Data managers are essential to the integrity of AE documentation in clinical trials. Their role ensures:

• Completeness and consistency of AE fields in eCRFs.
• Accurate reconciliation with pharmacovigilance systems.
• Inspection readiness through robust audit trails and oversight.
• Early identification of systemic issues through trend analysis.

By implementing these practices, data managers strengthen regulatory compliance, support accurate safety reporting, and ultimately protect patient safety across global clinical development programs.

A Step-by-Step Guide to Compiling Safety Data for PSUR Submission

The Periodic Safety Update Report (PSUR) is a critical pharmacovigilance document that requires comprehensive and well-organized safety data. Whether you’re compiling information from ongoing clinical trials or post-marketing surveillance, the success of your PSUR submission depends on the quality, completeness, and clarity of your safety data. This guide walks through the entire process of compiling safety data for PSURs in compliance with ICH E2C(R2), EMA, and USFDA expectations.

Why Accurate Safety Data Compilation Matters

Regulatory authorities evaluate PSURs to determine the evolving benefit-risk profile of a medicinal product. Poorly compiled data can lead to regulatory queries, delayed approvals, or even safety-related label changes. Key objectives of safety data compilation for PSUR include:

• Providing a cumulative view of adverse events (AEs)
• Identifying new or changing safety signals
• Quantifying patient exposure with accuracy
• Supporting benefit-risk assessment with validated metrics
• Ensuring compliance with regional and global standards

Step 1: Establish Your Data Lock Point (DLP)

The Data Lock Point is the cutoff date for the inclusion of safety data in the PSUR. All data compiled must be as of the DLP, and no subsequent information should be included unless specifically requested.

Ensure all stakeholders are aligned with the DLP, including data management, pharmacovigilance, medical writing, and regulatory teams.

Step 2: Identify and Extract Data Sources

Compile safety information from the following core sources:

• Clinical trial safety databases: Data on treatment-emergent AEs, SAEs, and discontinuations
• Spontaneous AE reports: Individual case safety reports (ICSRs) from global systems (e.g., EudraVigilance, FAERS)
• Post-Marketing Surveillance: Registries, patient support programs, and call center logs
• Medical literature: Safety signals or case reports found via systematic review
• Stability-related adverse findings from Stability Studies
• Ongoing or completed PASS: Post-authorization safety studies and observational data

Ensure data consistency across all sources to prevent duplication or omissions.

Step 3: Generate Core Safety Tables

Tabulation is a key part of safety data presentation in a PSUR. Below are the typical tables required:

• Summary of cumulative AEs by system organ class (SOC) and preferred term (PT)
• Serious vs. non-serious AEs
• Expected vs. unexpected AEs (based on RSI)
• Fatal outcomes and medically significant events
• AE frequency by population (adult, pediatric, elderly)

Use standard formats compliant with pharma SOP templates to maintain consistency across reports.

Step 4: Create Line Listings of Individual Cases

Line listings should include:

• Case ID and country
• Patient demographics and medical history
• Suspected product and indication
• Adverse event details with dates
• Outcome and causality assessment

Cases should be filtered to remove duplicates and must include both clinical trial and post-marketing cases.

Step 5: Conduct Cumulative Signal Evaluation

Safety signal detection is a key output of PSUR preparation. Use tools and methods such as:

• Disproportionality analysis (e.g., PRR, ROR)
• Time-trend graphs for AE frequency
• Comparison against historical data
• Use of signal management platforms

Document ongoing, new, or closed signals and reference their impact on the benefit-risk profile.

Step 6: Estimate Patient Exposure

Accurately estimating drug exposure is crucial for contextualizing AE data. Consider:

• Sales data converted into defined daily doses (DDDs)
• Number of patients in clinical trials per protocol
• Real-world usage data (if available)

Ensure clear distinction between estimated vs. calculated values and provide justification for assumptions.

Step 7: Review RSI and Label Changes

Any updates to the Company Core Safety Information (CCSI) or the Reference Safety Information (RSI) must be tracked:

• List changes to contraindications, warnings, precautions
• Highlight additions or removals of adverse reactions
• Track consistency across SmPCs in different countries

This section supports transparency and justifies data trends observed in safety tables.

Step 8: Perform Internal QC and Validation

Prior to finalization, all compiled data must undergo:

• Peer review by pharmacovigilance leads
• Cross-verification with clinical trial databases
• Validation checks for missing or inconsistent data
• Audit trail documentation for each source used

Ensure that the compiled safety dataset is audit-ready and meets both internal and GMP compliance expectations.

Best Practices for Efficient Compilation

1. Begin PSUR data compilation 60–90 days before DLP
2. Automate AE data extraction and filtering using validated tools
3. Use centralized data repositories for real-time signal monitoring
4. Standardize formatting and coding using MedDRA terminology
5. Maintain traceability from source document to PSUR summary

Common Pitfalls to Avoid

• Inconsistent AE classification across sources
• Failure to account for duplicate cases
• Incomplete or outdated RSI comparison
• Neglecting non-serious AE trends
• Late alignment between pharmacovigilance and regulatory teams

Conclusion

Safety data compilation is a foundational aspect of preparing a robust, compliant PSUR. By adopting a structured, stepwise approach and leveraging both automation and expert review, pharma professionals can ensure that PSURs reflect the true safety profile of a product. As PSURs evolve from static reports to dynamic tools for safety signal evaluation, accurate data compilation remains at the heart of regulatory success and patient protection.