Assess whether a CMO finding is a delay or a refuse-to-file risk (51b40a)

Situation

In a 505(b)(2) program relying on literature plus a bridging study, 505(b)(2) literature-to-product bridge table is the only Pharmacovigilance extract after a CMO 483 that maps to the NDA CMC module that clinical-development physician can use for a CMO finding is. Clinical-development physician has to pick A CMO finding is a delay or A refuse-to-file risk for this Pharma & Life Sciences Pharmacovigilance close using 505(b)(2) literature-to-product bridge table.

Decision

Clinical-development physician in a 505(b)(2) program relying on literature plus a bridging study must choose A CMO finding is a delay / A refuse-to-file risk using 505(b)(2) literature-to-product bridge table after a CMO 483 that maps to the NDA CMC module.

Hypotheses to test

• The population in 505(b)(2) literature-to-product bridge table is the one a CMO 483 that maps to the NDA CMC module named, so A CMO finding is a delay follows for this Pharmacovigilance file.
• The population in 505(b)(2) literature-to-product bridge table is adjacent only to a CMO 483 that maps to the NDA CMC module; A refuse-to-file risk is the honest Pharma & Life Sciences call.
• A 505(b)(2) program relying on literature plus a bridging study already contained a CMO 483 that maps to the NDA CMC module before 505(b)(2) literature-to-product bridge table arrived; no new Pharmacovigilance path.
• Provenance on 505(b)(2) literature-to-product bridge table after a CMO 483 that maps to the NDA CMC module is broken; do not pick A CMO finding is a delay or A refuse-to-file risk yet.

Analysis required

• Test a protocol deviation versus a safety signal versus a filing gap on a CMO finding is.
• Check whether 505(b)(2) literature-to-product bridge table supports the labeled claim clinical-development physician would keep.
• Map FDA-response timing and owner in a 505(b)(2) program relying on literature plus a bridging study.
• For this Pharma & Life Sciences Pharmacovigilance file, read 505(b)(2) literature-to-product bridge table against a CMO 483 that maps to the NDA CMC module and write the one fact that would move a CMO finding is for clinical-development physician.

Recommendation

Choose A CMO finding is a delay / A refuse-to-file risk on this Pharma & Life Sciences / Pharmacovigilance packet (505(b)(2) literature-to-product bridge table after a CMO 483 that maps to the NDA CMC module). Lead with the Pharma & Life Sciences option 505(b)(2) literature-to-product bridge table can support after a CMO 483 that maps to the NDA CMC module, then the two facts that force it, then the Monday action for clinical-development physician in a 505(b)(2) program relying on literature plus a bridging study.