News Focus
News Focus
Followers 43
Posts 5340
Boards Moderated 0
Alias Born 12/05/2021

Re: FeMike post# 795634

Thursday, 10/30/2025 4:30:36 PM

Thursday, October 30, 2025 4:30:36 PM

Post# of 822174

Eh, if that's true, this application should be backlogged and counting against MHRA's performance metrics. We don't see that. That pretty patently disproves this theory. I'm not saying the RFI's aren't complete, but if they are it wasn't "months" ago. Plus if you look at NWBO's own estimations of the process, the Flaskworks unit still shouldn't be ready for approval. We'll find out more on that in the 10Q in 2 weeks, but I don't think that's approvable quite yet.

I think the aspect of Eden/flaskworks manufacturing is well enough decoupled from the MAA. My estimate is they are going to approve the MAA on artisan, then over the next (few?) months, Eden manufacturing will be ready/approved, then the NICE application will be submitted for Eden and not artisan.

Actually, the MHRA backlog metric doesn’t really apply here.
Those performance stats only track standard chemical or biologic applications not complex ATMPs that involve ongoing GMP validation. ATMP reviews routinely fall outside those public “performance metrics” because those metrics measure clock days, and MHRA pauses the clock whenever the sponsor is completing regulatory tasks (like Flaskworks validation data).

So the absence of a “backlogged” entry doesn’t disprove anything, it just means this review remains active with supplementary data pending, which is completely normal for ATMPs.

On the Artisan vs Flaskworks issue:
MHRA could technically approve DCVax-L on the existing manual (Artisan) process first, but that would make little sense operationally. Flaskworks validation was initiated after the MAA submission and has been progressing in parallel under Advent’s GMP license.Once that validation data are ready, it’s far more efficient for MHRA to synchronize the two decisions the MAA for DCVax-L and the separate authorization to use Flaskworks for production rather than approve the manual process first and issue a replacement license a few months later.

The “manual production plans” mentioned in earlier filings are exactly that plans on paper, not real build-outs. They serve as regulatory insurance to keep the MAA technically valid while Flaskworks validation runs in parallel. NWBO never suggested those manual cleanrooms would actually be installed and used long-term; they’re there to satisfy MHRA’s requirement that a fallback process exists on record. The latest 10-Q confirms it:

“Building upon the design and engineering work in preceding months, the Company and Advent developed an improved design and configuration for the simplified Grade C lab. The Company and Advent also negotiated the construction arrangements and undertook preparations to enable construction to begin in the third quarter.”

That reads like paper planning, not physical construction essentially the regulatory equivalent of a “children’s trial” to keep MHRA comfortable that a validated manual option exists, even though Flaskworks will replace it.

NWBO’s 10-K ties it all together:

“Production of the GMP-grade units will be timed to coincide with the timing for build-out of Grade C labs in the Sawston facility. When the GMP-grade units are delivered, Advent BioServices will undertake qualification and validation of those units, conduct engineering runs and collect data, and apply to regulators for approval to use the system to produce DCVax-L for patients.”

That’s exactly what you’d expect if MHRA and NWBO are coordinating a single decision covering both DCVax-L and the new Flaskworks manufacturing platform. If the next 10-Q shows that GMP units are now being qualified or validation runs are underway, it would fit perfectly with an integrated approval timeline not two separate sign-offs.

Just my two cents
Volume:
Day Range:
Bid:
Ask:
Last Trade Time:
Total Trades:
  • 1D
  • 1M
  • 3M
  • 6M
  • 1Y
  • 5Y
Recent NWBO News