U N D E R T H E M I C R O S C O P E

When did Haleon first adopt Veeva Vault? It isn’ t too clear online. And what was the initial motivation behind the move?

Prasidda: Haleon was formed from GSK, where we then separated the pharma and consumer healthcare divisions. We already had applications running on Veeva Vault from around 2021, particularly for the clinical side. When Haleon was created, we transitioned those applications initially designed for pharma into Haleon. However, they included both pharma and consumer healthcare data, which we needed to separate. That’ s when we launched the new‘ Study Vault’, focused purely on consumer healthcare. This year, that new vault went live and we’ re now phasing out legacy GSK data to focus entirely on Haleon’ s consumer applications.

How is Haleon approaching the simplification of the five Vault systems? Are there specific strategies or frameworks being used to streamline setup and maintenance?

HALEON’ S DATA INFRASTRUCTURE DEMERGER JOURNEY WITH VEEVA SYSTEMS

During a recent visit to Madrid, we sat down with Prasidda Ananthram Rao Puttur, Senior System Engineer at Haleon, and Andrzej Dróżyński, Senior System Engineer, R & D Safety at Haleon, to explore how the company’ s demerger from GSK and the critical role of Veeva Systems in supporting Haleon’ s evolving data infrastructure. We also touch on their approach to simplifying five Vault environments and how automation and AI are paving the way for smarter, leaner operations.

that means user automation, deployment automation and automated content authoring. That’ s all in our roadmap up to 2030, developed alongside our product team.

Andrzej: And AI is a big part of that future too. At the summit, we saw some interesting developments from Veeva, particularly around AI agents that could redefine how we add value. For instance, content authoring automation, where documents can be generated automatically without going through CROs manually.

Prasidda: Yes, that was one of the key takeaways. AI agents doing content creation was a great example. People can be hesitant with new tech, but we believe in trying it out to see what works. We’ ve learned a lot in the last two days here and it’ s helping us shape the next few years.

Do you have any feedback from employees about the five Vault systems?

Prasidda: The clean-up has definitely been one of the hardest parts. It’ s been a long-running project that we started last June and went live in April this year. We’ re still migrating data, with a target go-live for June. By September, we expect to have stabilised the application and start working through our backlog of enhancements, like simplifying workflows such as replacing some reports with simple notifications, for example.

From an engineering and architecture standpoint, both of us are focused on bringing in automation. For Q3 and Q4,

Andrzej: Yes, internally we apply a consistent environment strategy across all Vaults. For end users, they mostly interact with production, but we ensure sandboxes, URLs, naming conventions and processes are aligned. That makes automation and integration easier, even though we’ re working on different Vaults like clinical and safety, the processes look the same.

Prasidda: We also share knowledge weekly. As engineers, we use the same platform, even if the business processes differ. Our release manager, Carol, brings everyone together

60 www. intelligenthealth. tech