◆ OCREA™ · Restricted Access

Licensed Access Required

This content is licensed under AH Investments LLC. If you've received an access code by email, enter it below.

Need access? Contact Alejandra E. Nieto, M.D., MBA, PhD

info@ocreaacademy.com →
OCREA™ · Enterprise Clinical Development Capability Platform
Tools Hub
Nine operational tools mapped to the nine phases of the Medical Monitor workflow — from protocol design through post-approval lifecycle. Designed for Medical Monitors, Clinical Scientists, Clinical Science Liaisons, and Senior Clinical Leaders in oncology drug development.
9
Workflow phases
6 new · 3 existing
Tools
MM · CS · CSL
Audience
All phases
Coverage
Phase 1
Protocol Review Checklist
Pre-submission design review — eligibility, endpoints, DLT, safety plan, ICF
New
Phase 2
Site Activation Readiness
FPI readiness — 5 domains, essential docs, IRB strategy, SIV delivery
New
Phase 3
Eligibility Decision Tool
Edge case classification, waiver framework, pattern monitoring
New
Phase 4
Safety Monitoring Command
SAE triage, signal detection, deviations, DSMB prep, cross-site patterns
New
Phase 5
Oncology Data Review
Day-to-day CRF review — Hy's Law, cardiac, efficacy, narrative
Existing
Phase 6
Tables & Listings
TLF medical review for CSR construction
Existing
Phase 7
IND / NDA / BLA
CTD Module 2.5, 2.7, ISS/ISE, submission integration
Existing
Phase 8
IR Response & AdCom
FDA/EMA Information Requests, ODAC prep, label negotiation, CRL
New
Phase 9
PMR/PMC Lifecycle
Post-marketing commitments, PSUR, REMS, confirmatory, label expansion
New
OCREA™ Tools · Phase 1 — Protocol Development & Study Design
Protocol Review Checklist
Pre-submission protocol design review · Medical Monitor & Clinical Scientist · All phases · All therapeutic areas
6
Review domains
48
Checklist items
MM · CS
Audience
Pre-IND · IND · Amendment
Stages
Overview
Eligibility
Endpoints
DLT & Dose
Safety Plan
Statistical
ICF Review
When to use this tool
Pre-IND / IND protocol submission
The Medical Monitor reviews the draft protocol before submission to FDA/EMA. Every item in this checklist must be assessed — gaps identified here can be closed before the protocol is filed, avoiding deficiency findings from the agency.
Protocol amendment review
When an amendment is drafted (e.g., eligibility change, dose modification, new safety population), use this tool to verify that all affected domains are assessed and that the change does not create downstream inconsistencies.
Inherited trial review
When a Medical Monitor inherits an ongoing trial from a prior MM, this tool provides the structured review to verify that the protocol as currently conducted is consistent with the approved version and that all safety and eligibility decisions are defensible.
Six review domains
1
Eligibility criteria design
Each inclusion/exclusion has a documented clinical rationale; criteria are operationally feasible; population matches the intended label indication.
2
Endpoint selection & definitions
Primary endpoint matches regulatory expectations for the indication; secondary endpoints add scientific value without diluting statistical design.
3
DLT definition & dose rationale
DLT criteria are specific, class-appropriate (IO/ADC/targeted); dose rationale aligned with Project Optimus expectations.
4
Safety Management Plan
SAE reporting pathway, 24-hr emergency contact, management algorithms for class-specific events (irAE, ILD, cardiac) all specified.
5
Statistical design integrity
Sample size justification matches endpoint and effect size assumption; interim analyses and alpha control specified; handling of missing data pre-specified.
6
Informed Consent Form scientific content
Risk language accurately reflects IB and preclinical findings; benefits not overstated; post-trial care clearly described.
Note: Work through each tab in sequence. Check items as you complete them. This tool is meant to be used alongside the draft protocol document — not as a replacement for detailed review, but as a structured framework that ensures no domain is missed.
Inclusion criteria review
  • Diagnosis criterion is specific (histology, stage, biomarker status) and matches the proposed label indication
  • Age range and performance status (ECOG/KPS) are clinically appropriate for the treatment intent
  • Prior treatment requirements are specific (lines of therapy, specific agents, response status) and operationally verifiable
  • Organ function thresholds (bone marrow, renal, hepatic, cardiac) are safety-justified, not arbitrary
  • Biomarker requirements specify tissue type, assay, cutoff, and central lab vs local testing
  • Measurable disease criterion (RECIST 1.1 or other) explicitly stated
  • Time windows for prior treatment washout are specified and clinically defensible
Exclusion criteria review
  • CNS metastases handling is explicit (excluded / stable / treated with specific criteria)
  • Prior malignancies handling is specified (disease-free interval, type of prior malignancy)
  • Autoimmune disease criteria are class-appropriate (critical for IO trials)
  • HBV/HCV/HIV serology requirements match current regulatory expectations
  • Contraception and pregnancy requirements are specific and compliant with local regulation
  • Concomitant medication exclusions are clinically necessary and operationally clear
  • No exclusion is present that is not clinically justified (avoid over-restriction)
Common MM finding: Eligibility criteria designed for Asian populations (BMI caps, weight ranges, age ceilings) that create enrollment barriers in US/EU when the trial is globalized. These require adjustment or separate eligibility criteria per region — not granted waivers during conduct.
Primary endpoint review
  • Primary endpoint matches regulatory expectation for the indication (e.g., OS for 1L metastatic, PFS or ORR for later lines)
  • Endpoint definition is explicit and matches standard guidelines (RECIST 1.1, iRECIST, Lugano, ASTCT) as applicable
  • Censoring rules are specified for time-to-event endpoints (crossover, subsequent therapy, loss to follow-up)
  • Confirmation requirement for response is specified (required / not required, time interval)
  • Central review vs investigator assessment is specified; if both, the primary is identified
Secondary & exploratory endpoints
  • Each secondary endpoint has a specific definition and analysis plan
  • PRO endpoints specify instruments, timing, and completion targets (EMA Rev.6 expects ≥70% completion)
  • Biomarker endpoints specify assays, timepoints, and exploratory vs confirmatory status
  • Safety endpoints (irAE rates, cardiac events, ILD rates) are specifically named if relevant to class
Red flag: If ORR is the primary endpoint in a single-arm Phase 2, verify that the comparison to historical control is statistically justified and that the Phase 3 design is already scoped as RCT. Single-arm ORR cannot support full approval in most oncology indications.
DLT definition review (Phase 1)
  • DLT window is specified (typically C1, 21 or 28 days) with exposure requirement
  • Hematologic DLT criteria are class-appropriate (e.g., neutropenia duration/severity thresholds)
  • Non-hematologic DLT criteria are class-appropriate and IO-specific if applicable (Grade 2 pneumonitis for IO, Grade 3+ rash for EGFR, etc.)
  • DLT exclusions are justified (e.g., Grade 3 nausea controlled with antiemetics may not be DLT)
  • Combination-specific DLT attribution rules are clear (when one drug vs both are held)
Dose rationale (Project Optimus)
  • Starting dose rationale includes preclinical NOAEL, HED calculation, and FIH margin
  • Escalation design specified (BOIN, mTPI, 3+3) with target DLT rate
  • For targeted agents / IO: RP2D selection not assumed to equal MTD (Project Optimus alignment)
  • Exposure-response analysis plan specified
  • Multiple dose comparison in Phase 2 planned if RP2D < MTD
Project Optimus check: Since May 2021 (Sotorasib, Amgen) FDA has required dose-optimization data in most oncology submissions. A protocol that selects RP2D = MTD without exposure-response or multi-dose comparison is likely to receive an FDA Type A meeting request to address this pre-submission.
Safety Management Plan components
  • SAE reporting pathway (site → sponsor → regulatory) specified with timelines (24-hr for all SAE; 7-day for fatal/life-threatening SUSAR)
  • 24-hour Medical Monitor emergency contact specified in protocol and SMP
  • AE grading framework specified (CTCAE v5.0 standard; supplementary scales for specific events)
  • Class-specific management algorithms included: irAE (if IO), ILD (if ADC with ILD risk), cardiac (if cardiotoxic class), CRS/ICANS (if cell therapy)
  • Dose modification rules: delay, reduce, hold, discontinue — specified for each toxicity grade
  • Rechallenge criteria specified after dose modification
  • Drug-induced liver injury (DILI) framework: Hy's Law triggers, workup, reporting
  • QT monitoring plan if applicable (ECG frequency, QTc thresholds)
Data Safety Monitoring Board
  • DSMB charter drafted with meeting frequency (typically every 3-6 months in Phase 3)
  • DSMB membership independence verified (no sponsor employees voting)
  • Stopping rules specified (safety, futility, superiority)
  • Statistical framework for interim analyses specified (alpha spending, conditional power)
Sample size & power
  • Sample size calculation is explicit: effect size, power, alpha, dropout assumption
  • Effect size assumption is clinically reasonable and supported by prior data
  • Dropout assumption matches the indication (oncology: typically 10-20%)
  • If stratified randomization: stratification factors specified and rationale given
Analysis populations & endpoints
  • ITT, mITT, PP, Safety populations defined with specific inclusion criteria
  • Primary analysis population clearly stated (typically ITT for Phase 3 efficacy, Safety for safety)
  • Estimand framework per ICH E9(R1) addressed for primary endpoint (intercurrent event handling)
  • Missing data handling specified (sensitivity analyses if missing data expected)
Alpha control & multiplicity
  • Multiple testing strategy specified (hierarchical, Hochberg, Bonferroni)
  • Interim analyses specified with alpha spending function
  • Subgroup analyses pre-specified vs post-hoc clearly distinguished
Scientific content review
  • Study purpose is described in plain language (avoid technical jargon)
  • Investigational nature of the treatment is clearly stated
  • Procedures are listed with timing and duration
  • Known risks are described with frequency and severity (consistent with current IB)
  • Theoretical risks from mechanism are included if relevant
  • Potential benefits are described without overstating (no promises of efficacy)
  • Alternative treatments are mentioned
  • Voluntary nature and right to withdraw are clearly stated
  • Compensation and cost coverage are specified
  • Confidentiality and data protection are addressed (HIPAA/GDPR per region)
  • Post-trial treatment access is described if applicable
  • Contact information for questions/emergencies is clearly visible
Readability & compliance
  • Reading level appropriate for typical patient (8th-grade level or lower preferred)
  • Translation plan specified if enrolling non-English speakers
  • 21 CFR 50.25 elements all present (US trials)
  • EU CTR / ICH E6(R3) elements present (global trials)
MM sign-off: The ICF is the document the patient reads. Every risk the MM knows must be disclosed. Every benefit described must be defensible. This is the document where softening risk language or overstating benefit creates both regulatory and ethical exposure.
OCREA™ Tools · Phase 2 — Site Start-up & Trial Activation
Site Activation Readiness Assessment
FPI readiness verification · Essential documents, IRB/EC strategy, SIV delivery, 5-domain framework
5
Readiness domains
36
Verification items
MM · CS · CRA
Audience
Per site
Applied
Overview
Essential Docs
IRB/EC Strategy
SIV Delivery
FPI Readiness
Site Signals
Site-by-site activation workflow
Not delegable to CRA
This tool addresses the Medical Monitor's non-delegable responsibilities in site activation. The CRA handles administrative document collection; the MM performs the clinical review of those documents and makes the final authorization decision.
Activation sequence — run in order
1
Essential documents review (in parallel with CRA)
MM reviews IB currency, protocol version, ICF scientific content, and Safety Management Plan delivery — concurrent with CRA's administrative review, not sequential.
2
IRB/EC strategy assessment
Confirm central vs local IRB, review any local modifications for clinical acceptability, escalate unacceptable modifications before SIV.
3
Site Initiation Visit delivery
MM personally delivers trial rationale, eligibility rationale, DLT/irAE/ILD algorithms, SAE expectations. PI must be present for full duration — not partial attendance.
4
FPI readiness verification — 5 domains
DLT knowledge, 24-hr emergency contact, CTCAE currency, combination management, ICF quality. All five must be verified before authorization.
5
FPI authorization
Signed by MM only after all preceding domains complete. Authorization is documented in site file with date and MM signature.
Common start-up failure: Activating a site under timeline pressure without completing all 5 FPI readiness domains. Sites activated with gaps will generate protocol deviations and safety events in the first 4-8 weeks of enrollment — creating cleanup work that exceeds the timeline savings.
Investigator's Brochure (IB) verification
  • Current IB version provided to site (match sponsor-approved version)
  • Reference Safety Information (RSI) is current — new safety events added since last version
  • Site acknowledgment of IB receipt documented in site file
  • PI has read the IB (not just received it) — verifiable at SIV
Protocol & amendments
  • Current approved protocol version on file at site (IRB-approved)
  • All protocol amendments through current date are on file
  • No version mismatch across sites (verify with master list)
  • Amendment training documented for all site staff
Informed Consent Form (ICF)
  • IRB/EC-approved ICF matches sponsor-approved version in all safety-relevant content
  • Any local IRB modifications reviewed by MM for clinical acceptability
  • Translated versions (if applicable) confirmed accurate by qualified reviewer
  • Version control and expiration date confirmed
Safety Management Plan (SMP)
  • SMP delivered to site team
  • SAE reporting pathway confirmed operational (test submission verified)
  • 24-hour emergency contact number confirmed active and known to site
  • Class-specific algorithms (irAE, ILD, cardiac) delivered as supplement
Red flag: Site operating on outdated IB. An outdated IB means expectedness classification of new AEs will be incorrect — directly affecting SUSAR reporting obligations and creating a reporting compliance issue before the first patient is enrolled.
Central IRB (cIRB) review
  • cIRB approval letter on file with specific protocol version referenced
  • cIRB approval covers all proposed procedures and populations
  • Site's reliance agreement with cIRB documented
  • Continuing review date noted for tracking
Local IRB/EC review
  • Local IRB approval letter on file with specific protocol and ICF versions
  • Any modifications from sponsor-approved versions documented
  • Modifications reviewed for clinical acceptability (see table below)
  • Unacceptable modifications escalated and resolved before SIV
Modification classification — MM decision framework
Additional safety monitoring
Typically acceptable. If the local IRB adds ECG, labs, or follow-up beyond protocol — may strengthen the trial. Consider adopting trial-wide if clinically valuable.
Narrower eligibility
Conditionally acceptable at that site. May affect enrollment feasibility; does not compromise data integrity. Document and proceed.
Softened risk language in ICF
Not acceptable Escalate. The ICF must convey the risks accurately. Softened language compromises informed consent and creates ethical and legal exposure.
Modified DLT definition
Not acceptable Escalate. DLT criteria are trial-wide; site-specific variation compromises dose escalation integrity.
Additional procedures (site-specific)
Acceptable if clinically non-impacting. Verify no interference with protocol assessments.
Modified stopping rules
Not acceptable Stopping rules are trial-wide statistical parameters. Site cannot modify.
SIV clinical content — MM personally delivers
  • Trial rationale and scientific framing (why this trial, where it sits in the program)
  • Critical eligibility criteria with clinical rationale (not just read-through)
  • DLT / irAE / ILD algorithms discussed with example cases
  • SAE reporting expectations (24-hour clock, required information at initial notification)
  • Medical Monitor contact protocol — who to call, when, for what
  • Dose modification rules walked through for top 5 toxicity scenarios
Documentation verified at SIV
  • FDA 1572 (or equivalent) listing PI and sub-investigators is current
  • All listed personnel have current licenses and appropriate oncology trial experience
  • GCP training current for all listed personnel (within 2-3 years typically)
  • Protocol-specific training completed and documented for all listed personnel
  • Site pharmacy setup for IP handling (storage, dispensing, accountability)
  • Central lab / imaging contracts in place if applicable
  • Research nursing / coordinator availability confirmed
Consent process verification
  • Who obtains consent identified (PI or named sub-investigator)
  • Consent location appropriate (private consent room, not hallway)
  • Translation services available if enrolling non-English speakers
  • Process for re-consent if new safety information emerges
Domain 1 — DLT/Safety operational knowledge
  • PI can articulate the DLT definition without referring to the protocol
  • Sub-Is can describe the irAE management algorithm for top toxicities
  • Study coordinator knows SAE reporting timeline and information required
Domain 2 — 24-hour emergency contact protocol
  • Site has 24/7 on-call investigator or designated sub-I protocol
  • Sponsor MM 24/7 emergency contact documented and known
  • Written SOP at site defines what constitutes sponsor notification emergency
  • Test question verified: "Grade 4 pneumonitis at 2 AM Saturday — what happens?"
Domain 3 — CTCAE grading currency
  • Site using current CTCAE v5.0 for all grading
  • Class-specific grading frameworks understood (ASTCT for CRS/ICANS if CAR-T; Lee et al 2019)
  • ILD grading per mechanism-specific scale if ADC with ILD risk
Domain 4 — Combination management
  • Site understands which drug to hold for specific toxicity categories
  • Site knows when both drugs must be held
  • Permanent discontinuation rules for single-component toxicities known
Domain 5 — Informed consent quality
  • Site has clearly defined consent process (not ad hoc)
  • Consenter understands specific risks of this IP (preclinical tox, human data, theoretical)
  • Process accommodates typical patient population (language, health literacy, time)
  • Re-consent plan if new safety information emerges (21 CFR 312.32)
FPI authorization decision: All 5 domains verified → authorize. Any gap → do NOT authorize; schedule remediation (supplemental call, re-training, additional documentation). Document the authorization decision in site file with date and MM signature.
Green flags during site start-up
PI engagement signals
Full SIV attendance by PI, not delegated. PI asks specific questions about DLT scenarios and edge cases. Team has read the protocol before SIV. Questions demonstrate clinical thinking, not just procedural compliance. Team asks about MM availability and emergency protocol.
Red flags during site start-up
PI disengagement signals
PI delegates SIV to sub-I or coordinator. Team has not read protocol and asks basic questions suggesting unfamiliarity. No questions about DLT or safety management — suggests no clinical thinking about decisions trial will require. Team says trial is "similar to a previous trial" and does not engage with specifics.
Operational red flags
Documentation and process gaps
Sub-investigators listed on 1572 without protocol training. Pharmacy or lab contracts not executed. Research coordinator unavailable or unknown. ICF process not clearly defined. No written 24-hour emergency SOP.
Escalation matrix
One green flag missing
Address at SIV; may still authorize FPI after remediation
One red flag present
Delay FPI until addressed; schedule supplemental training or documentation session
Multiple red flags
Do not authorize FPI. Escalate to Clinical Ops leadership. Consider whether this site is appropriate for this trial.
PI absent from SIV
Do not authorize FPI based on SIV alone. Schedule supplemental call with PI covering safety content. Document.
OCREA™ Tools · Phase 3 — Enrollment & Eligibility Review
Eligibility Decision Tool
Edge case classification · Waiver framework · Pattern monitoring · MM decision documentation
3
Question framework
5
Edge case types
4
Monitoring signals
MM
Primary user
Overview
3-Question Framework
Edge Cases
Waiver Decision
Pattern Monitoring
Amendment Trigger
The MM's daily enrollment work
What this tool does
Every week during enrollment, sites submit eligibility questions to the Medical Monitor: borderline lab values, treatment-free interval boundaries, asymptomatic prior conditions, ECOG reclassifications, historical biomarker data. This tool provides the structured framework to respond correctly to each question and to monitor for systematic drift across sites.
Core principle: The default answer to waiver requests is NO
Waivers are protocol deviations. They compound across the trial. They create precedent. They appear in the CSR deviation listing and may be reviewed by FDA inspectors. The MM's authority is to apply the protocol as written and to propose amendments when the protocol needs to change — not to grant waivers case-by-case.
Decision workflow — follow in order
1
Apply the Three-Question Framework
Classify the request: safety risk, data integrity concern, or regulatory population definition?
2
Identify the edge case type
Borderline lab, washout boundary, asymptomatic prior condition, ECOG reclassification, or historical biomarker.
3
Apply the No-Waiver Principle
Default response is NO. Only three narrow exceptions justify waiver consideration.
4
Document the decision
Every decision — approved or denied — is documented in the site file with MM rationale.
5
Monitor for patterns
Track waiver requests by site. Pattern of similar requests across sites indicates the criterion needs amendment, not case-by-case waivers.
The Three-Question Framework
Question 1 — Does this criterion address a safety risk?
Example: Organ function thresholds (ANC, platelets, creatinine, bilirubin). Cardiac ejection fraction minimums. Hepatic function thresholds for drugs with hepatic metabolism.

If YES: waiver risks patient harm. The threshold exists because below it, the drug may be unsafe. Granting a waiver means the patient may be exposed to a dose the drug was not designed for.
Question 2 — Does this criterion address data integrity?
Example: Washout periods between prior therapy and study drug. Minimum follow-up after radiation. Excluding patients with conditions that confound endpoint assessment.

If YES: waiver risks uninterpretable endpoints. The criterion protects the ability to attribute response and AEs to the study drug. Granting a waiver introduces confounding that cannot be removed retrospectively.
Question 3 — Does this criterion define the regulatory population?
Example: Biomarker status (HER2+, EGFR+, BRAF V600E, MSI-H). Prior treatment lines (1L vs 2L+). Histology specifics for indication-specific trials.

If YES: waiver risks including patients outside the label indication. The criterion defines who the drug is for. Granting a waiver creates a dataset that cannot support the intended submission.
Key insight: A single criterion may address multiple dimensions. ANC 1500 is both safety (neutropenia risk) and data integrity (attribution of neutropenic events). The most restrictive dimension governs the decision.
Five most common edge cases — click to see decision guidance
Borderline lab values
ANC 1450 · Plt 99k · CrCl 48
Washout boundaries
Last chemo 27 days ago
Asymptomatic priors
Old brain mets · HBV+
ECOG reclassification
Screening ECOG 2 → 1
Historical biomarkers
HER2+ 18 months ago
Borderline lab values (ANC 1450 when criterion is ≥1500)
Typical MM response: This is usually a rescreening question, not a waiver question. Ask: is a repeat lab the same day or the next day permitted by protocol? If the current value is genuinely transient (e.g., dehydration, recent infection resolved), a repeat value may meet criterion. If the value is stable, the patient does not meet criterion. Accepting the PI's clinical speculation that it is "transient" without a confirmatory repeat value is not defensible documentation.
Example: CrCl 48 when criterion is ≥50. Patient rehydrated → repeat CrCl 54. Patient qualifies with documentation of both values. This is not a waiver; this is rescreening.
Treatment-free interval boundaries (last dose 27 days when washout is 28 days)
Typical MM response: Ask the site to wait one day. The washout period exists for PK, PD, and attribution reasons. A one-day accommodation is operationally trivial and protects data integrity. If the site cannot wait (e.g., patient's PS is rapidly declining), the patient likely has other issues that affect eligibility. A waiver of washout because "the patient cannot wait" suggests the patient may not be stable enough for the trial.
Asymptomatic prior conditions (brain mets treated 6 months ago, asymptomatic)
MM decision requires reading the exact criterion. Many trials specify "no active CNS metastases" — in which case stable, treated, asymptomatic patients meet criterion. Other trials say "no prior CNS metastases" — in which case the patient does not meet criterion regardless of current status. The decision is interpretation of the criterion as written, not a waiver. Document the interpretation with the criterion text and clinical reasoning.
HBV example: Protocol excludes "active HBV infection." Patient has HBsAg+ but HBV DNA undetectable on antiviral therapy. Most specialists would classify as inactive. MM interpretation: inactive, meets criterion, document rationale and hepatology consult.
ECOG reclassification requests
MM response: The screening ECOG is the protocol-defined baseline. Patient assessed as ECOG 2 at screening is ECOG 2 for the trial, regardless of how they feel a week later. Reassessing at enrollment to downgrade is reclassification, not reassessment. If the site genuinely believes the screening assessment was wrong, the patient should be formally rescreened — which requires documentation of the rescreen rationale.
Pattern signal: Multiple sites requesting ECOG reclassification may indicate systematic overstatement at screening to avoid screen failures — a data integrity concern requiring central monitoring review.
Historical biomarker data (HER2+ from 18 months ago)
Decision depends on protocol specification. If the protocol requires "confirmed within 6 months" or "fresh biopsy," historical data does not meet criterion regardless of the patient's clinical course. If the protocol allows "archival tissue acceptable," historical data meets criterion. If the criterion is ambiguous, MM interpretation with documented rationale is required — and the pattern of such requests may indicate protocol amendment is needed.
The three narrow exceptions for waiver consideration
1. Transcription or timing errors
The value actually meets criterion; a documentation error caused the discrepancy. A repeat lab the same day shows ANC 1600 — the 1450 was an analytical artifact. This is not a waiver; it is a correction. Document the corrected value and source.
2. Minor numerical boundary with documented medical equivalence
ANC 1480 vs. required 1500 for a trial where the safety population is heavily pretreated and the analytical window of the criterion is conservative. Requires MM clinical assessment AND documentation. Use sparingly — overuse becomes pattern-waiver.
3. Criterion ambiguity requiring interpretation
Protocol says "no prior checkpoint inhibitor" but patient received a CTLA-4/PD-1 bispecific in a Phase 1 trial 3 years ago. Interpretation of whether this meets exclusion requires MM judgment. Document the interpretation and reasoning; apply consistently across all sites for similar cases.
Decision documentation template
Every waiver decision — approved or denied — requires the following in the site file
Patient ID (blinded): ____
Date of request: ____
Site / PI: ____
Specific criterion in question: (exact protocol text) ____
Clinical details: (relevant values, dates, clinical context) ____
Three-Question Framework classification: Safety / Data Integrity / Regulatory Population
Edge case type: (one of five) ____
MM decision: Approved / Denied / Rescreening required / Interpretation
MM rationale: ____
MM signature and date: ____
Audit readiness: Every waiver decision is inspection-reviewable. A waiver granted without documented rationale is worse than a waiver denied — because the auditor cannot see the clinical judgment. Thorough documentation protects both the patient and the MM.
Four enrollment pattern signals to monitor
Signal 1 — Screen failure rate anomalies
Program average screen failure rate establishes baseline. Site rate <50% of average: possibly incomplete screening documentation, or eligibility drift. Site rate >200% of average: possibly rigid interpretation, poor pre-screening, or population mismatch. Both directions warrant investigation.
Signal 2 — Site-specific borderline value clustering
Central monitoring of baseline values can detect clustering at eligibility thresholds. Site 14 shows 78% of patients with baseline ECOG PS = 1 vs program average 45%. Signal: the site may be systematically rounding ECOG 2 patients to 1. Triggers central review of source documentation.
Signal 3 — Enrollment velocity divergence
High-performing sites exist. Velocity alone is not a red flag. But velocity combined with other signals (low screen failure rate, borderline clustering, high deviation rate, underreported SAEs) creates a composite pattern. Sites at 3× program rate deserve closer monitoring review.
Signal 4 — Waiver request frequency
Track waiver requests by site. A site submitting 15 waiver requests when program average is 2 per site is a pattern — regardless of individual waiver reasonableness. The pattern itself is the signal.
Investigation protocol when signal detected
1
Central review of source documentation
Does the documented value match the clinical description in source records?
2
Screen failure log review
Are patients being screen-failed at appropriate rates? Are the screen failure reasons consistent with the pattern being investigated?
3
SAE/safety event rate comparison
If enrolled patients are sicker than documented, AE rates at this site will be elevated relative to program. Compare.
4
Targeted on-site audit if earlier steps support hypothesis
Only after remote investigation supports the signal. Due process for the site preserved. Signal is hypothesis; investigation establishes finding.
When waivers indicate the criterion itself needs amendment
The signal: multiple sites requesting same waiver
11 waiver requests for the same criterion across 7 sites in 8 weeks is not 11 separate case-by-case questions. It is a structural mismatch between the protocol criterion and clinical reality. The correct response is a formal protocol amendment, not 11 case-by-case approvals.
Amendment vs pattern waiver — the critical distinction
Pattern waiver (WRONG)
11 individual protocol deviations. No regulatory review. No documented scientific rationale. Creates precedent for future requests. Inspection finding.
Protocol amendment (RIGHT)
Single change to protocol. Scientific rationale documented. IRB/EC and agency reviewed. Binding on all sites going forward. Transparent record.
Amendment decision criteria
  • ≥3 waiver requests for the same criterion from different sites within 4 weeks
  • Scientific rationale supports extending or modifying the criterion
  • Modification does not compromise safety or data integrity
  • Modification is consistent with intended label population
Amendment process
  • Draft amendment text with specific change and rationale
  • Cross-functional review (Clinical, Statistics, Regulatory, Pharmacovigilance)
  • Regulatory submission (FDA/EMA) with justification
  • IRB/EC submission at all sites
  • Site training on amended criterion
  • Prior waiver requests reconsidered under amended criterion
  • Amendment applied prospectively from IRB/EC approval date
Key principle: The MM's structural authority is not to grant waivers — it is to propose protocol amendments when the protocol needs to change. This distinction is what separates the MM who manages a trial from the MM who leads a trial.
OCREA™ Tools · Phase 4 — Active Trial Conduct
Safety Monitoring Command Center
SAE triage · Signal detection · Protocol deviation tracking · DSMB preparation · Cross-site pattern recognition
6-step
SAE framework
4-move
Signal detection
Weekly
Review cadence
MM · PV
Audience
SAE Triage
Signal Detection
Causality
Deviations
DSMB Prep
Cross-Site Patterns
Individual SAE — 6-step review framework
1
Seriousness criteria verification
Does the event meet ICH E2A seriousness criteria? Death, life-threatening, hospitalization/prolongation, persistent/significant disability, congenital anomaly, or medically important. Events reported as SAE that do not meet criteria should be reclassified. Events meeting criteria but not reported as SAE are underreporting — a compliance issue.
2
Event chronology reconstruction
Build the timeline: last dose → symptom onset → workup → management → outcome. Gaps in chronology indicate documentation issues; implausible chronology (e.g., event 30 minutes after dose for a slow-onset toxicity) indicates reporting error.
3
Clinical picture assessment
Does the clinical presentation fit the reported event term? Fever + cough + hypoxia + bilateral infiltrates on CT = pneumonitis. Without infiltrates, the clinical picture is pneumonia, not pneumonitis. Mismatch between reported term and clinical picture requires reclassification.
4
Causality attribution
Apply the causality framework (see Causality tab). Temporal relationship, dose-response, dechallenge, rechallenge, alternative explanations, biological plausibility. Attribution should be explicit and defensible.
5
Regulatory reporting classification
Is this a SUSAR? Expedited reporting clock: 7 days for fatal/life-threatening SUSAR, 15 days for other SUSAR. Non-SUSAR SAEs reported per protocol in routine safety reporting. Classification determines timeline.
6
Signal evaluation
Does this event plus prior events in the trial constitute a signal? Cross-reference to Signal Detection tab. A single event may not be a signal; the Nth event of the same type may be. Document whether this event changes the signal assessment.
Daily SAE triage workflow
  • All new SAEs reviewed within 24 hours of receipt
  • Fatal/life-threatening events flagged immediately for SUSAR assessment (7-day clock)
  • Apply 6-step framework to each new SAE
  • Follow-up information requested if chronology or clinical picture is incomplete
  • Attribution documented with rationale, not checkbox
  • Signal impact assessed for each event
Critical threshold: ALT/AST >3× ULN + bilirubin >2× ULN = potential Hy's Law. Individual narrative review same day. Drug-induced liver injury is a sentinel signal that can affect the entire program, not just the individual patient.
4-Move Signal Detection Framework
Move 1 — Does the event exceed expectation?
Expectation sources: IB Reference Safety Information (background rate in prior trials), published class-effect literature, preclinical findings. Exceeding: higher frequency, higher severity, earlier onset, different population than expected.
Move 2 — Is there a pattern in the trial?
Single events are generally not signals. Multiple similar events become signals. Consider: clustering in time (events concentrated in specific cycles), clustering by site (specific sites with higher rates), clustering by patient subgroup (specific comorbidities, prior treatments, biomarker status).
Move 3 — Is there biological plausibility?
Does the drug's mechanism support the event being causally related? Known class effects (irAE for IO, ILD for specific ADCs, cardiac for certain TKIs) have built-in plausibility. Unexpected events in unrelated organ systems are lower plausibility but not dismissible — may represent novel findings.
Move 4 — What is the action?
Possible actions escalating: Enhanced monitoring of specific parameter. Protocol amendment (add monitoring, change dose modification rules, narrow eligibility). Temporary hold pending investigation. DSMB review. Safety communication to sites. IB update. Trial suspension.
Signal evaluation documentation
  • Signal identified and described specifically (event, frequency, severity, timing)
  • Expected rate documented from IB/class literature
  • Observed rate in this trial calculated
  • Comparison: observed vs expected with appropriate denominator
  • Patterns assessed (temporal, site, subgroup)
  • Biological plausibility assessed
  • Action proposed with rationale
  • Tracking plan for signal resolution
Regulatory context: Signals identified and not acted on are worse than signals identified and acted on. Regulatory inspectors look for signal documentation and action history. A signal log with clear evaluation and action trail demonstrates active safety oversight.
Causality attribution framework
Temporal relationship
Does the onset of the event align with exposure to the drug? Events within the PK half-life window or the biologically plausible onset window support causality. Events before first dose or long after discontinuation are less likely related.
Dose-response
Higher dose → more frequent or severe event supports causality. No dose-response does not rule out causality but weakens the case.
Dechallenge
Did the event resolve when drug was held or discontinued? Resolution supports causality. Persistence after discontinuation may indicate irreversible effect or non-drug etiology.
Rechallenge
Did the event recur when drug was restarted? Strongest evidence of causality. Rarely available in oncology because rechallenge is often clinically inappropriate.
Alternative explanations
Disease progression, concomitant medications, pre-existing conditions, incidental findings. Each must be considered. Absence of alternative explanation strengthens drug attribution; presence of plausible alternative weakens it.
Biological plausibility
Is the event consistent with drug mechanism or class effect? Known class effects have built-in plausibility. Unexpected events in unrelated systems require stronger other evidence.
Common attribution errors
Error 1 — Pre-existing condition confounder misapplication
Patient with fatty liver develops ALT 7× ULN on ADC trial. Attributing to "pre-existing liver disease" without documentation that the pre-existing condition explains the acute new event. Pre-existing conditions explain baseline abnormalities, not new acute events.
Error 2 — Disease progression default
Any new event in an oncology patient attributed to "disease progression." Valid for some events (cachexia, pain from known lesions) but not for events that are not typical of the patient's cancer (new pulmonary infiltrates, new cytopenias, new cardiac events).
Error 3 — Chemotherapy vs IO attribution in combination trials
Attributing GI events in IO+chemo combination exclusively to chemotherapy. Grade 2 diarrhea in IO combination requires differential diagnosis — immune-mediated colitis can present identically. Attribution affects management pathway (IO hold vs continue).
Attribution discipline: "Not related" attribution requires specific, documented, mechanistically plausible alternative explanation. Not merely the absence of certainty about causation. The default in clinical research is "at least possible" until evidence supports a stronger classification.
Protocol deviation classification during active conduct
Critical deviations — must be reported to IRB/EC per protocol
Categories:
• Eligibility: patient enrolled without meeting criteria
• Informed consent: enrolled without valid consent, or consent error
• Investigational product: wrong drug, wrong dose, missing dose modification
• Primary endpoint integrity: tumor assessment outside window, missing key assessments
• Safety monitoring: SAE not reported timely, DLT assessment missed, cardiac monitoring not performed
Non-critical deviations — tracked but not IRB-reportable individually
Minor visit window deviations (1-3 days). PRO questionnaires late. Administrative documentation errors. Subject identifier corrections. Non-critical concomitant medication documentation gaps.
Active-conduct deviation tracking
  • All reported deviations reviewed within 48 hours
  • Critical deviations reported to IRB/EC within required timeline (typically 5-10 days)
  • Corrective and preventive action (CAPA) documented for recurring deviations
  • Pattern detection across sites (same deviation at multiple sites)
  • Root cause analysis for critical deviations
  • Site-level deviation rate monitoring
Deviation pattern signals
Same deviation at multiple sites
Suggests a protocol design issue (unrealistic window, ambiguous procedure). Consider protocol clarification or amendment — not repeated site-by-site CAPA.
Single site with high deviation rate
Suggests site-specific process or training issue. CAPA with targeted retraining; monitor resolution.
Escalating critical deviation rate over time
Site quality deterioration or team turnover. Consider enhanced monitoring or PI re-training.
Eligibility deviations with prior MM waivers
Pre-enrollment waivers become post-enrollment critical deviations at database lock. See Tool 3 (Eligibility).
DSMB package preparation — core content
  • Trial status update (enrollment, data maturity, site activity)
  • Safety summary — aggregate AE/SAE rates by arm (blinded or unblinded per charter)
  • All deaths listed with narratives (on-study and off-study follow-up)
  • SUSARs listed with narratives
  • Discontinuation summary by reason
  • Signal assessment — any new signals identified since last DSMB
  • Interim efficacy summary if applicable per charter
  • Protocol deviation summary (critical deviations detailed)
  • Any proposed protocol amendments for DSMB input
DSMB meeting logistics
  • Package distributed 7-10 days before meeting
  • Independent statistician available for member questions
  • Open session agenda prepared (sponsor attendance)
  • Closed session content ready (DSMB members only, unblinded)
  • DSMB charter reviewed for meeting-specific requirements
DSMB recommendation categories
Continue as planned
No safety or efficacy concerns warranting change.
Continue with modifications
Specific protocol changes recommended — enhanced monitoring, amended eligibility, dose modification rules.
Pause enrollment pending investigation
Specific safety signal requires investigation before further enrollment.
Stop for futility
Interim analysis shows no realistic path to meeting primary endpoint.
Stop for superiority
Pre-specified superiority stopping boundary crossed.
Stop for safety
Unacceptable safety profile — risk exceeds anticipated benefit.
Cross-site pattern recognition — weekly review
Pattern type 1 — AE reporting rate variance
Site A reports AE per patient-month at 2.1; Site B reports 0.6. Both trials are the same arm, same patient population. Either Site A over-reports (unlikely in oncology) or Site B under-reports (more common). Under-reporting is a data integrity issue requiring investigation.
Pattern type 2 — Severity distribution differences
Site C reports only Grade 1-2 events for a toxicity that other sites report as Grade 3+. Suggests grading standardization issue at Site C. Could affect dose modification decisions at that site.
Pattern type 3 — SAE reporting timeliness
Site D consistently reports SAEs at hour 22-23 of the 24-hour reporting window. Timeliness is compliant but suggests possible administrative backlog. Could miss a truly urgent event if the SAE is reported late in the window but occurred early.
Pattern type 4 — Efficacy-safety disconnect
Site E shows much higher response rate than program average with much lower AE rate. Possible: Site E has a genuinely better patient population. Also possible: Site E under-reports AEs and over-reports responses (both threaten data integrity).
Investigation protocol for cross-site patterns
  • Central monitoring algorithm flags the pattern with specific data
  • MM reviews the pattern and determines investigation priority
  • Remote source document review for a sample of enrolled patients
  • Direct conversation with PI about site process and clinical judgment
  • CRA enhanced monitoring visit if indicated
  • For-cause audit if pattern persists and investigation supports concern
  • CAPA documentation regardless of investigation outcome
ICH E6(R3) alignment: The 2023 ICH E6(R3) update explicitly emphasizes central monitoring and cross-site pattern recognition as core sponsor responsibilities. This is not optional oversight — it is the regulatory expectation for risk-based quality management.

Oncology Data Review Framework

This tool is a standalone module covering Database Lock & Pre-Analysis Data Review. Day-to-day CRF data review framework, Hy's Law detection, cardiac monitoring, efficacy verification across the 13 CRF domains. Opens in a new browser tab to preserve the Hub navigation.

Open Tool →

Tables & Listings Review

This tool is a standalone module covering CSR Preparation. Medical review of statistical tables, listings, and figures (TLFs) for CSR construction — what to check, how to flag issues, sign-off framework. Opens in a new browser tab to preserve the Hub navigation.

Open Tool →

IND / NDA / BLA Submission

This tool is a standalone module covering Submission Package Integration. End-to-end submission document architecture — CTD Module 2.5 Clinical Overview, Module 2.7 Clinical Summary, ISS/ISE integration, MM sign-off framework. Opens in a new browser tab to preserve the Hub navigation.

Open Tool →
OCREA™ Tools · Phase 8 — Regulatory Review Response
IR Response & AdCom Prep Tool
FDA/EMA Information Requests · AdCom/ODAC preparation · Label negotiation · CRL response
4
IR categories
7
AdCom prep steps
MM · Reg
Audience
6-12 mo
Review period
Overview
IR Types
Response Framework
AdCom Prep
Label Negotiation
CRL Response
The post-submission review period
Timeline context
After submission, FDA review takes 6-10 months (Priority Review) to 10-12 months (Standard Review). EMA review takes 210 days of active review time. During this period, the MM is responsible for: (1) responding to Information Requests (IRs/Day 120 questions/Major Objections), (2) preparing AdCom/ODAC if convened, (3) negotiating the label, (4) responding to CRL if issued. This is the period where the clinical program can be won or lost based on documentation quality and response preparation.
The MM's role during review
Regulatory affairs leads the review process and formal communication with the agency. The MM provides the clinical substrate: data reanalysis, clinical interpretation of findings, medical rationale for proposed label language, clinical framing for AdCom presentations. Every regulatory response has a clinical core; the MM is responsible for that core.
Critical outputs during review
1
IR responses (FDA Information Requests)
FDA asks questions during review. Responses are time-boxed (often 5-15 business days). Response quality affects subsequent review.
2
AdCom/ODAC preparation
If the application is referred to advisory committee, preparation typically begins 3-4 months before the meeting. Backgrounder, briefing document, presentation, anticipated Q&A.
3
Label negotiation
FDA proposes label language; sponsor responds with clinical rationale for alternative language. Iterative process. Clinical integrity of the label is the MM's responsibility.
4
CRL response (if not approved)
If FDA issues Complete Response Letter, sponsor must address each deficiency. Response may require additional analyses, clinical studies, or data packages.
FDA Information Request categories
Category 1 — Clarification requests
Agency asks for clarification of existing data or description. Example: "Please clarify the timing of tumor assessments for subjects in Cohort 3." Response approach: Direct, specific answer with data reference. Response length typically short (1-2 pages).
Category 2 — Additional analyses requests
Agency requests analyses not included in the original submission. Example: "Please provide efficacy analysis in subjects aged ≥75 years." Response approach: Perform analysis, provide interpretation, address any emerging findings. Response may be 3-10 pages with supporting tables.
Category 3 — Data integrity concerns
Agency identifies potential inconsistency or concern about specific data. Example: "Please address the discrepancy between investigator and central reader assessments in subjects X, Y, Z." Response approach: Investigate thoroughly, provide the clinical and procedural explanation, propose corrective action if indicated. These responses are high-stakes and require extensive MM review.
Category 4 — Major Objections (EMA) / Day 120 questions
EMA specifically issues Major Objections (MOs) that are considered a potential ground for refusal. Response is typically due in 60-90 days and requires comprehensive data and clinical reanalysis. These responses can involve multiple rounds and may affect approval outcome. MO categories commonly include: efficacy in specific subgroups, safety profile adequacy, pharmacovigilance plan, population applicability.
IR response timing expectations
Standard clarification
5-10 business days
Additional analysis
10-20 business days
Data integrity
15-30 days (depending on complexity)
EMA Major Objection
60-90 days (LoOI cycle)
Advisory committee prep
60-120 days from notification
Operational reality: IR responses are time-pressured. The sponsor team working on IRs often works weekends and evenings. A pre-submission plan for IR response capacity is essential — identify who on the MM team will be available, what priorities take precedence, and how response quality is maintained under time pressure.
IR response framework — MM contribution
1
Understand the question precisely
Read the IR carefully. Identify what the agency is actually asking — not what you think they're asking. Agency questions are typically precise; responding to a related-but-different question signals miscommunication.
2
Identify what analysis or data answers it
Exact data source, analysis population, endpoint definitions, timeframe. If the answer requires new analysis, specify the analytic approach before running it (pre-specification protects credibility).
3
Perform the analysis / gather the data
Work with biostatistics. Ensure the analysis follows the methodology that produced the original submission results — not ad hoc. If methodology differs, explain why.
4
Interpret the finding clinically
The MM's specific contribution. Raw data are not the answer — the clinical interpretation is. Frame the finding with context: what does it mean for the benefit-risk, what does it change (or not change) in the overall submission.
5
Draft response with clinical core
Response structure: restate the question, provide the data/analysis, provide clinical interpretation, conclude with impact on the submission. Clinical interpretation is the MM's section; it cannot be delegated to regulatory affairs.
6
Cross-functional review
Regulatory, biostatistics, safety, legal review of response. Ensure consistency with prior submissions and with label negotiation positions.
7
MM sign-off
MM personally signs off on clinical content before submission. Regulatory handles submission logistics.
Response quality checklist
  • Question restated accurately at the beginning
  • All relevant data provided (not selectively)
  • Unfavorable findings acknowledged explicitly, not minimized
  • Clinical interpretation is specific, not generic
  • Impact on benefit-risk clearly stated
  • Consistency with prior submissions verified
  • Cross-references to specific CSR / CTD sections provided
  • Response length proportional to question complexity (not padded)
Writing principle: Agency reviewers read hundreds of IR responses. A response that directly answers the question with clear data and interpretation is valued. A response that hedges, provides incomplete data, or shifts the question is penalized — not just for this IR but for subsequent IRs in the same application.
When AdCom/ODAC is convened
Typical triggers for ODAC referral
Novel mechanism of action with uncertain benefit-risk. Accelerated approval with confirmatory trial concerns. Significant safety profile. First approval in a new indication. Controversial efficacy data (e.g., single-arm trials, subgroup-driven analyses). Advisory committee provides external expert input; FDA is not bound by committee vote but takes it into serious consideration.
AdCom preparation — 7-step timeline
1
T-120 days: AdCom confirmed, team assembled
Identify sponsor presenters (typically CMO/VP Medical + MM + biostatistics). Engage outside KOLs. Legal counsel review of sponsor strategy.
2
T-90 days: Briefing document drafting begins
Sponsor briefing document typically 60-200 pages. MM authors the clinical sections: benefit-risk narrative, safety detailed analysis, subgroup analyses, response to anticipated FDA concerns.
3
T-60 days: Mock AdCom / rehearsals begin
External consultants play committee role. Sponsor presents; consultants ask questions. Identify gaps in data, preparation, or communication.
4
T-45 days: Briefing document submitted to FDA
Sponsor briefing is published on FDA website typically 2 business days before the meeting. The briefing document becomes the scientific record of the sponsor's position.
5
T-30 days: FDA briefing document published
FDA's independent clinical review is public. Sponsor team reviews for differences in interpretation and prepares responses. FDA Q&A for the committee is often indicative of committee voting questions.
6
T-14 days: Final preparation
Rehearsals with real timing. Backup slides for anticipated questions. Committee member backgrounds reviewed. KOL alignment confirmed.
7
AdCom day: Execution
Sponsor presents; FDA presents; open public hearing; committee discussion and vote. Sponsor questions answered concisely and accurately. Do not overstate; do not evade.
MM contributions to AdCom success
  • Clinical rationale for every data point in the briefing document
  • Anticipated Q&A prepared for every plausible committee question
  • Fatal events addressed directly with specific clinical context
  • Subgroup analyses characterized (signal vs noise, pre-specified vs post-hoc)
  • Comparison to standard of care specific and quantitative
  • Benefit-risk framing tested in mock AdCom
  • KOL alignment confirmed on public hearing testimony
Historical context: Recent ODAC votes against AA have cited inadequate confirmatory trial progress (Sotorasib 10-2 against Oct 2023), non-US enrollment concerns (STARGLO/tislelizumab, Oct 2023), and OS detriment signals (melanoma combinations, 2023). These patterns suggest ODAC committees are attentive to specific themes. MM preparation should address them directly.
Label negotiation principles
What the label can and cannot say
The label must reflect the data. Claims must be supported by adequate and well-controlled studies. Dose and administration must match what was studied. Safety information must be complete. Contraindications and warnings must be clinically justified. The label is a legal document; language that cannot be supported by data will not be accepted by FDA.
Label sections and MM involvement
Indication & Usage (1)
MM primary — ensures the indication language matches the studied population and trial design.
Dosage & Administration (2)
MM + clinical pharmacology — dose, schedule, modifications, administration details.
Contraindications (4)
MM — based on absolute contraindications from trial data or class effect.
Warnings & Precautions (5)
MM primary — most scrutinized section. Every warning reflects specific clinical findings. Language must be both accurate and clinically actionable.
Adverse Reactions (6)
MM + PV — trial safety data presentation. Rates, categories, severity.
Drug Interactions (7)
Clinical pharmacology + MM review.
Use in Specific Populations (8)
MM — pregnancy, lactation, pediatric, geriatric, renal/hepatic. Reflects trial data and extrapolation limits.
Clinical Studies (14)
MM + biostatistics — pivotal trial results for the label indication. Primary and key secondary endpoints with data.
Common label negotiation tensions
FDA proposes narrower indication than sponsor requests
MM response: Provide data supporting broader indication. Pre-specified subgroup consistency, biomarker-agnostic activity, real-world population overlap. If data do not support broader, negotiation shifts to PMR/PMC commitments to expand indication post-approval.
FDA adds boxed warning sponsor did not propose
MM response: Assess whether the warning reflects the data accurately. Engage directly on specific language. Boxed warnings are negotiable on language even when the warning itself is required. Specific language affects clinical uptake and medical understanding.
FDA requires REMS the sponsor believes is not needed
MM response: REMS negotiation involves the specific REMS elements: medication guide only, communication plan, REMS with ETASU (elements to assure safe use). Each level has operational and commercial implications. MM argues for the minimum REMS consistent with safety, supported by risk analysis.
Complete Response Letter response framework
What a CRL means
FDA has determined the application cannot be approved in its current form. The CRL lists specific deficiencies. The sponsor must address each deficiency and resubmit. CRL response is typically 6-12 months of work. Second CRL after resubmission is possible but significantly reduces the probability of eventual approval.
CRL deficiency categories
Efficacy deficiency
FDA does not accept the evidence of effectiveness. May require additional clinical trial, reanalysis of existing data, or narrower indication. Most serious category.
Safety deficiency
Safety profile not acceptable for the proposed indication. May require additional safety data, enhanced RMP, or dose modification.
CMC deficiency
Chemistry, manufacturing, controls issue. Often addressable through additional manufacturing data or process validation.
Clinical pharmacology deficiency
PK/PD characterization inadequate, or dose rationale questioned. May require additional PK studies.
Labeling deficiency
Agency and sponsor did not reach agreement on label. May be resolvable through renegotiation without additional data.
CRL response strategy
1
Comprehensive deficiency analysis
Each deficiency broken down into what the agency is asking, what data address it, what new analysis or data are needed.
2
Type A meeting request
Sponsor can request a Type A meeting to discuss CRL deficiencies and alignment on the response path. Highly recommended for clinical deficiencies.
3
Response plan development
Detailed plan with deliverables, timelines, and leadership accountability. This is typically a 6-18 month program of work.
4
Additional clinical data generation if needed
New studies, confirmatory trials, bridging analyses, real-world evidence.
5
Resubmission preparation
Class 1 (minor) or Class 2 (major) resubmission. Class 2 triggers new 6-month review clock.
MM role in CRL response: The MM owns the clinical response to clinical deficiencies. For each clinical deficiency, the MM leads: clinical data analysis, interpretation, response framing. The MM participates in Type A meetings with FDA. The MM signs off on clinical content of the resubmission. This is a senior-level responsibility that typically occupies the MM full-time during the response period.
OCREA™ Tools · Phase 9 — Post-Approval Lifecycle
PMR/PMC Lifecycle Tracker
Post-marketing commitments · PSUR · REMS · Label expansion · Confirmatory trials · Withdrawal risk management
PMR · PMC
Commitments
PSUR
Periodic reporting
REMS
Risk mitigation
MM · PV
Audience
Overview
PMR / PMC
Confirmatory Trials
PSUR / PBRER
REMS
Label Expansion
Post-approval is not the end — it is a new phase of work
What happens after approval
Approval is the midpoint, not the endpoint. Post-approval obligations include: Post-Marketing Requirements (PMRs, legally binding), Post-Marketing Commitments (PMCs, non-binding but tracked), Periodic Safety Update Reports (PSUR/PBRER), confirmatory trials for Accelerated Approval, REMS compliance if applicable, real-world evidence generation, label expansion programs, and monitoring for withdrawal risk if confirmatory data are unfavorable.
The MM's role changes but does not end
The MM's intensive trial-conduct phase transitions to a lifecycle management phase. The MM remains responsible for: clinical integrity of periodic safety reports, clinical rationale for PMR responses, confirmatory trial oversight, label expansion clinical strategy, REMS effectiveness monitoring, and withdrawal-risk decision-making if confirmatory trials fail.
Core lifecycle obligations
1
PMR / PMC completion
PMRs are legally required; failure to complete can result in loss of approval. PMCs are committed but not legally required. Both are tracked by FDA throughout product lifecycle.
2
Confirmatory trials (if AA)
Accelerated Approval requires confirmatory trials. Post-FDORA (Dec 2022), confirmatory trials must be "underway" at time of AA and must be diligently pursued.
3
Periodic safety reporting
PSUR/PBRER every 6 months for first 2 years, then annually. Format per ICH E2C(R2). Report integrates all new safety information globally.
4
REMS compliance
If approved with REMS, ongoing compliance with all REMS elements. Periodic REMS assessments per REMS-specified schedule.
5
Label expansion
New indications, population expansions, dose additions. Each requires supplemental submission with supporting clinical data.
6
Withdrawal risk management
If confirmatory trial fails to verify benefit, sponsor must decide: voluntary withdrawal, negotiated label narrowing, or ODAC referral for FDA decision on continued approval.
PMR vs PMC distinction
PMR — Post-Marketing Requirement
Legally required under FDAAA authority. Failure to complete can result in label change, market withdrawal, or civil penalties. Typical triggers: accelerated approval confirmatory trial, specific pediatric study, specific safety study.
PMC — Post-Marketing Commitment
Committed by sponsor but not legally required. Tracked by FDA. Failure is noted but does not automatically trigger regulatory action. Often covers exploratory analyses, population-specific studies, or specific formulations.
PMR tracking requirements
  • All PMRs documented with specific deliverables and due dates
  • FDA 3988 or equivalent tracking form completed annually
  • Status updates submitted per PMR milestone schedule
  • Delays reported with specific cause and revised timeline
  • Final study report submitted within specified timeframe
  • FDA review of final report with acceptance or further action
Common PMR categories
Category 1 — Confirmatory trial (AA)
Phase 3 RCT to confirm clinical benefit. Required under AA. Post-FDORA: must be "underway" at time of AA. FDA Project Confirm monitors diligent pursuit.
Category 2 — Pediatric studies (PREA)
Required under Pediatric Research Equity Act unless waiver granted. Typically a pharmacokinetic study and safety/efficacy study in pediatric age groups relevant to the indication.
Category 3 — Specific safety study
Focused study to characterize a specific safety concern — typically Important Potential Risk in the RMP. May be an enhanced pharmacovigilance study, a registry, or a dedicated clinical trial.
Category 4 — PK in specific populations
PK study in hepatic impairment, renal impairment, pregnant/lactating women, or drug-drug interaction studies identified as needed but not completed at approval.
Post-FDORA consequences: Failure to diligently pursue a confirmatory trial for AA can now result in expedited withdrawal of approval. The 2023 ODAC vote against sotorasib AA (10-2) was specifically tied to concerns about the confirmatory trial progress. PMR tracking is not a back-burner activity — it is a core regulatory obligation.
Confirmatory trial obligations (Accelerated Approval)
FDORA December 2022 — changed the landscape
Confirmatory trial must be "underway" at time of AA — interpreted by FDA as enrolling at least one patient. Sponsor must demonstrate diligent pursuit. FDA has expedited withdrawal authority for confirmatory trials that fail. Project Confirm monitors AA sponsors. Sponsors who do not show diligent enrollment progress face inquiry.
Confirmatory trial tracking
  • Confirmatory trial protocol finalized and IND submitted
  • First site activated
  • First patient enrolled (meets "underway" threshold)
  • Enrollment tracking with monthly reports to FDA (if requested)
  • DSMB established and meeting per charter
  • Target enrollment completion date specified and tracked
  • LPLV date projected with updates as enrollment progresses
  • Primary endpoint maturity date projected
Confirmatory trial outcomes and consequences
Positive confirmatory
AA converts to full approval. Label updated. PMR discharged. Product continues.
Non-significant confirmatory (ambiguous)
Sponsor and FDA discuss interpretation. May require additional data or different analytic approach. Outcome uncertain.
Negative confirmatory (HR unfavorable)
Withdrawal discussion. Sponsor may: voluntarily withdraw, negotiate narrower label, or face FDA-initiated withdrawal proceeding. ODAC referral possible.
Negative with detriment
If confirmatory shows the drug is worse than control (OS detriment), withdrawal is typically inevitable and accelerated.
MM role during confirmatory trial
Owning the confirmatory trial clinical integrity
The confirmatory trial is a Phase 3 RCT with full MM responsibilities. But the stakes are different: unlike an initial NDA where a failed Phase 3 results in non-approval, a failed confirmatory results in withdrawal of an approved product — affecting patients who have come to rely on it. The MM's clinical integrity during confirmatory trial conduct is critical.
PSUR / PBRER framework (ICH E2C(R2))
What is PSUR / PBRER
Periodic Safety Update Report / Periodic Benefit-Risk Evaluation Report. Integrates all new safety data globally in a specified time period (typically 6-monthly for first 2 years, then annually). Standardized format per ICH E2C(R2). Submitted to all relevant regulatory agencies.
PSUR content structure
  • Worldwide marketing authorization status
  • Actions taken for safety reasons (label changes, recalls, etc.)
  • Changes to reference safety information (IB, Company Core Data Sheet)
  • Estimated exposure (patient-years)
  • Data in summary tabulations (serious AEs, non-serious AEs by MedDRA)
  • Significant findings from clinical trials during the reporting period
  • Non-clinical findings
  • Literature findings
  • Other periodic reports (5-year PSUR if applicable)
  • Lack of efficacy in controlled clinical trials
  • Late-breaking information
  • Overall safety evaluation
  • Integrated benefit-risk analysis
  • Conclusions and actions
MM contribution to PSUR
  • Clinical interpretation of aggregate safety data
  • Signal assessment — new signals identified in reporting period
  • Benefit-risk reassessment with new data
  • Proposed label changes if safety signal requires
  • Integration with RMP updates (new Important Identified or Potential Risks)
PSUR as strategic document: PSURs are public to regulatory agencies across all markets. A well-written PSUR with clear benefit-risk analysis and proactive signal identification supports continued confidence in the product. A PSUR that misses a signal FDA identifies independently damages the sponsor-agency relationship.
REMS hierarchy — from least to most burdensome
Medication Guide only
Standard patient-directed information provided with each prescription. Least burdensome. Most common for REMS-required products with manageable risks.
Communication plan
Dear Healthcare Provider letters, targeted communications to specific specialties. Often combined with Medication Guide.
REMS with ETASU
Elements to Assure Safe Use. Prescriber certification, pharmacy certification, patient enrollment in REMS program, monitoring requirements, dispensing restrictions. Most burdensome. Reserved for products with specific risks requiring active mitigation.
REMS compliance ongoing obligations
  • REMS elements implemented as approved
  • Compliance metrics tracked per REMS specification
  • Periodic REMS assessments submitted per schedule (typically 18, 36, 72 months)
  • REMS modifications submitted as supplements if indicated
  • REMS effectiveness evaluated against pre-specified objectives
REMS assessment — MM role
Evaluating REMS effectiveness
REMS assessments evaluate whether the REMS is achieving its goals. MM contribution: clinical evaluation of safety outcomes in the real-world population. Is the risk being mitigated? Are the REMS elements creating patient access barriers? Does the evidence support REMS modification (de-escalation or escalation)?
REMS de-escalation considerations
Multiple years of favorable real-world safety data
May support elimination of ETASU while retaining Medication Guide
Healthcare provider knowledge established
May support elimination of prescriber certification requirement
Patient registry data showing no unexpected signals
May support elimination of patient enrollment requirement
REMS creating disproportionate access barrier
Supports simplification — access considerations are part of benefit-risk
Label expansion pathways
New indication
Different disease or different line of therapy. Requires supplemental NDA with supporting clinical data — typically a new pivotal trial in the new indication. Example: drug approved for 2L NSCLC expanding to 1L NSCLC.
Population expansion within existing indication
Adding pediatric, geriatric, or specific subgroup to an existing adult indication. May require supporting PK and efficacy/safety data in the new population.
Combination expansion
Adding a new combination partner or regimen. Requires specific trial data for the combination. Combination safety must be characterized separately.
Dose or schedule modification
New dose, different schedule, different route. Requires data supporting the modification's efficacy and safety.
Tissue-agnostic / biomarker-defined expansion
Expanding from histology-specific to biomarker-defined population. Requires evidence of activity across tumor types with the defining biomarker. Precedents: larotrectinib NTRK, pembrolizumab MSI-H, pembrolizumab TMB-H.
Expansion clinical strategy
  • Clinical rationale for expansion (unmet need, mechanism, prior data)
  • Pre-IND/pre-sNDA meeting with FDA to align on trial design
  • Pivotal trial designed to support the specific expansion
  • Parallel development of any required PMCs
  • Integrated safety database updated to include expansion population
  • Supplemental submission with complete CTD
Strategic consideration: Label expansion is how oncology drugs maximize value over their patent life. A drug that approves in one indication and expands to 3-4 indications over 5-7 years typically generates substantially more revenue and benefits many more patients. The MM's role in label expansion is to identify feasible expansions early and drive the clinical program that enables them.
OCREA™ · Oncology Clinical Research Excellence Academy · Enterprise Capability Platform
© 2026 · All Rights Reserved · Proprietary & Confidential · 17 U.S.C. § 504 · Trade Secret Protection Applies
← Return to OCREA Landing