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 RC to build scalability into the records architecture from the outset, using modular design principles that allow the system to grow as the site's research portfolio expands.
A site director calls a meeting on a Tuesday morning. The agenda is one sentence: the institution has signed a contract with a new sponsor bringing ten additional clinical trials to the site over the next 18 months. The portfolio will grow from 12 active studies to 22. The site director asks the regulatory coordinator a question that sounds simple but is not: "Can our current systems handle this?"
The honest answer, at most research sites, is: it depends on what was built.
If the records architecture was designed study by study -- each new trial adding its own filing conventions, its own folder structure on the shared drive, its own interpretation of where site-level records belong -- then the answer is no. Not because the system will fail spectacularly, but because it will degrade incrementally. Each new study adds another slight variation. The time to file a record increases. The time to retrieve a record during a monitoring visit increases. Cross-referencing breaks down because the 13th study's binder was set up by a new coordinator who did not know the cross-referencing conventions established for the first 12. And by the time the 18th study opens, the regulatory coordinator is spending more time maintaining the architecture than managing the records within it.
But if the architecture was designed with growth in mind -- modular, standardized, and governed by procedures rather than institutional memory -- then the answer is yes. Adding a new study is not a design exercise. It is an implementation exercise: instantiate the template, apply the taxonomy, connect the cross-references, verify the setup, and move on. The architecture absorbs the new study the way a well-designed bookshelf absorbs a new book. The shelf does not need to be rebuilt. The book just goes in the right place.
This lesson teaches you to build the bookshelf, not just shelve the book. It is the capstone of Module 2, and it draws on everything you have learned so far: the three architecture principles from Lesson 1 (standardization, scalability, retrievability), the filing taxonomy and naming conventions from Lesson 2, and the dual-repository classification from Lesson 3. The question now is: how do you design an architecture that works not just for the studies you have, but for the studies you do not yet know are coming?
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
