Regulatory Coordinator
Full course · Essential Records Infrastructure & Document Management
Free Lesson Preview
View the Regulatory Coordinator track for current pricing and enrollment options.
View enrollment optionsAlready enrolled? Sign in
Teaches the design of portfolio-wide expiration tracking systems that provide tiered advance notifications, assign renewal responsibility, and verify that renewed documents replace expired versions across all affected study binders.
A principal investigator's medical license at one research site expired on 14 March. The site was running 14 active clinical trials. Not one person noticed until 22 March, when a sponsor's monitor reviewing the regulatory binder for a routine visit flagged the expired license and asked whether the investigator had been conducting study activities -- enrolling participants, making eligibility determinations, performing protocol-required assessments -- during the eight days the license was lapsed.
The answer, of course, was yes. Fourteen studies. Eight days. The investigator had signed eligibility confirmations, reviewed adverse events, and authorized two new enrollments. Every action taken during that period was performed by an individual whose license to practice medicine had, technically, expired. And every study file at the site contained a copy of the same expired license.
The license was renewed. It had always been going to be renewed -- the investigator had submitted the renewal application months earlier, and the state licensing board was simply behind in processing. But the gap existed. It was documented. And for each of those 14 studies, the sponsor had to determine whether a protocol deviation report was warranted, whether the actions taken during the lapse period were valid, and whether the IRB needed to be notified. The paperwork generated by those eight days consumed more staff hours than maintaining a proper tracking system would have consumed in an entire year.
This is not an unusual story. I have seen variations of it at sites of every size, and the pattern is remarkably consistent: the person whose credential expired fully intended to renew it, often had already initiated the renewal process, and the lapse occurred not because anyone was negligent but because no system existed to translate an approaching expiration date into a specific action assigned to a specific person with a specific deadline. The expiration was known. The response was assumed. And in the space between known and assumed, the lapse occurred.
Lessons 1 through 3 of this module addressed version control triggered by events -- protocol amendments, consent revisions, IRB approvals. This lesson addresses version control triggered by time. Expiring documents do not wait for an event to become outdated. They become outdated on a date that is known in advance, printed on the document itself, and entirely predictable. And yet, across the industry, expiration lapses remain among the most common findings during monitoring visits and regulatory inspections.
The reason is not that sites forget dates. The reason is that sites lack systems -- portfolio-wide tracking infrastructure that converts known expiration dates into tiered advance notifications, assigns renewal responsibility to specific individuals, and verifies that renewed documents have replaced expired versions in every affected study file.
What you will learn3 objectives
By the end of this lesson, you will be able to:
Progress saves itself — finish reading and this lesson completes
