Accelerating innovation

Sponsors Leave. Patients Don't.

The lifecycle of a rare disease therapy involves multiple parties. Most of them are transient. The person with the disease is not.

Bluebird bio received European marketing authorization for Zynteglo, a gene therapy for transfusion-dependent beta-thalassemia, in June 2019. The therapy cost approximately $1.8 million per treatment. By 2021, the company had withdrawn from Germany after failing to reach a reimbursement agreement. By 2022, it had exited the European market entirely, pulling both Zynteglo and Skysona (a gene therapy for cerebral adrenoleukodystrophy) from European availability. The company reported quarterly losses in the hundreds of millions and warned that there was "substantial doubt" about its ability to remain solvent. In 2025, bluebird bio was acquired by private equity firms Carlyle and SK Capital Partners for $29 million, a company that had once been valued in the billions.

The families whose children had received bluebird's gene therapies still had the therapies in their cells. The families who were waiting for treatment no longer had access. The clinical data generated during the development and post-market monitoring of those therapies was now held by a private equity-owned entity with no obligation to make it available for research, no commitment to long-term follow-up, and no relationship with the rare disease community that had enrolled in the clinical trials.

This is not an exceptional event. It is the normal lifecycle of rare disease drug development.

The Pattern

Pharmaceutical companies enter rare disease markets for rational economic reasons: orphan drug incentives (seven years of market exclusivity in the U.S., ten in the EU), smaller clinical trials (lower development costs), premium pricing (payers accept higher per-dose prices for severe, rare conditions), and faster regulatory pathways (accelerated approval, breakthrough therapy designation). These incentives can make rare disease drug development profitable.

Pharmaceutical companies exit rare disease markets for equally rational economic reasons: revenue falls short of projections, reimbursement negotiations fail, manufacturing costs exceed revenue, a larger company acquires the smaller one and deprioritizes the rare disease portfolio, or the company simply runs out of money. The exit is a business decision. It is not made with reference to the families whose children depend on the therapy.

When a sponsor exits, several things happen to the data infrastructure.

The disease registry the sponsor funded may lose its funding source. Rare disease registries are expensive to maintain: data management, quality assurance, regulatory compliance, and site coordination cost hundreds of thousands of dollars annually. Many registries are funded directly by the pharmaceutical sponsor, either through direct support or through contracts with contract research organizations (CROs). When the sponsor leaves, the funding stops.

The natural history data collected during the development program may become inaccessible. Clinical trial data is held by the sponsor under regulatory agreements with the FDA or EMA. The sponsor is required to retain the data for specified periods, but there is no requirement to make it available for subsequent research, to transfer it to the rare disease community, or to maintain it in a queryable format. The data may be archived in a proprietary database, absorbed into the acquiring company's systems, or effectively lost when the CRO that managed the trial is itself acquired or dissolved.

The long-term follow-up data, the most valuable component for gene therapies and other curative treatments, may stop being collected. Gene therapy recipients require decades of follow-up to monitor for late effects, durability of gene expression, and long-term safety. The FDA requires 15 years of follow-up for gene therapy recipients. If the sponsor exits at year 3, who collects the data for years 4 through 15? The regulatory requirement exists. The enforcement mechanism for a company that no longer exists does not.

The Parties Who Exit

The lifecycle of a rare disease therapy involves multiple parties, and the majority of them are transient.

The pharmaceutical company that sponsors the development program may exit through acquisition, bankruptcy, strategic reprioritization, or market withdrawal. The average tenure of a pharmaceutical company in a specific rare disease market is difficult to measure precisely, but the pattern of entry and exit is well documented across dozens of conditions.

The academic principal investigator who runs the natural history study may retire, lose funding, or shift research focus. Academic careers last decades, but grant funding for a specific rare disease study lasts three to five years. When the grant ends, data collection stops unless new funding is secured. The PI who devoted 15 years to studying a rare disease retires eventually. The postdoctoral fellow who maintained the database moves to another position. The institutional knowledge of how the data was collected, what the variables mean, and where the quality issues are leaves with them.

The contract research organization that managed the clinical trial data may be acquired. CRO consolidation is ongoing: smaller CROs are regularly absorbed by larger ones. Data migration during acquisition is imperfect. Databases may be reformatted, archived, or simply not transferred. The data from a Phase II trial conducted in 2015 by a CRO that was acquired in 2018 may be retrievable by someone who knows where to look, or it may not.

The regulatory agency retains submissions and review documents, but regulatory databases are not designed for research use. They hold the data that the sponsor submitted, in the format the sponsor chose, for the purpose of evaluating safety and efficacy at the time of the submission. They are not longitudinal research databases.

The Participant Who Does Not Exit

The person with the rare disease does not exit. The parent of a child with the rare disease does not exit. They are the one party whose engagement is permanent.

The parent who managed PKU from the day of diagnosis will manage it until the child takes over, and then will worry about it until she dies. The adult with Ehlers-Danlos syndrome who has tracked symptoms for 20 years will continue tracking them for 20 more. The person who received a gene therapy at age two will carry the transgene for life and will need follow-up data collection for decades.

The permanence of the affected individual's engagement is the structural argument for data custody. If the data must persist for 50 years, and every other stakeholder's engagement is measured in years, the data must be held by the stakeholder who stays.

What Data Custody Means

Data custody, in the context of a rare disease data trust, means that the people who contribute data retain governance rights over its use, access terms, and disposition. The data trust holds the data under a fiduciary obligation to the contributors, not under a contractual obligation to a sponsor.

The practical implications are specific.

When a sponsor exits, the data persists. The natural history data collected during a clinical development program, if contributed by the affected individuals to a data trust rather than held by the sponsor, survives the sponsor's departure. The next sponsor entering the market inherits a richer dataset than the first sponsor built, because the data has been accumulating during the interval between sponsors.

When a PI retires, the data persists. The longitudinal data collected during an academic natural history study, if structured and held in a data trust rather than on a university server maintained by a graduate student, survives the PI's departure. The next researcher studying the condition does not start from zero.

When a CRO is acquired, the data persists. Clinical trial data contributed by participants to a data trust, rather than held exclusively by the CRO, is not subject to the uncertainties of corporate acquisition. The data stays where the contributors put it, under governance terms the contributors agreed to.

The data trust does not prevent sponsors from entering or exiting. It does not interfere with the business decisions that pharmaceutical companies make. It simply ensures that the data generated during each sponsor's engagement survives that engagement and is available to the next participant in the ecosystem.

The Compounding Effect of Persistence

Each sponsor transition, in the current system, is a data loss event. The new sponsor starts with whatever published literature exists, whatever regulatory submissions are publicly available, and whatever the new PI can reconstruct from personal contacts and conference presentations. The unpublished data, the granular individual-level data, the adverse event reports, the quality-of-life assessments, the long-term follow-up observations: these are the data that would most accelerate the new program, and they are the data most likely to be lost.

In a persistent data infrastructure, each sponsor transition is a data inheritance event. The new sponsor enters a market where the natural history data is richer than when the last sponsor entered, because the data has continued to accumulate. The safety database from the previous sponsor's therapy is available, structured and queryable, to inform the design of the new therapy. The regulatory submission for the new therapy can reference the accumulated evidence base rather than building one from scratch.

The difference between a data loss event and a data inheritance event, repeated across dozens of conditions and hundreds of sponsor transitions over decades, is the difference between a field that periodically resets to zero and a field that compounds knowledge over time.

The Mennonite Lesson

The Clinic for Special Children in Lancaster County, Pennsylvania, has operated continuously since 1989. Its data on maple syrup urine disease, glutaric acidemia type I, and dozens of other conditions spans more than three decades. The clinic has survived multiple funding cycles, changes in leadership, and the evolution of treatment approaches. The data persists because the community persists. The Amish and Mennonite families who fund the clinic through benefit auctions are the same families whose children receive care. The financial relationship is direct, and the commitment is permanent.

The clinic is not a data trust. It is a clinical practice with an embedded research program. But it demonstrates the principle: when the community that generates the data is also the community that sustains the infrastructure, the infrastructure persists.

Sponsors come and go. Companies are acquired. PIs retire. Grants expire. CROs are consolidated. The families remain. The data infrastructure should be designed for the stakeholder who stays.