Novo Nordisk’s OpenAI partnership got a week of headlines back in April and then the cycle moved on. I’m still thinking about it — because the part that’s actually hard was never the part anyone reported.
It’s being read as a model story. It’s an infrastructure story, and the hard part isn’t OpenAI.
I’ve spent years building systems inside regulated clinical research environments. The part that’s hard about a Novo Nordisk-scale rollout has very little to do with which AI is doing the work. It has everything to do with the layer underneath.
Start with the data. Clinical trial data is among the messiest data anywhere — pulled from dozens of sites, written under different protocols, captured in different versions of the same case report form, vocabulary inconsistent across studies that started two years apart. The “data ready” stage most AI projects assume already exists is something pharma companies pay vendors millions of dollars to maintain. It’s still not really there.
Then layer GxP on top. In a regulated environment, an AI recommendation isn’t usable unless it’s traceable and auditable end to end. A prompt change is a controlled document. The output gets reviewed against the protocol. Any system in the workflow has to be qualified before anything it produces can affect a patient or a submission. That’s the work the announcement isn’t talking about, and it’s the work that has to happen before any model output is considered usable.
Underneath all of that is the integration layer. CTMS, EDC, eTMF, LIMS, ERP — the systems Novo already runs were never designed to share data with anything, let alone with an autonomous AI orchestrating across them. Building that integration is the slower, more expensive part of this rollout by a wide margin.
None of this is a reason it won’t work. Novo Nordisk is well-resourced and serious. But the timeline is ambitious. Twelve months in pharma is roughly one validation cycle if everything goes well, and rollouts of this scope rarely run without something going sideways. The rollout will expose how much of the work is infrastructure, not intelligence.
What I’d watch for: who they hire. The model decision is the easy one. The orchestration team is the project. The people they staff for this will tell you whether they understand that.