Jesster64, I want to thank you for laying out your thoughts in such a constructive and reasoned way. You are asking the right questions and connecting key points that many are still trying to sort out. Much of what you have said is directionally correct, and I would like to walk through it carefully. Not to counter your logic but to help structure what you are already sensing. The regulatory and manufacturing layers here are intricate, but they are beginning to form a clear pattern.
Let us begin with the idea that the original submission to the MHRA has evolved. That is more than plausible, it is likely. Full credit goes to SeekingAnswers for highlighting the importance of what is known as a variation. In the UK system, a variation is a formal amendment submitted during an active Marketing Authorisation Application. It allows a sponsor to update elements such as the manufacturing method, the formulation, or technical documentation. The key point is this: a variation can only be submitted if the application is still under review. So if NWBO submitted one, perhaps to include Flaskworks or to reflect other manufacturing changes, that confirms the application is alive and actively progressing through the regulatory system.
Now regarding Flaskworks, this is the piece that often gets misunderstood. Some still think of Flaskworks as a post approval upgrade or a secondary tool to reduce costs after launch. But in advanced cell therapies, particularly autologous therapies like DCVax, that kind of separation is not possible. In this category of medicine, the manufacturing method is the therapy. It is not simply a production step, it defines the therapeutic identity. The specific way in which the dendritic cells are harvested, cultured, loaded with tumor lysate, matured through cytokine exposure, and reinfused into the patient is what gives the product its clinical effect. This is known in regulatory science as the product equals process principle.
So if Flaskworks is included in the current submission, it is not a peripheral addition. It becomes part of the product itself. The MHRA would need to evaluate Flaskworks not just as a manufacturing device but as a complete system capable of replicating the final clinical product validated in the Phase 3 trial. That includes demonstrating that Flaskworks can produce dendritic cells that match Advent’s output in potency, antigen presentation, viability, sterility, cytokine expression, and overall therapeutic profile.
This is not speculative. In its regulatory filings, NWBO has stated that the Flaskworks system is designed to replicate the DCVax manufacturing process and provide a closed, automated, scalable version of the same validated clinical method. The company has also made it clear that Flaskworks commercialization depends on approval of the DCVax product, since it is not a different therapy, it is a platform that recreates the same one using automation.
In the meantime, commercial production would most likely begin at Advent Bioservices. This is the facility used during the Phase 3 trial and the one originally named in the Marketing Authorisation Application. Advent can produce DCVax in the same artisanal fashion as before, allowing the company to fulfill initial orders using the already approved infrastructure. But Advent alone cannot scale to meet future demand. That is where Flaskworks becomes critical. It enables a modular and potentially distributed manufacturing model, one that can scale globally if approved.
Now this is where your point about broader patient access comes in. While the formal label under the Marketing Authorisation Application is for glioblastoma, NWBO has another legal pathway to serve patients in other indications. This is made possible by the UK’s Specials framework, which was updated in 2023 through Statutory Instrument Number 87. Under this framework, unlicensed advanced therapies can be supplied to individual patients on a named basis if a physician determines it is clinically necessary and there are no approved alternatives. This model is known operationally as the Individual Funding Request or IFR pathway.
NWBO has referenced this pathway as a way to provide treatment to patients outside the trial population. While exact numbers have not been published, the legal infrastructure is active and functional. IFR offers NWBO the flexibility to continue serving patients while formal approval is being finalized and while initial manufacturing remains centralized through Advent.
It is also important to point out that the IFR model does not change the formal label. However, it may help build the foundation for a future expansion of the approved indication. When treatments delivered under IFR are tracked through pharmacovigilance or real world outcome monitoring, they can generate supportive evidence around safety and therapeutic effect. Over time, this can help justify a variation request or a new indication filing. So while IFR does not replace the formal approval process, it operates as a strategic bridge providing access now while helping construct the clinical rationale for what comes next.
If Flaskworks is already included in the current variation, then that same variation may also serve a dual purpose. It may simultaneously authorize the manufacturing transition and quietly broaden the regulatory language to accommodate a wider range of patient types. That part will not be confirmed until the Summary of Product Characteristics is made public, but the logic and regulatory precedent support it.
So what is likely unfolding is the following sequence
First, NWBO submitted its Marketing Authorisation Application for glioblastoma using the manufacturing method validated at AdventSecond, the company likely submitted a variation to include Flaskworks and possibly other updatesThird, validation testing for Flaskworks has already been completed, showing equivalence to AdventFourth, initial production will begin at Advent using the same artisanal model as the clinical trialFifth, Flaskworks will be commercialized only if approved as part of the product, either now or through a follow up variationSixth, the IFR and Specials model allows NWBO to treat patients beyond glioblastoma through legal physician named accessSeventh, treatment under IFR may generate the real world data necessary for eventual label expansion
In this light, the current silence is not a red flag. It reflects the quiet but essential process of finalizing the Summary of Product Characteristics. That document is what NICE needs in order to begin cost effectiveness modeling. It is also what defines the approved label, the dosage, the manufacturing source, and the legal boundaries of use. Until it is complete, the company is not expected to speak publicly and NICE cannot act.
You were absolutely correct to recognize this as a coordinated evolution between NWBO and the regulators. Flaskworks cannot proceed without DCVax approval. DCVax cannot scale without Flaskworks. And the IFR pathway provides the legal and operational bridge to begin real world deployment while the broader commercial model falls into place.
You are thinking through this with care and your question deserves exactly that.
Market Data 
Markets 
AI
