And yet, in my experience reviewing data management metrics across dozens of trials, the AE CRF page generates more queries per page than any other section of the case report form. Not the medical history page, with its complex coding requirements. Not the concomitant medication log, with its start and stop dates and overlapping indications. The AE page. The reason is not that coordinators are careless -- it is that every field on this page involves conventions, interdependencies, and judgment calls that are not self-evident from the field labels alone.

An AE term entered as "GI problems" instead of "nausea" sends the medical coder on a guessing expedition. An onset date that postdates the visit date triggers an automatic edit check. A seriousness assessment of "not serious" on an event where the participant was hospitalized creates a logical contradiction that will generate a query before the data management team finishes their morning coffee. And an outcome of "recovered/resolved" with no resolution date is a data point that contradicts itself.

The previous lesson taught you what to capture in the AE source document -- the detailed clinical record from which all downstream data flow. This lesson teaches you how to translate that source data into accurate CRF entries. Every field has conventions. Every convention exists for a reason. And the reason, invariably, is that someone downstream -- a medical coder, a safety reviewer, a regulatory analyst -- depends on the data being right.

And yet, in my experience reviewing data management metrics across dozens of trials, the AE CRF page generates more queries per page than any other section of the case report form. Not the medical history page, with its complex coding requirements. Not the concomitant medication log, with its start and stop dates and overlapping indications. The AE page. The reason is not that coordinators are careless -- it is that every field on this page involves conventions, interdependencies, and judgment calls that are not self-evident from the field labels alone.

An AE term entered as "GI problems" instead of "nausea" sends the medical coder on a guessing expedition. An onset date that postdates the visit date triggers an automatic edit check. A seriousness assessment of "not serious" on an event where the participant was hospitalized creates a logical contradiction that will generate a query before the data management team finishes their morning coffee. And an outcome of "recovered/resolved" with no resolution date is a data point that contradicts itself.

The previous lesson taught you what to capture in the AE source document -- the detailed clinical record from which all downstream data flow. This lesson teaches you how to translate that source data into accurate CRF entries. Every field has conventions. Every convention exists for a reason. And the reason, invariably, is that someone downstream -- a medical coder, a safety reviewer, a regulatory analyst -- depends on the data being right.