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

SITUATION A rare-disease team designing a pediatric plan cannot treat a CMO 483 that maps to the NDA CMC module as incidental context on CMC comparability package for a site change. 505(b)(2) development lead must close to drop a secondary from that extract under Pharma & Life Sciences / FDA Response and Labeling.

DECISION 505(b)(2) development lead in a rare-disease team designing a pediatric plan must choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold using CMC comparability package for a site change after a CMO 483 that maps to the NDA CMC module.

HYPOTHESES TO TEST 1. 505(b)(2) development lead can defend Proceed under protocol from CMC comparability package for a site change after a CMO 483 that maps to the NDA CMC module in a Pharma & Life Sciences challenge. 2. 505(b)(2) development lead cannot defend Proceed under protocol from CMC comparability package for a site change; Pause the pathway is what the extract actually supports after a CMO 483 that maps to the NDA CMC module. 3. A CMO 483 that maps to the NDA CMC module never reached the population in CMC comparability package for a site change — reopen intake, do not close to drop a secondary. 4. Two facts in CMC comparability package for a site change after a CMO 483 that maps to the NDA CMC module conflict for 505(b)(2) development lead; hold this FDA Response and Labeling file.

ANALYSIS REQUIRED 1. Trace CMC, labeling, or pharmacovigilance facts in CMC comparability package for a site change after a CMO 483 that maps to the NDA CMC module. 2. Separate an isolated adverse event from a systemic quality issue. 3. Test a protocol deviation versus a safety signal versus a filing gap on to drop a secondary. 4. For this Pharma & Life Sciences FDA Response and Labeling file, read CMC comparability package for a site change against a CMO 483 that maps to the NDA CMC module 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 / FDA Response and Labeling packet (CMC comparability package for a site change after a CMO 483 that maps to the NDA CMC module). If CMC comparability package for a site change cannot force a Pharma & Life Sciences label under FDA Response and Labeling, stop. Do not invent missing evidence a rare-disease team designing a pediatric plan does not have.

COMMAND RETURNS - Bottom-line Pharma & Life Sciences option on to drop a secondary, then the evidence in CMC comparability package for a site change, then the action for 505(b)(2) development lead - Hypothesis scorecard against CMC comparability package for a site change: supported / rejected / untestable - FDA Response and Labeling finding in CMC comparability package for a site change that a second reviewer can re-perform - Missing page in CMC comparability package for a site change after a CMO 483 that maps to the NDA CMC module, if any