Assess whether to drop a secondary endpoint that will dominate the AdCom

SITUATION 505(b)(2) development lead is responsible for to drop a secondary in a safety team sitting on a new disproportionate signal, using phase-3 protocol with endpoint-sensitivity issues as the only working extract. An inspector asking for batch records you cannot produce this week is what reset the timeline for this Pharma & Life Sciences Pharmacovigilance file.

DECISION 505(b)(2) development lead in a safety team sitting on a new disproportionate signal must choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold using phase-3 protocol with endpoint-sensitivity issues after an inspector asking for batch records you cannot produce this week.

HYPOTHESES TO TEST 1. Authorize Proceed under protocol now; phase-3 protocol with endpoint-sensitivity issues already has the discriminator after an inspector asking for batch records you cannot produce this week. 2. Keep Pause the pathway in force until phase-3 protocol with endpoint-sensitivity issues is completed after an inspector asking for batch records you cannot produce this week for 505(b)(2) development lead. 3. Treat phase-3 protocol with endpoint-sensitivity issues as Escalate safety review because both readings appear after an inspector asking for batch records you cannot produce this week. 4. Refuse a Pharma & Life Sciences close: 505(b)(2) development lead does not have the decision to drop a secondary turns on in phase-3 protocol with endpoint-sensitivity issues.

ANALYSIS REQUIRED 1. Test a protocol deviation versus a safety signal versus a filing gap on to drop a secondary. 2. Check whether phase-3 protocol with endpoint-sensitivity issues supports the labeled claim 505(b)(2) development lead would keep. 3. Map FDA-response timing and owner in a safety team sitting on a new disproportionate signal. 4. For this Pharma & Life Sciences Pharmacovigilance file, read phase-3 protocol with endpoint-sensitivity issues against an inspector asking for batch records you cannot produce this week and write the one fact that would move to drop a secondary for 505(b)(2) development lead.

RECOMMENDATION Choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold on this Pharma & Life Sciences / Pharmacovigilance packet (phase-3 protocol with endpoint-sensitivity issues after an inspector asking for batch records you cannot produce this week). The follow-on Pharmacovigilance action is what 505(b)(2) development lead does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Pharma & Life Sciences option on to drop a secondary, then the evidence in phase-3 protocol with endpoint-sensitivity issues, then the action for 505(b)(2) development lead - Hypothesis scorecard against phase-3 protocol with endpoint-sensitivity issues: supported / rejected / untestable - Named option among Proceed under protocol, Pause the pathway, Escalate safety review and the fact that kills the others - Owner and next date for 505(b)(2) development lead in a safety team sitting on a new disproportionate signal