AE start date capture – Clinical Research Made Simple

Time of Onset and Resolution Recording in AE Documentation

digi — Mon, 15 Sep 2025 11:09:41 +0000

Time of Onset and Resolution Recording in AE Documentation

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:

Field	Purpose	Example Entry
AE Start Date	Indicates when the AE began	2025-09-14
AE Start Time	Refines onset to exact time (if available)	09:30
AE Stop Date	Captures when the AE resolved	2025-09-16
AE Stop Time	Precise resolution time	14:15
Ongoing Indicator	Flags unresolved events at last visit	Yes / No

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.

Fields Required for Proper AE Documentation in eCRFs

digi — Sun, 14 Sep 2025 09:25:26 +0000

Fields Required for Proper AE Documentation in eCRFs

Essential Fields for Accurate Adverse Event Documentation in eCRFs

Introduction: Why AE Fields in eCRFs Matter

Accurate adverse event (AE) documentation is at the core of clinical trial safety monitoring. The transition from paper case report forms to electronic case report forms (eCRFs) has transformed how AEs are recorded, validated, and reported to regulators. However, the reliability of safety data depends heavily on the fields included in the AE module. Missing or poorly defined fields lead to incomplete data, inconsistent reporting, and regulatory non-compliance. Authorities such as the FDA, EMA, and MHRA expect sponsors to demonstrate that AE data capture systems are robust, validated, and aligned with ICH E2A/E2B standards.

This article provides a detailed tutorial on the required fields for proper AE documentation in eCRFs, with examples, best practices, and real-world case studies. It explains how each field contributes to safety signal detection, pharmacovigilance accuracy, and regulatory inspection readiness.

Core Data Fields for AE Documentation

Each AE reported in a clinical trial must include a minimum set of data points. These fields are considered regulatory essentials and are audited during inspections:

Field	Purpose	Example
AE Term (Verbatim)	Investigator’s description of the event	“Severe headache”
Start Date/Time	Identify onset of the event	2025-08-14 09:30
Stop Date/Time	Identify resolution of the event	2025-08-16 13:00
Severity/Grade	Grading based on CTCAE or protocol-specific scale	Grade 2 (Moderate)
Causality	Relationship to investigational product	Related / Not related
Outcome	Event status	Recovered
Action Taken	Intervention by investigator or sponsor	Dose reduced / Drug discontinued
Seriousness Criteria	Triggers expedited SAE reporting	Hospitalization
MedDRA Coding	Standardized terminology	PT: Migraine

Each of these fields must be mandatory and supported by system edit checks to prevent incomplete data capture. Regulators expect audit trails that document changes made to these fields throughout the trial.

Case Study: SAE Documentation Failure

During an EMA inspection of a Phase II oncology trial, auditors found that the AE module did not require investigators to enter “seriousness criteria.” As a result, several hospitalizations were recorded as routine AEs rather than SAEs. This omission delayed expedited reporting and was cited as a major finding. The sponsor was required to update its eCRF design, retrain investigators, and reclassify past events. This case highlights the criticality of including all mandatory fields in AE eCRFs.

Regulatory Expectations for AE Fields

Agencies require that AE documentation includes enough information to allow regulators to assess causality, severity, and outcome. Key expectations include:

FDA: Inspects completeness of SAE documentation during IND and NDA reviews.
EMA: Requires MedDRA coding for all AE terms submitted via EudraVigilance.
MHRA: Focuses on traceability of AE documentation and audit trails in eCRFs.
CDSCO: Requires sponsors to include seriousness criteria and causality assessments in SAE reports.

Public registries like the ISRCTN registry emphasize standardized AE data capture, reinforcing global regulatory expectations for field completeness and accuracy.

Best Practices for AE Field Design

To minimize errors and regulatory findings, sponsors and data managers should apply the following best practices:

Use drop-down lists for causality, severity, and outcomes to avoid free-text variability.
Configure mandatory field validations for onset, severity, and seriousness.
Incorporate conditional logic (e.g., seriousness criteria only appears if SAE is marked “Yes”).
Enable audit trails to capture any changes in AE documentation.
Provide narrative fields for complex or unusual AEs requiring additional context.

For example, if an investigator enters “chest pain” without causality, the system should prompt completion before allowing form submission. Such safeguards improve data integrity and reduce the number of data queries raised by monitors and data managers.

Integration with Other eCRF Modules

AE documentation must not exist in isolation. Integration with other modules strengthens data reliability:

Concomitant medications: AE forms should link to medications taken during the event.
Medical history: Helps distinguish between pre-existing and new events.
Lab results: Supports objective confirmation (e.g., “ALT increased” linked to laboratory values).

By enabling cross-linkage, sponsors can reconcile safety data across different systems and ensure consistency in regulatory reporting.

Challenges and Solutions in AE Field Documentation

Common challenges in AE field documentation include:

Investigators using ambiguous free-text terms.
Sites skipping optional fields that should have been mandatory.
Inconsistent causality assessments across investigators.

Solutions include developing coding conventions, providing investigator training, and implementing real-time edit checks in the eCRF system.

Key Takeaways

AE documentation in eCRFs is only as reliable as the fields it captures. Sponsors must:

Ensure inclusion of mandatory AE fields such as onset, severity, causality, outcome, and seriousness.
Design systems with validations and edit checks to enforce completeness.
Integrate AE data with concomitant medication, lab, and medical history modules.
Maintain audit trails and provide narrative fields for context.
Continuously train investigators and CRAs on field completion requirements.

By following these practices, organizations can ensure that AE data captured in eCRFs is accurate, complete, and inspection-ready, thereby supporting regulatory compliance and patient safety.