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

SITUATION After a payer demanding RWE the protocol cannot generate, RWE protocol that may not meet regulator expectations is what 505(b)(2) development lead can touch in a labeling team facing a boxed-warning debate. Pharma & Life Sciences will live with Proceed under protocol versus Pause the pathway on this CMC and Development Pathways file.

DECISION 505(b)(2) development lead in a labeling team facing a boxed-warning debate must choose Proceed under protocol / Pause the pathway / Escalate safety review / Hold using RWE protocol that may not meet regulator expectations after a payer demanding RWE the protocol cannot generate.

HYPOTHESES TO TEST 1. 505(b)(2) development lead can defend Proceed under protocol from RWE protocol that may not meet regulator expectations after a payer demanding RWE the protocol cannot generate in a Pharma & Life Sciences challenge. 2. 505(b)(2) development lead cannot defend Proceed under protocol from RWE protocol that may not meet regulator expectations; Pause the pathway is what the extract actually supports after a payer demanding RWE the protocol cannot generate. 3. A payer demanding RWE the protocol cannot generate never reached the population in RWE protocol that may not meet regulator expectations — reopen intake, do not close to drop a secondary. 4. Two facts in RWE protocol that may not meet regulator expectations after a payer demanding RWE the protocol cannot generate conflict for 505(b)(2) development lead; hold this CMC and Development Pathways file.

ANALYSIS REQUIRED 1. Check whether RWE protocol that may not meet regulator expectations supports the labeled claim 505(b)(2) development lead would keep. 2. Map FDA-response timing and owner in a labeling team facing a boxed-warning debate. 3. Trace CMC, labeling, or pharmacovigilance facts in RWE protocol that may not meet regulator expectations after a payer demanding RWE the protocol cannot generate. 4. For this Pharma & Life Sciences CMC and Development Pathways file, read RWE protocol that may not meet regulator expectations against a payer demanding RWE the protocol cannot generate 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 / CMC and Development Pathways packet (RWE protocol that may not meet regulator expectations after a payer demanding RWE the protocol cannot generate). Lead with the Pharma & Life Sciences option RWE protocol that may not meet regulator expectations can support after a payer demanding RWE the protocol cannot generate, then the two facts that force it, then the Monday action for 505(b)(2) development lead in a labeling team facing a boxed-warning debate.