News Focus
News Focus
icon url

underpar71

11/22/25 10:36 AM

#799290 RE: flipper44 #799289

That would be a material event, IMO and need to be disclosed
icon url

dennisdave

11/22/25 10:45 AM

#799292 RE: flipper44 #799289

WRONG.

MHRA requires that the intended commercial manufacturing process be assessed before granting a marketing authorisation for an ATMP.

Direct quote from MHRA’s own GMP inspectorate: “The MHRA require you to fully demonstrate your ability to consistently and correctly manufacture your ATMP in order to obtain an authorisation.”

If Flaskworks/Grade C is the commercial route (NWBO explicitly stated it is “central to large scale-up”), then that is the process that must be validated, inspected and reviewed as part of the MAA. Manual Grade B is pilot-scale, not the commercial plan and that is NWBO’s own wording, not mine. Im asthonised you and the lot of you refuse to accept the last NWBO PR in that regard.

You cannot submit an MAA with Process A (manual) and commercially supply Process B (Flaskworks). MHRA inspects and approves the process that will actually be used. If the commercial route changes during review, the dossier must be updated and the review will pause until the new CMC is assessed. MHRA explicitly classifies this as a sponsor-side clock-stop. Flaskworks is not a Type II variation. A Type II variation is only allowed when the originally approved process remains commercially viable. Manual is not. NWBO said it themselves: Flaskworks/Grade C is required for scalable commercial production. That makes the automation pathway part of the active MAA, not a post-approval convenience update.

ATMP law is clear:
A major manufacturing-platform change (manual ? automated closed system) must be included in the MAA assessment.
Not after approval.
Not “later.”
Not optional.

But hey whatever makes you sleep better at night
icon url

sentiment_stocks

11/22/25 10:58 AM

#799295 RE: flipper44 #799289

Right…Flaskworks and the C Suites aren’t “central” to an MAA approval, but they are “central” to a transition from the B suites to the C suites to enable “large scale-up production” AFTER an approval.

And as you point out, that’s been the “long-term plan all along.”

From the recent PR:

The Company views use of the
Flaskworks closed system as key to enabling DCVax-L production to begin taking place in Grade C suites rather than Grade B suites – and the Company views such transition to Grade C suites as central to large scale-up of production.



The B suites should be able to handle the initial volume of patient treatments in the first year coming from the UK, while the C suites and the Flaskworks units are under development and validation. Meanwhile, the company would also be submitting their DCVax-L applications to the other regulators (Canada, US, EU) while this scale-up preparation was underway.

That’s been the long-term plan for the past several years, so I don’t understand why dennisdave is suddenly arguing there’s an entirely different pathway now upon the company’s announcement that they’re moving ahead with the plan they’ve intended all along?