Clinical Research Foundations and Regulatory Framework
This domain tests whether you can name which rule governs a situation - not just recall acronyms. Items combine ICH GCP principles, US FDA regulations, the Common Rule, and the division of responsibility between sponsor, investigator, IRB/IEC and monitor. Expect scenarios that ask who must act, in what order, and which document controls when a protocol, an SOP and a regulation point in different directions.
The authority hierarchy
- ICH E6 GCP is an international guideline; FDA regulations (21 CFR) are enforceable law where they apply. The protocol may be stricter than the regulation, never looser.
- Two GCP principles run through every question: participant rights, safety and well-being outrank science; and the data must be credible.
- Map the parts: 50 informed consent, 56 IRB, 312 drugs/biologics IND, 812 devices IDE, 11 electronic records, 54 financial disclosure, 45 CFR 46 the Common Rule (2018 revision effective 21 January 2019, single IRB for federally funded multi-site studies from 20 January 2020).
- ICH E6(R2) added quality management and risk-based approaches; E6(R3) modernised them further in 2025 but did not remove the investigator's core duties.
Who does what
- Sponsor: initiates and funds, holds the IND/IDE, selects investigators, ensures monitoring, submits expedited safety reports.
- Investigator: signs the 1572 (or device agreement), conducts per protocol, delegates only to qualified staff, reports serious adverse events to the sponsor.
- IRB/IEC: initial and continuing review, approves amendments, reviews unanticipated problems.
- Monitor: verifies; does not approve data and never makes clinical decisions.
Development phases
Phase I (roughly 20–80 participants): safety, PK, maximum tolerated dose. Phase II: 100–300, efficacy signal and dose finding. Phase III: hundreds to thousands, confirmatory. Phase IV: post-approval.
Worked example
A coordinator learns a subject will miss the mandatory Week 8 MRI and the PI says "just skip it." Reasoning: there is no immediate hazard, so this cannot be handled as an emergency change. A prospective change to a required assessment is a protocol amendment requiring sponsor agreement and IRB approval before implementation. Skipping the scan is an unapproved deviation: document it, assess impact on the primary endpoint, and report per site SOP. The PI's verbal instruction does not substitute for approval.
Traps that cost marks
- Assuming "GCP says" makes something legally binding in every country.
- Confusing IRB approval with regulatory-authority authorisation of an IND or IDE.
- Believing an amendment can be implemented the day it is written, or that a monitor can approve it.
- Using "deviation" and "serious noncompliance" as synonyms.