Thanks for the question Beartrap. There’s a lot here that’s been misinterpreted publicly, so let’s walk through it carefully. Mill Creek Life Sciences is a privately held reagent manufacturer based in Minnesota. It is not a hospital, it is not a trial sponsor, and it is not a therapeutic developer. Its entire footprint is in academic research, primarily as a supplier of GMP-grade reagents to institutions running early-phase or investigator-initiated trials. The best-documented example of this is their work with Mayo Clinic, where they provided the manufacturing support necessary for dendritic cell generation in non-commercial clinical protocols. These trials do not operate under a commercial IND, and there is no evidence that Mill Creek has submitted or been included on any drug master file, biologics license, or therapeutic registration. Their involvement is academic-only.
In the Mayo trials, dendritic cells were pulsed not with patient-specific lysate, but with lysate derived from a tumor antigen library. This library was built using in vitro–expanded tumor cell lines and standardized lysate pools. That approach effectively makes it functionally allogeneic, it’s not derived from the individual patient’s tumor. This is a significant distinction. It removes the fully personalized component that defines autologous vaccines like DCVax-L. The Mayo model using the library has value in academic trials because it increases trial efficiency, reduces patient-specific manufacturing constraints, and allows standardized comparisons across subjects. But it also removes the personalized immune targeting that NWBO’s process is built on. Mechanistically, it activates dendritic cells and generates T cell responses, but it does not do so with patient-matched tumor antigens.
Now, regarding the process itself: Yes, even though the antigen source is allogeneic, the dendritic cell generation process in those trials follows the same classical immunology steps: CD14+ monocyte enrichment, exposure to IL-4 and GM-CSF for differentiation into immature DCs, then antigen loading, maturation, and cryopreservation. That is broadly consistent with the process described for DCVax-L. But similarity in biological methods does not imply platform parity, commercial platforms are defined by IP scope, regulatory validation, and manufacturing control, all of which NWBO holds uniquely for DCVax-L. The difference lies in the antigen source, the scope of use, and the regulatory handling. NWBO owns a suite of IP not just around dendritic cell generation, but around the integration of personalized lysate, the specific maturation protocols, the method of delivery, and the commercial-scale manufacturing workflows, including integration of Flaskworks’ automated, closed-system manufacturing platform, developed for consistent, scalable dendritic cell production under GMP. Even if the underlying biological steps overlap, the platform ownership and clinical utility diverge.
There has been some public confusion about whether Mayo/Mill Creek trials overlap with NWBO’s IP. Based on what’s available, it’s more accurate to say that the trials reflect a structurally adjacent effort using similar immunological tools, but without the full DCVax platform. There is no evidence that Mill Creek or Mayo holds rights to the entire end-to-end vaccine architecture. And importantly, these trials were not structured for commercialization. That means no formal assignment of IP in ClinicalTrials.gov listings, no declared manufacturing licensees, and no commercial sponsor named. If NWBO had quietly in-licensed any data or tools from those trials, they would not be required to disclose it until that relationship became material, typically at the point of approval, manufacturing integration, or trial expansion.
Now regarding Merck, this part is often underplayed, but it shouldn’t be. Merck didn’t just provide Keytruda to these trials. In several of the dendritic cell vaccine studies conducted at Mayo, Merck appears in the public record as a collaborator or funding source. These were structured trials with checkpoint inhibitor combination arms. That means Merck supplied drug product, worked with investigators on combination protocols, and likely funded portions of the trial infrastructure. The indications included glioblastoma and NSCLC, at a minimum. This is not uncommon in early immunotherapy development, Merck has used a similar strategy in other investigator-led studies where dendritic cell or tumor vaccine platforms are used to try to increase PD-1 efficacy in non-responsive tumor types. What matters is that Merck invested significant clinical resources in these studies. That’s a real strategic signal, especially given their dominant checkpoint position.
As for the outcomes, many of those Mayo/Mill Creek trials were subsequently terminated or completed without results being posted. That’s critical. In the U.S., academic trials that are not conducted under a commercial IND, or that fall outside the scope of FDAAA 801, are not required to publish results on ClinicalTrials.gov. Once terminated, investigators are under no further obligation to share results publicly unless they choose to do so through journal publication or press release. That means that any data, immune readouts, or findings from these Merck-supported Mayo trials may never be disclosed. And if there were lessons learned, proprietary methods developed, or collaborative frameworks established, they can remain under NDA or internal records.
That brings us to your question about whether any of these trials were tied to known IP or patent ownership. In the case of the Mayo/Mill Creek trials: no. None of the ClinicalTrials.gov records associated with those studies name a patent holder, technology sponsor, or commercial licensor. They were investigator-initiated and classified under exploratory research. That means we cannot assign them to any known platform (DCVax or otherwise) without speculation. If NWBO has any rights to methods or data arising from those trials, that information would not be available until post-approval or follow-on study launch.
For comparison, it’s worth bringing in the UCLA trial using ATL-DC in combination with Hiltonol. That trial used autologous tumor lysate, patient-derived monocytes, and dendritic cell maturation protocols nearly identical to those described in NWBO’s regulatory filings. The study was led by Dr. Linda Liau, who also served as principal investigator at UCLA for NWBO’s Phase 3 DCVax-L trial, and later joined the company in an official capacity after the trial concluded. At the time the ATL-DC + Hiltonol trial was running, it was not identified as a DCVax-L trial publicly. It was referenced only as a dendritic cell vaccine using autologous tumor lysate. It wasn’t until results were published, specifically in peer-reviewed literature including Nature Communications, and after NWBO included UCLA in its list of trial sites, that the connection to DCVax-L became visible. This kind of delayed public attribution is common in blinded, multi-site trials where site-level studies proceed under local IRB oversight but feed into a broader protocol. The process, antigens, and maturation conditions all matched DCVax-L. The link was only acknowledged post-publication.
That’s why UCLA’s trial is the only one that can be confidently associated with NWBO’s platform after the fact. It used the autologous model. It was conducted at a known NWBO trial site. It followed NWBO’s manufacturing logic. In contrast, the Mayo/Mill Creek trials, while biologically similar, used allogeneic inputs, were not linked to a commercial sponsor, and were terminated without publication. So any overlap, if it exists, remains undisclosed and cannot be assumed.
If there’s a commercial relationship behind the scenes, licensing of reagents, methods, or data integration, it will likely surface only when approval occurs or when follow-on trials are launched under a new structure. Until then, we can say with confidence that UCLA’s ATL-DC trial became retrospectively identifiable as DCVax-L based on data and sponsor records, whereas the Mayo/Mill Creek trials remain academic efforts without confirmed IP alignment or declared platform ownership.
Also worth noting, the choice between shared (allogeneic) lysate and autologous tumor lysate has significant clinical and strategic implications. Shared antigen libraries offer logistical advantages: they eliminate the need for surgical tumor harvest, enable faster production timelines, and allow batch manufacturing, which is more scalable and easier to standardize in academic settings. That makes them appealing for early-stage trials or exploratory studies.
But those benefits come at a tradeoff. Shared lysates may lack patient-specific neoantigens, especially in tumors with low mutational burden like glioblastoma, and may present irrelevant or non-immunogenic antigens. That can blunt T cell specificity and reduce the likelihood of a durable anti-tumor response.
Autologous lysate, by contrast, captures the unique mutational and antigenic profile of each patient’s tumor. It introduces personalized signals that the patient’s immune system has never effectively targeted. When pulsed onto autologous dendritic cells, this enables the vaccine to present both shared and private tumor antigens through MHC class I and II pathways, increasing the chances of a patient-specific cytotoxic T cell response.
This personalization is central to DCVax-L’s design. While it introduces manufacturing complexity, it also offers a level of immune targeting that shared models cannot replicate, especially in indications where the tumor microenvironment is immunologically “cold.” That distinction is one reason DCVax-L has been developed and protected as a commercial platform, while shared lysate models have thus far remained limited to academic and exploratory settings.
Hope that clarifies it. Everything above is based on what’s publicly available and structurally verifiable.
Market Data 
Markets 
AI
