Platform Progress, Transparency Gaps in the EU Pharma Package
The European Union is in the middle of revising its medicines legislation. This reform, often referred to as the “pharma package,” centers on a proposed new Pharmaceutical Regulation and a proposed new Pharmaceutical Directive. Its stated aims are to improve access to medicines, encourage innovation, and strengthen the EU’s competitiveness and security of supply.

Published
Author
Share
The European Union is in the middle of revising its medicines legislation. This reform, often referred to as the “pharma package,” centers on a proposed new Pharmaceutical Regulation and a proposed new Pharmaceutical Directive. Its stated aims are to improve access to medicines, encourage innovation, and strengthen the EU’s competitiveness and security of supply.
The pharma package introduces what are known as platform technologies as a new regulatory concept in the EU medicines regulation. This matters beyond the EU because similar platform-based approaches are already central to drug development globally, and regulatory choices in one major market shape how these technologies are developed, governed, and accessed elsewhere.
Platform technologies are reusable technological foundations on which different medicines and innovation ecosystems can be built. An mRNA system or viral vector, for example, can be adapted by developers for different diseases, pathogens, or patient groups. Think of an mRNA platform adapted from one infectious disease target to another: The core delivery system and much of the manufacturing process may remain the same even though the sequence and disease target change. The attraction is straightforward: Where the underlying system is already known, regulators need not start from zero each time. The newly negotiated draft reflects that logic most clearly by creating a route for certified platform technology master files, which would allow later applications to rely on data already assessed for the platform. In simple terms, that means regulators could assess the reusable backbone of a platform once, and later applications could rely on that earlier assessment rather than duplicating the entire evidentiary exercise.
That is a welcome development. But a platform-based future also depends on whether other developers can tell whether a platform is actually available for reuse and on what terms. The newly negotiated draft begins to build the regulatory architecture for platform-based development, but it still says little about the legal conditions on which other developers may access and reuse those platforms.
Here, “transparency” does not mean disclosure of trade secrets. At minimum, such metadata could identify the key patent families covering the platform backbone or delivery system, indicate whether licensing is open, case-by-case, or unavailable, flag whether regulatory data protection still applies, and note whether key materials are subject to transfer restrictions.
A More Modular Future
Earlier versions of the reform acknowledged platform technologies, but in a much narrower way, chiefly for use in exceptional circumstances. The newly negotiated draft moves beyond that model. It frames platform technology master files as a way to rely on pre-evaluated quality, non-clinical, and clinical data, avoid duplicative assessments, and reduce the repetition of studies. In other words, the package begins to accept a more modular approach to medicines regulation: Not every new medicine needs to be assessed entirely from scratch where the underlying technological platform has already been evaluated.
The draft reflects a more diverse innovation ecosystem in which ownership of platform technology and marketing authorization may be held by different entities. Some platforms may originate in academic or publicly funded research before moving into regulatory use, allowing industry and academia to build on prior work instead of reinventing it.
When Platforms Meet Intellectual Property
Pharmaceutical innovation is deeply dependent on intellectual property. But platform technologies raise additional questions: not only whether protection exists, but whether follow-on users can tell what is protected, by whom, and on what terms.
If those surrounding rights and agreements remain opaque, two bad outcomes follow. Some developers, especially smaller firms and academic groups, may avoid the platform altogether because the legal risk is too hard to price. Others may accept practical lock-in, tying themselves to one technological route because switching becomes legally or economically costly. That would frustrate the package’s promise of reuse and entrench dependence on a small number of proprietary technological routes. “Transparency” means that there is enough visibility into patents, protected data, licenses, and material transfer restrictions to know what strings are attached when re-using a platform technology.
Finishing the Job
This is where the EU pharma package still feels unfinished. Yes, the negotiated draft creates a repository for certified platform technology master files and their assessment reports. But the text specifically emphasizes the protection of commercially confidential information and guarantees access for competent authorities. That is a narrow form of regulatory transparency, not one that is meaningful for the broader set of innovators who may want, or need, to rely on a platform.
A modest reform would go a long way: When a sponsor seeks certification of a platform technology master file, the framework could require disclosure of structured metadata on relevant patents, licensing posture, and material transfer restrictions. This would not entail disclosure of confidential details or trade secrets. Just enough transparency to let other developers understand whether a platform is realistically open to follow-on use, and under what conditions. Tools such as patent pledges could also play a role here.
Europe does not need to choose between platform technologies and intellectual property. It needs to make those two systems work together. The negotiated draft takes a meaningful first step by recognizing that some medicines can and should be developed more modularly. But that promise will remain limited if developers cannot tell whether a platform is realistically available for follow-on use, and on what terms. The broader lesson is simple: Reuse frameworks do not work well when the legal conditions of access remain opaque.