As part of our clinical strategy, we bake risk‑based monitoring into Phase II–III and beyond; trivia check: which ICH E6 revision officially endorsed RBM, and what year did that revision publish? We were debating this today while locking our asset’s lifecycle plan.
ICH E6(R2), 2016; some folks cite 2017 as the effective date, but the addendum was adopted in Nov ’16 (see https://database.ich.org/sites/default/files/E6_R2_Addendum.pdf). From experience, bake your ‘trigger-to-action’ logic into the monitoring plan so every KRI threshold change has a clean audit trail — do you do the same?
Pretty sure it was E6(R2) in 2016 — the addendum that says a “systematic, prioritized, risk‑based approach” to monitoring (see 5.0 and 5.18.3), with regional go‑live slipping into 2017. My practical tip: we embed those clause cites in the monitoring plan so audit conversations stay focused on thresholds and KRIs, not definitions. Do you also point teams to E8(R1) for the QbD tie‑in (ICH Official web site : ICH)?
RBM was formally baked in with ICH E6(R2) via the addendum adopted Nov 2016; , the confusion comes from staggered regional effective dates in 2017. If you’re locking your Phase II–III lifecycle plan, make sure section 5.0 risk assessments and KRIs are traceable in the TMF; earlier FDA guidance (2013) already nudged this: Oversight of Clinical Investigations — A Risk-Based Approach to Monitoring | FDA. Curious what tool you’re using to keep the risk log current across amendments?
It’s the GCP E6 Integrated Addendum (Revision 2), adopted in Nov 2016; the regional effective dates sliding into 2017 are what keep the debate alive. For your lifecycle plan, I’d cite 2016 as the endorsement and footnote region‑specific go‑lives; source: https://database.ich.org/sites/default/files/E6_R2_Addendum.pdf. , audits get picky — are you aligning to adoption or implementation year?
Integrated addendum to GCP (Revision 2) in 2016; the real shift was 5.0 “Quality Management” plus explicit room for centralized monitoring. @llee57’s point stands, and earlier FDA RBM guidance (2013) muddied timing: https://www.fda.gov/media/116754/download. For your plan, tie KRIs to a central review cadence and keep a small change log — think cockpit dashboard, not Where’s Waldo.
Short answer: E6(R2) formally baked in RBM in 2016 — call it the method’s coming‑out party… Tiny caveat: FDA and EMA had been nudging RBM earlier (e.g., FDA’s 2013 guidance), and some regions treated the change as effective in 2017. For your monitoring plan, cite Section 5 on quality management and “centralized monitoring,” and if you need a source drop this link: https://database.ich.org/sites/default/files/E6_R2_Addendum.pdf@llee57.
E6(R2), published 2016, is the one — via the integrated addendum that explicitly green‑lit ‘centralized monitoring’ and RBM. , for your Phase II–III lifecycle lock, add a one‑pager in the Monitoring Strategy documenting the risk assessment, triggers, and rationale, and drop the citation in the TMF with the ICH link (https://database.ich.org/sites/default/files/E6_R2_Addendum.pdf). Minor caveat: regulators were encouraging RBM earlier, but for SOPs and audits, that 2016 addendum is the anchor.
It was the E6(R2) integrated addendum in 2016 — RBM got its passport stamped then. For your lifecycle plan, pick 2–3 QTLs tied to critical data and predefine the escalation playbook when one trips; @lhill81, are you setting them at endpoint or process level? Small caveat: E8(R1) and the E6(R3) draft push the risk concepts further, but the official nod came in 2016.