Free Lesson Preview
This is just the beginning
The full CRC track covers 8 courses from study start-up to close-out β the skills sponsors actually look for.
View enrollment optionsAlready enrolled? Sign in
Clinical Research Coordinator
Full course Β· Safety Reporting and Pharmacovigilance for CRCs
Free Lesson Preview
The full CRC track covers 8 courses from study start-up to close-out β the skills sponsors actually look for.
View enrollment optionsAlready enrolled? Sign in
Master the essential data elements, structured approaches, and longitudinal documentation practices for adverse event source records that support regulatory reporting and participant safety.
A monitor arrives at a research site for a routine visit and opens the source records for a participant enrolled in a Phase II oncology trial. Under the adverse event section of the most recent visit record, the coordinator has written: "Participant reports fatigue. Grade 2. Not serious. Possibly related."
That is four data points. And if you had asked me early in my career whether that constituted adequate documentation, I might have said it seemed reasonable. Fatigue is a common adverse event in oncology trials. The coordinator captured severity, seriousness, and causality. What else is there?
Quite a lot, as it turns out.
The monitor needs to know when this fatigue started -- not just that it exists at the time of the visit, but whether it began two days ago or two weeks ago. The monitor needs to know how the event was identified -- did the participant volunteer it spontaneously, or did the coordinator elicit it through systematic questioning? The monitor needs to understand what "fatigue" means for this particular participant -- is this an inability to complete household tasks, or an inability to get out of bed? The monitor needs to know whether the severity has changed since the last assessment, what action was taken with the study drug, whether any concomitant medications were administered, and what the current trajectory looks like.
"Participant reports fatigue. Grade 2. Not serious. Possibly related" is a data snapshot. What the safety record requires is a clinical story -- one that begins at onset, continues through each assessment, and ends at resolution. The AE source record is where that story is written. And if it is written incompletely, every downstream record -- the CRF, the safety narrative, the regulatory submission -- inherits that incompleteness.
This lesson teaches you what belongs in the AE source record and how to capture it. You have already learned to identify adverse events (Module 2), grade their severity (Module 3, Lesson 1), assess their seriousness (Module 3, Lesson 2), and understand causality assessment (Module 3, Lesson 4). Now you bring all of that together into a single, structured record that serves as the foundation for everything that follows.
Progress saves itself β finish reading and this lesson completes