Harmonized
Common standards give concepts a consistent meaning across sources, so downstream analysis can work with the clinical information rather than reconcile its formatting.
AI can help clean the data, connect the infrastructure, and build the intelligence. The strategic question for pharma and biotech: which work should your team make its own?
Hear Sundeep on where organizations can focus their AI investment.
Building every layer yourself can mean repeating work that other teams are already doing.
In Sundeep's view, the decision goes beyond the cost of running a model. It includes the people designing the workflows, resolving data inconsistencies, and interpreting the results.
For many real-world data programs, the early work is similar across companies. The opportunity is to build on a trusted foundation and focus your own resources on decisions, applications, and insights that are distinctive to your business.
The AI resources behind each workflow.
The effort between acquiring data and using it.
The expertise your people bring to the problem.
Select a layer to see the work involved—and what it means for your team.
Assemble records, resolve differences in naming and structure, and add the context needed to use the data consistently. Even individually clean sources still need to work together.
A test can look different across laboratories. A common interpretation helps your analysis follow the clinical concept, rather than the source's formatting.
Laboratories can use different test names, codes, units, and free-text conventions. Without the right context, an AI workflow may treat equivalent concepts as unrelated—or miss a distinction that matters.
Harmonization is more than moving records into one place. It brings clinical meaning into a structure that downstream teams and applications can interpret.
Standard test codeCODEInternal abbreviationNAMEFree-text descriptionTEXTSundeep proposes four practical criteria. Together, they describe a foundation that gives an AI application more than a set of values to process.
Before building the next application, consider the data foundation beneath it. Watch Sundeep discuss why defining AI-ready data matters—then explore the four criteria below.
Common standards give concepts a consistent meaning across sources, so downstream analysis can work with the clinical information rather than reconcile its formatting.
Address available gaps and connect records at the patient level where possible, supporting a more coherent view across the participating data.
Make field definitions, derivations, and limitations understandable, so applications have the context needed to interpret what the data represents.
Provide appropriate connectivity for AI applications to query the data and its context. The article highlights MCP as one approach to that connection.
The case for shared foundations is strongest when multiple companies are solving similar problems with the same underlying sources. That creates room to focus internal investment on the intelligence above the foundation.
Evaluate partners on transparency and auditability, as well as usability.
Apply your strategy, expertise, and workflows to the questions that matter to your business.
There are valid reasons to own more of the stack. Sundeep notes that control, audit requirements, and unique proprietary data can justify an internal approach. The choice should follow the value of the work to your organization, rather than an assumption that every layer needs to be rebuilt.
Spend them where they make you different.Read “Where Are You Spending Your Tokens in RWD?” on LinkedIn ↗
A connected clinical foundation supports the work above it. The intelligence comes from how your organization applies it to its own priorities.
Bring clinical signals and provider context into the way your team evaluates engagement opportunities.
Develop the rules, workflows, and follow-through that connect a relevant event to your commercial strategy.
Use your market understanding and business objectives to decide which analytical applications to build next.
Prognos harmonizes and enriches laboratory data, connects available patient and provider context, and helps teams create a usable foundation for analytics and commercial applications.
Adapted from Sundeep Bhan's perspective on AI investment in real-world data, published October 14, 2026. Read the original article for his full argument.
Tell us what your team is building—and where data preparation, context, or connectivity is slowing the work down. Let's explore the foundation that can support your next step.