
autologous assassin 🇺🇸🇨🇦🇺🇦🇮🇱
6.1K posts

autologous assassin 🇺🇸🇨🇦🇺🇦🇮🇱
@flaskworks
Retail $NWBO shareholder. Posts my own opinion. Make your own decisions. Not legal, investment, medical, or economic advice.














Lykiri's interpretation of $NWBO and Flaskworks is incorrect and built on a misreading of EMA commercial manufacturing rules that don’t apply to NWBO’s case for three reasons: 1. He’s Quoting EMA Centralized Procedure Rules—Not MHRA’s ATMP Pathway The quote about “not permitted to add a new site or change steps of manufacture after validation” applies to non-ATMP central submissions to EMA—not to the MHRA’s national MAA for an ATMP, where rolling, parallel comparability updates are explicitly allowed under: ✅️ ICH Q5E – Which governs comparability for biologics ✅️.EU GMP Annex 15 – Which permits validation runs during submission ✅️ MHRA ATMP Guidelines – Which allow inclusion of non-finalized data if comparability is demonstrated and commitments are in place NWBO clearly followed this path. 2. NWBO Confirmed Comparability Pre-Validation On Feb 6, 2024, NWBO stated that Flaskworks-produced DCVax-L met the same: ✅️ Purity ✅️ Biologic profile ✅️ Dose yield via validated release assays (language that only applies to GMP conditions). 🧠 That means Flaskworks comparability was demonstrated before the Jan 24, 2024 MAA validation cutoff—as required. And on March 7, 2024, NWBO confirmed MHRA had validated the MAA, meaning all required data was accepted. Under MHRA rules: “All required information must be included for the application to be considered valid.” If Flaskworks wasn’t included, the MAA would have been kicked back as incomplete. 3. GMP Update Confirms Flaskworks Inclusion, Not Post-Approval Variation On Feb 21, 2025, MHRA updated NWBO’s GMP certificate to include commercial-grade Flaskworks. MHRA does not update a GMP license unless: ✅️ The process was part of the MAA submission OR ✅️ A Type II variation was filed post-approval No such variation was ever disclosed or filed, meaning Flaskworks had to be already under review. This matches Linda Powers’ own ASM remarks: Flaskworks validation was happening “in parallel” with the MAA—not after it. Conclusion: EMA commercial manufacturing rules don’t apply here Flaskworks was reviewed under ATMP-specific MHRA pathways Comparability was proven before MAA validation Final validation was for scale-up, not re-proving comparability GMP license update confirms Flaskworks was included all along The theory that Flaskworks is a post-approval add-on is flat-out wrong. MHRA policy, the company’s PRs, and the updated license all point to one conclusion: 🚀 Flaskworks EDEN was part of the MAA from the start. Don’t conflate general EMA guidance with the specific rules that govern GMP process changes in ATMPs under ICH Q5E and Annex 15. investorshub.advfn.com/boards/read_ms…






#dcvax $nwbo #gbm Interesting that MHRA added the following additional comment to similar comments they made when replying to others recently:- "As a regulator, unless we have the company’s agreement, we cannot share information regarding an application. We appreciate you may be a Shareholder, but we cannot give out information without company permission" Red_Right_Hand 33 minutes ago Post #756,289 Re: #756,286: @pgsd - Did that also have the same emphasis on From muee88 on February 4th. muee88 Tuesday, February 04, 2025 Post# of 747454 Recent response from the MHRA regarding the status of the DCVax application: “We understand and support the need for treatments for glioblastomas and are actively working to ensure all medicines filed are safe, effective, and manufactured with appropriate quality standards, and subsequently reach patients as rapidly as possible. In our role we are responsible for licensing medicines and ensuring that both medicines and medical devices work and are acceptably safe. As you have already seen, the company has announced that they have submitted their application to us. We are working actively on this application, recognising the impact this medicine could potentially have. [insert a bunch of link for contacting NWBO] Finally, please be assured we a progressing this application as rapidly as possible and in collaboration with the company.” investorshub.advfn.com/boards/read_ms… x.com/peter_brit/sta…









Some investors misunderstood $NWBO Feb 6, 2024 PR. The “engineering runs” on GMP-grade Flaskworks units are for commercial deployment not regulatory comparability. Comparability was already completed using functionally equivalent prototype units. Adjusting size of unit, fit, power supply, color, buttons, etc for mass production does not invalidate comparability assays. Per ICH Q5E, regulators require: 🎯 Same purity, identity, biologic profile, & yield 🎯 Validated release assays under GMP-compliant conditions 🎯 No new clinical data if assays are comprehensive If that data was submitted before MHRA validated the MAA (Jan 24, 2024) then Flaskworks was already under review when units for mass production were ordered then later proven to be at GMP standards. Subsequent engineering runs are standard IQ/OQ/PQ steps to ensure the final GMP units work as expected but they are not for redoing comparability. So they do not need to be completed before Flaskworks data was included in MAA. They are a final validation step prior to GMP approval. These engineering runs ensure: 🔥 IQ – Installed correctly 🔥 OQ – Operates as intended 🔥 PQ – Performs the process consistently with real materials In short: ✅ Comparability already accepted ✅ Validation runs were for scale-up ✅ Approval isn’t waiting on hardware ✅ Feb 2025 GMP license update = validation runs successful = Flaskworks GMP process approved! prnewswire.com/news-releases/…




