The behind-the-curtain look at how a clinical research site actually runs. Written for people looking to enter the clinical trial world, for new coordinators learning the ropes, and open to anyone curious what happens at clinical research sites.

In this file:

·        Why "the day you found out" starts the clock, not "the day it happened"

·        The difference between an adverse event and a serious one, and why the line matters

·        The 24 hour habit that has nothing to do with an FDA rule, and everything to do with not missing a deadline

·        MedDRA, and why the exact words a patient uses never make it into the report

Walter called the site on a Tuesday, three days after his last dose in Study OLS-114. He mentioned it almost as an afterthought, at the end of a call about something else entirely: a headache, bad enough that he'd taken something for it, gone by the next morning. Nani almost let the call end there. Then she caught herself. That is exactly the sentence a coordinator has to stop and pull apart before hanging up.

Nani's first instinct was to ask when the headache started. The more important question was when she found out about it, because that is the date that actually matters on paper. An adverse event's reporting clock does not start when a patient experiences something. It starts when the site becomes aware of it, the moment of knowledge, not the moment of onset. Walter's headache happened three days ago. Nani's clock started the second he mentioned it on the phone.

Not every adverse event is the same kind of urgent, and mixing the two up is one of the fastest ways a new coordinator either over-reports or, worse, under-reports. An adverse event is any unfavorable medical occurrence in a patient during the study, whether or not it turns out to be related to the study drug. A serious adverse event, an SAE, is a narrower category: death, a life-threatening event, hospitalization or a longer hospital stay, persistent or significant disability, a birth defect, or another event a physician judges to be medically important. Walter's headache, resolved overnight, no hospital visit, is an adverse event. It is not, on the facts as reported, serious. That distinction determines which clock Nani is actually running.

Most site staff will tell you a serious adverse event has to be reported within 24 hours. That number is real, but it is not, strictly speaking, an FDA rule written for sites. It is almost always a requirement built into the study's own protocol and the site's contract with the sponsor, because the sponsor has its own federal clock running once the site tells them. FDA's timeline for IND safety reporting, under 21 CFR 312.32, gives sponsors 7 calendar days to report an unexpected fatal or life-threatening reaction to the agency, and 15 calendar days for other serious, unexpected reactions, counted from the sponsor's determination that the information qualifies for reporting. Every one of those federal clocks depends on the sponsor knowing about the event as early as possible, which is exactly why almost every protocol pushes the site's own reporting window down to 24 hours. The site's tighter deadline exists to protect the sponsor's federal one.

Note to File: An SAE report that is accurate and thirty minutes late will always beat one that is fast and wrong. But being fast and right is the actual job. Build the habit of flagging anything that gives you pause the moment you hear it, before you have even decided whether it meets the serious threshold. Let the sponsor's medical monitor help make that call. Your job is not to filter what gets reported. It is to make sure nothing worth reporting gets missed because you decided too early it wasn't.

Walter told Nani his head "felt like it was in a vice." The report Nani eventually files will say "headache." That is not Nani editing Walter down, or a coordinator being clinical for its own sake. Every reported event gets translated into a standardized term from MedDRA, the Medical Dictionary for Regulatory Activities, so that a headache reported at Nani's site in one country can be counted, searched, and compared against a headache reported at a different site on a different continent, in a different language. A vivid description helps a clinician understand severity in the moment. A standardized term is what lets the sponsor look across thousands of reports and actually see a pattern, if one exists. Losing the color of Walter's own words is the cost of making his data count toward something bigger than his own case.

An adverse event's clock starts the moment the site knows, not the moment it happened. Serious and non-serious are not the same urgency, and mixing them up is its own kind of error. The 24 hour habit most sites live by is not an FDA rule, it is a protocol requirement built to protect a federal deadline the site never sees directly. And the plain words a patient uses still matter for understanding what happened, even after they are translated into the standardized term that lets the sponsor see the pattern across every site running the study. Nani hung up, opened the safety reporting form, and started the clock.

·        Root to Rx: the newsletter and The Root Room, the patient-facing side of the same story, at roottorx.com

·        Root to Rx: free Patient Logs at shop.roottorx.com, for tracking exactly the kind of detail Walter almost didn't mention

·        21 CFR 312.32 — IND Safety Reporting (eCFR)

·        FDA — E6(R3) Good Clinical Practice, Guidance for Industry (adopted by FDA Sept 9, 2025)

·        ICH E6(R3) Good Clinical Practice — Step 4 Final Guideline (Jan 6, 2025)_Step4_FinalGuideline_2025_0106.pdf)

·        MedDRA — Medical Dictionary for Regulatory Activities

·        ClinicalTrials.gov — NIH/NLM clinical trials registry

•  •  •

The Open Site File is general education about how clinical research sites work. It is not regulatory, legal, or medical advice, and it is not tied to any specific study, sponsor, or employer. Study OLS-114, Walter, and all names are invented. Always follow your own site's SOPs, your protocol, and your PI and QA team. Characters are composites.

Filed by Justin Yamashita, MSc., Open Label Media

Next in the file: Issue 7, how a site and a sponsor decide whether Walter's headache was caused by the study drug at all.