Recording Onset and Resolution Times of Adverse Events in eCRFs

Introduction: Importance of Onset and Resolution Recording

The accurate recording of time of onset and time of resolution of adverse events (AEs) is critical for safety data integrity in clinical trials. Regulators such as the FDA, EMA, and MHRA require sponsors to capture AE chronology in electronic case report forms (eCRFs) to determine relationships to study drugs, assess seriousness, and meet expedited reporting timelines. Recording only the event description without timing data risks obscuring safety patterns and undermining causality assessments.

Onset and resolution data not only inform causality determination but also contribute to trial-level analyses such as median AE duration, correlation with dosing cycles, and impact on treatment discontinuations. This tutorial explores how onset and resolution recording should be structured in eCRFs, regulatory expectations, real-world challenges, and best practices for ensuring accurate, complete, and inspection-ready AE documentation.

Core Fields for Onset and Resolution in eCRFs

Every AE captured in an eCRF should include both onset and resolution fields. The recommended structure is shown below:

This structured approach ensures that every AE has a documented timeline. Where exact times are unavailable, systems should allow partial dates (e.g., YYYY-MM-DD) with clear documentation. Regulators emphasize that “ongoing” AEs must be updated at subsequent visits until resolution or end of study.

Case Study: Oncology Infusion Reaction

In a Phase II oncology trial, a patient developed chills and shortness of breath during drug infusion at 10:45 AM. The AE was recorded as “Infusion reaction,” but no onset time was captured. During an EMA inspection, auditors identified the missing onset time as a significant finding, as it was critical for differentiating between infusion-related reactions and disease progression. After system updates, onset and resolution fields were made mandatory, improving accuracy and regulatory compliance.

Regulatory Expectations on Onset and Resolution

Authorities have clear expectations regarding AE chronology:

• FDA: Requires onset and resolution times for all SAEs to support causality and expedited reporting (IND safety reports).
• EMA: Expects onset and resolution in EudraVigilance submissions, with “ongoing” clearly marked if unresolved.
• ICH E2A: Defines onset and resolution as essential data elements in clinical safety data management.
• MHRA: Auditors frequently cite incomplete onset/resolution recording as a critical finding.

Global registries such as the Clinical Trials Registry – India also highlight the importance of standardized AE recording, reinforcing its role in transparency and pharmacovigilance.

Challenges in Capturing Onset and Resolution

Common challenges encountered in trials include:

• Incomplete data: Investigators may capture only start dates without times.
• Ongoing events: Failure to update unresolved AEs at follow-up visits.
• Recall bias: Patients may inaccurately recall the exact timing of symptoms.
• System limitations: eCRFs that do not allow partial dates or mark ongoing events.

Mitigating these challenges requires system flexibility, site training, and continuous monitoring by data managers. For instance, allowing partial date entry with justification reduces delays, while reminders for ongoing AE updates ensure completeness.

Best Practices for Designing Onset/Resolution Fields

To ensure accuracy, sponsors should incorporate best practices such as:

• Make onset and resolution fields mandatory for all AEs.
• Allow partial dates but require justification when time is unknown.
• Use edit checks to prevent illogical entries (e.g., resolution before onset).
• Flag ongoing AEs for follow-up at subsequent visits.
• Train investigators on recording exact times for procedure-related AEs.

For example, in a vaccine trial, system validations prevented entry of “Ongoing” without outcome documentation, reducing data gaps and inspection findings.

Role of Data Managers in AE Timeline Oversight

Data managers ensure consistency and completeness of onset and resolution data by:

• Reviewing missing or illogical AE timelines during data cleaning.
• Generating queries for unresolved AEs without updates.
• Reconciling eCRF data with safety databases to ensure accuracy.

In one global cardiovascular trial, data managers identified inconsistencies where resolution dates were after patient death dates. Queries led to corrections, ensuring inspection readiness and database integrity.

Key Takeaways

Onset and resolution recording is a cornerstone of accurate AE documentation. Sponsors and CROs must:

• Include structured onset and resolution fields in every eCRF.
• Support partial dates with justification and updates for ongoing events.
• Apply validation rules and edit checks to prevent errors.
• Train investigators on importance of precise timing for causality assessment.
• Ensure reconciliation across CRFs, narratives, and safety databases.

By implementing these measures, clinical teams strengthen regulatory compliance, enhance pharmacovigilance quality, and improve patient safety outcomes across trials.

Linking Adverse Events to Study Drug and Procedures in eCRFs

Introduction: Why Linking AEs to Study Drug and Procedures Matters

One of the most critical aspects of adverse event (AE) documentation is establishing a clear and traceable link between the AE, the investigational product (IP), and any procedures conducted as part of the study. Regulators across the globe—including the FDA, EMA, MHRA, and CDSCO—require sponsors to demonstrate causality assessments in every clinical trial. This ensures that AEs are not only documented but also evaluated in the context of the study drug and trial interventions.

In electronic case report forms (eCRFs), specific fields are designed to capture whether an AE is related to the IP, a comparator, or a procedure (e.g., biopsy, surgery, infusion). These fields serve as the foundation for regulatory submissions such as DSURs, PSURs, IND safety reports, and expedited SAE reports. Without proper linkage, safety signals may be overlooked, delayed, or misrepresented in regulatory filings. This tutorial provides a detailed guide on how to design eCRF modules that enable accurate linkage of AEs to study drugs and procedures, supported by real-world examples, case studies, and best practices.

Core Concepts of AE-Drug/Procedure Linkage

AE linkage to study drug and procedures involves three interconnected steps:

1. Attribution: Determining whether the AE is related to the study drug, comparator, placebo, or a trial-specific procedure.
2. Documentation: Capturing the causality assessment in eCRF fields with mandatory data entry and audit trails.
3. Reporting: Reflecting causality in regulatory submissions and safety analyses for pharmacovigilance purposes.

Each of these steps must be supported by structured eCRF design, investigator training, and data management oversight. For instance, if an AE occurs immediately after a biopsy, the AE must be linked to the procedure rather than the investigational drug. Conversely, if the AE occurs after drug administration and matches known safety signals, it must be attributed to the study drug.

Fields in eCRFs for Linking AEs to Study Drugs and Procedures

To enable accurate linkage, AE modules should include fields such as:

These fields provide regulators with clear evidence of how investigators determined causality and what actions were taken in response.

Case Example: Infusion Reaction vs. Disease Progression

In a Phase II oncology trial, a patient experienced shortness of breath and fever following monoclonal antibody infusion. Investigators faced the challenge of determining whether this was:

• An infusion-related reaction linked to the investigational product.
• A disease-related symptom from underlying tumor progression.
• An infection-related event due to immunosuppression.

Through structured eCRF fields, the investigator documented causality as “Probably related to study drug.” The action taken was “Drug interrupted,” and the outcome was “Recovered.” This attribution was later included in the sponsor’s DSUR and expedited reports, ensuring regulatory compliance.

Regulatory Expectations for AE Linkage

Regulatory agencies emphasize that causality assessment is the responsibility of the investigator, supported by sponsor oversight. Key expectations include:

• FDA: Requires causality assessment fields in AE documentation for IND submissions.
• EMA: Mandates causality attribution in EudraVigilance safety reports and EU-CTR data submissions.
• MHRA: Expects traceable evidence of how investigators determined AE attribution.
• CDSCO: Requires causality assessment for all SAE reports with action taken on the drug.

Agencies frequently cite inspection findings where causality was inconsistently documented or not reconciled across CRFs, narratives, and safety databases. Public registries such as the NIHR Be Part of Research reinforce the importance of attributing AEs accurately for transparency and patient trust.

Challenges in Linking AEs to Drugs and Procedures

Despite structured eCRFs, challenges persist in attributing AEs:

• Ambiguity: Symptoms like “fever” may stem from infection, disease, or study drug toxicity.
• Overlap: Procedures (e.g., catheter placement) may introduce risks similar to drug-induced AEs.
• Subjectivity: Different investigators may assess causality differently without conventions.
• Incomplete data: Missing lab or diagnostic information can hinder accurate attribution.

To mitigate these risks, sponsors must provide clear SOPs, training, and conventions for investigators and CRAs, along with edit checks that prevent missing causality fields in eCRFs.

Best Practices for AE Linkage in eCRFs

Sponsors and CROs should adopt the following practices to improve AE linkage quality:

• Use mandatory causality fields for both drug and procedure attribution.
• Integrate drop-down options to reduce variability in responses.
• Implement cross-field validations (e.g., SAE must have causality completed).
• Reconcile causality data across CRFs, narratives, and safety databases.
• Conduct investigator training on AE attribution and regulatory expectations.

For instance, a sponsor SOP may specify that any AE occurring within 24 hours of infusion must be considered “Possibly related” unless clear evidence suggests otherwise. Such conventions reduce variability and inspection findings.

Role of Data Managers and Safety Physicians

Data managers and safety physicians play a critical role in ensuring the reliability of AE linkage data:

• Data managers review AE forms for completeness and trigger queries where causality is missing or inconsistent.
• Safety physicians review SAE narratives and confirm consistency between causality attribution and medical judgment.
• Quality checks are performed during database lock to ensure reconciliation with pharmacovigilance systems.

In one vaccine trial, data managers discovered that several AEs were marked as “Not related” to the study drug, despite timing immediately after vaccination. Queries were issued, and investigators revised entries to “Possibly related,” ensuring accurate signal detection.

Key Takeaways

Linking AEs to study drugs and procedures is a foundational requirement for accurate safety reporting. Clinical teams must:

• Design eCRFs with structured fields for drug and procedure causality.
• Train investigators to apply consistent causality assessments.
• Ensure reconciliation between CRFs, safety databases, and narratives.
• Maintain audit-ready documentation of attribution decisions.

By applying these practices, sponsors can minimize regulatory findings, ensure accurate pharmacovigilance, and protect patient safety across global clinical trials.