##  [Regulatory Context Ecosystem is ALIVE!](/blog/regulatory-context-ecosystem-is-alive) 

    November 16, 2026 

  ![Regulatory Context Ecosystem is ALIVE!]()

7 min read 

- [Medicinal Products](/blog-main-categories/medicinal-products)
- [Regulatory Affairs](/blog-main-categories/regulatory-affairs)





 

At [Freyr ONE USA 2026](https://www.freyrsolutions.com/freyr-events/freyrone-usa-2026-princeton-nj), Chris Lee, vice president of regulatory affairs innovation and strategic operations at Gilead Sciences, outlined the case for moving beyond incremental improvements in regulatory technology. His keynote explored a more fundamental shift: moving from systems that manage regulatory information to regulatory context ecosystem that connects information, context and action.

At the centre of his presentation was an “ecosystem of context.” The idea extends beyond connecting applications. It brings together the data, processes and relationships that shape how a medicinal product is developed, improved and maintained. That context must also be available within the individual business processes where decisions are made.

The presentation connected this ambition with grounded AI, cross-functional collaboration and the practical demands of execution. Throughout, one principle remained clear: regulatory digital transformation must ultimately demonstrate its value through better business and patient outcomes.

### Digital convergence is challenging the limits of incremental improvement 

The keynote described a “cosmic collision” between business process outsourcing providers, contract research organizations, established providers, AI platforms and hyperscalers. Organizations are moving into one another’s spaces, bringing services, data, technology and science into closer contact. This convergence creates room for new approaches to digital transformation in life sciences and broadens the range of organizations providing regulatory capabilities.

At the same time, the presentation noted limitations in the current digital environment. Despite years of development, the industry remained incrementally better equipped than it had been several years earlier. The issue was not a lack of willingness or vision among regulatory teams. It was technical infrastructure that continued to limit what they could achieve.

This provided the context for the keynote. New capabilities are emerging, but their significance depends on whether they help organizations move beyond familiar limitations. The larger opportunity is to reconsider how the digital environment supports regulatory work as a whole.

### Regulatory context must extend beyond the system of record 

Much of the focus in regulatory information technology has been on documents, storage and systems of record. These remain necessary, but they do not represent the full environment in which regulatory decisions are made.

The proposed shift was from managing information to managing its context. That means understanding the relationships around a record: how it connects to a medicinal product, where it sits within a process and which dependencies matter to the work. An ecosystem of context makes those relationships part of the digital environment rather than treating them as a separate consideration.

The distinction matters at two levels. Across the product lifecycle, context connects the information and dependencies that support development and maintenance. Within an individual process, it helps establish what is relevant to the decision at hand.

Systems of record still have a place in this model, supporting regulatory data management. The proposed architecture retained them as sources, alongside external signals and medicinal product context. The change lies in how these elements work together, rather than simply where information is stored.

### Grounded AI requires confidence in the evidence behind an answer 

The section on AI brought the importance of context into focus. [Confidence in the information behind an AI response was a central concern.](https://www.freyrsolutions.com/artificial-intelligence-ai-regulatory-services)

Chris illustrated the concern through his experience of an AI assistant that could access external sources whose credibility was not necessarily clear. The availability of an answer did not, by itself, establish that the information behind it was reliable. This was the basis on grounded AI in regulatory affairs: intelligence built on validated information.

This should not be read as a rejection of external intelligence. External signals were explicitly included in the proposed ecosystem. They help establish context and inform how an organization responds. The concern was with relying on information without sufficient confidence in its credibility, not with looking beyond internal systems.

Evidence integrity therefore remains central. The objective is to strengthen the connection between evidence and decisions, rather than rely on an answer without understanding its sources. As intelligence becomes more embedded in regulatory work, the evidence supporting it must remain part of the decision-making process.

### A connected architecture must carry intelligence through to action 

An ecosystem of context needs more than connected sources. It also needs capabilities that help people find relevant information, interpret it and use it within a business process.

The proposed architecture brought together source information, external signals, medicinal product context and context services. Knowledge graphs, semantic retrieval and analysis were important components. Grounded AI and predictive signals would help identify patterns that could inform action and portfolio insights.

The significance of the proposal was in how these elements worked together. Knowledge graphs, retrieval capabilities and AI were presented as connected elements supporting regulatory intelligence within the proposed architecture. Each had a role in connecting information with the decisions and actions the business needed to take.

Learning loops extended across the proposed environment. This was not intended to be a one-way flow from information to an answer. The decisions and actions supported by the ecosystem would also vary according to the topic and the stage of the business process.

The architecture was presented as a starting point for collaboration, not a finished blueprint. Its purpose was to make the shift toward context more tangible and explore how it could work in practice.

### Integration matters more than the boundaries of individual platforms 

The presentation also examined the constraints of monolithic platforms. Progress within an individual system does not necessarily produce an environment in which context, data and processes work together.

A platform-agnostic approach changes the emphasis. The starting point becomes the context and execution the business needs, rather than the boundaries of a particular application. Individual platforms must be considered in relation to the wider environment they are expected to support.

This has implications for the way organizations work with technology and service partners. The requirement is broader than supplying another tool or capability. It is to help connect regulatory context, process execution and digital capabilities within a coherent approach.

The closing emphasis was therefore on collaboration. Organizations and their partners need a shared expectation of what the regulatory ecosystem should enable.

### Operational execution is the real test of the vision 

A clear architecture can establish the direction. It cannot, on its own, change how work gets done.

The keynote repeatedly returned to the gap between describing a digital future and putting it into practice. Cross-functional governance, ways of working and enabling technology all need to support execution. Metrics are equally important. They help organizations assess performance, identify opportunities for improvement and understand whether the environment is supporting better-informed decisions.

This makes transformation an organizational undertaking, not simply a technology programme. Connecting systems and data must be accompanied by a workable approach to how the environment is governed and used across functions.

Measurement also makes the value visible beyond the teams delivering the change. It allows the wider enterprise to understand what has improved, rather than judge progress only by the capabilities introduced.

Business and patient outcomes remained the focus throughout the presentation. The purpose was not to create a more sophisticated digital environment for its own sake. It was to support regulatory work that contributes to organizational objectives, public health and better patient care. Those outcomes must guide execution, not be assumed to follow from technology adoption.

### Conclusion: Connecting evidence, decisions and outcomes 

The keynote’s message was clear: incremental improvements in information management are not the full ambition. The next step is to connect information with the context that makes it useful.

A regulatory context ecosystem requires grounded intelligence, an integrated digital environment and a practical approach to cross-functional execution. It also requires organizations and their partners to work toward a shared direction. The aim is to connect evidence to decisions and decisions to outcomes, while preserving the integrity of the evidence along the way.

**Ready to connect regulatory information, context and action? Talk to** [**Freyr’s regulatory intelligence experts.**](https://www.freyrregintel.com/freya-intelligence)

## Frequently Asked Questions



#### [What is a regulatory context ecosystem?](#collapseOne)



A regulatory context ecosystem connects the data, processes, relationships and strategic dependencies that shape how a medicinal product is developed, improved and maintained. Described in the keynote as an “ecosystem of context,” it extends beyond individual systems of record. Its purpose is to make relevant context available within the business processes where information supports decisions and action.







#### [What is regulatory context in regulatory affairs?](#collapseTwo)



Regulatory context concerns how information relates to a medicinal product, a business process and the dependencies surrounding it. It helps establish why information matters to a particular decision, rather than simply where it is stored. The keynote addressed context at both the product lifecycle level and within individual processes, where teams need to interpret information in relation to their work.







#### [What is grounded AI, and why is it important for regulatory decision-making?](#collapseThree)



Grounded AI bases its responses and insights on validated information. This matters because an AI assistant may retrieve information from external sources whose credibility is unclear. Grounded AI in regulatory affairs aims to provide a more dependable information base for decisions. The emphasis is on confidence in the supporting evidence, not simply the availability of an answer.







#### [What is regulatory intelligence in the pharmaceutical industry?](#collapseFour)



Within the approach presented in the keynote, regulatory intelligence brings together information, external signals and medicinal product context to support decisions and action. Analysis and predictive signals help identify relevant patterns and portfolio insights. The focus is on understanding what information means for a product or business process, rather than treating access to information as the end goal.







#### [How can organizations connect regulatory information and business processes?](#collapseFive)



The proposed approach connects systems of record and external signals with medicinal product context. That context needs to be available within individual business processes, so information can be interpreted in relation to the work being performed. Cross-functional governance, enabling technology and performance metrics support putting this connected environment into operation and assessing how effectively it works.







#### [What is the role of knowledge graphs in regulatory intelligence?](#collapseSix)



Knowledge graphs were included in the proposed architecture alongside semantic retrieval and analysis. These capabilities were presented as parts of a broader ecosystem that brings information and medicinal product context into regulatory work. Their relevance lies in how they work together to support finding and analysing information within the context of business decisions and actions.