RTCT May Redefine What Operational Oversight Looks Like
Signals, latency, interoperability, and the future of operational oversight and inspection readiness
This article reflects insights and analysis following the FDA Industry Information Session on Real-Time Clinical Trials held on May 15, 2026 from 11:00 AM – 1:00 PM ET.
Participants:
- Jeremy Walsh, Chief AI Officer, FDA
- Malika Mundkur, MD, MPH, Deputy Chief Medical Officer, FDA
- Sundeep Agrawal, Associate Director, Oncology Center of Excellence, FDA
The FDA webinar on Real-Time Clinical Trials (RTCT) was framed as a discussion about accelerating clinical trials through more connected, interoperable, and real-time operational models.
But underneath the technical discussion was a much more important signal:
The FDA appears increasingly interested in reducing operational latency across the clinical trial ecosystem.
And that has significant implications for how sponsors demonstrate oversight, operational control, and inspection readiness moving forward.
The most interesting aspect of the discussion was not the technology itself.
It was the operational philosophy underneath it.
Ultimately, what the FDA described was not simply a faster submission mechanism or a new method for transmitting clinical data.
It was the early outline of a more signal-based, event-driven oversight model.
The FDA Is Thinking in Signals, Not Static Data Transfers
One of the clearest themes throughout the session was the FDA’s repeated distinction between:
- patient-level data
- operational and clinical signals
Jeremy Walsh clarified multiple times that the FDA is not looking to ingest continuous streams of raw patient data.
Rather, the focus shifts toward:
- predefined protocol-driven signals
- operational triggers
- enrollment activity
- safety trends
- endpoint-related events
- changes that may warrant regulatory visibility or operational attention
That distinction matters.
Operationally, it shifts the conversation away from “real-time data sharing” and toward something more operationally significant: continuous visibility into meaningful operational trial activity.
Specifically, the architecture discussed was:
- API-driven
- JSON-schema based
- interoperable
- protocol-informed
- event-oriented
And notably, the FDA repeatedly emphasized wanting only the minimum amount of information necessary to support timely awareness and decision-making.
That suggests the agency is thinking carefully about:
- signal relevance
- operational burden
- scalability
- privacy boundaries
- interoperability efficiency
Ultimately, his is not simply a modernization of submission workflows.
It is the early development of a signal-based operational oversight framework.
The Real Focus of the Webinar Was Latency
The operational concept that surfaced most consistently throughout the webinar was latency reduction.
Again and again, speakers referenced:
- reducing delay
- accelerating visibility
- shortening time between event occurrence and awareness
- improving the speed of operational interpretation
Operationally, latency exists throughout clinical development today:
- vendor handoffs
- site reporting
- reconciliation cycles
- safety review
- issue escalation
- TMF filing
- cross-functional communication
- protocol deviation review
The FDA appears increasingly interested in determining which aspects of that latency are operationally necessary and which are simply artifacts of fragmented systems and legacy workflows.
Importantly, that is a very different regulatory conversation than sponsors are traditionally used to having.
More broadly, it aligns closely with the direction of ICH E6(R3), particularly around:
- risk-proportionate oversight
- fit-for-purpose systems
- proactive quality management
- operational control across people, process, and systems
RTCT appears to operationalize many of those same concepts through a more continuous visibility model.
Why the Protocol-to-Schema Discussion May Have Been the Most Important Part
One of the more consequential technical details discussed was the FDA’s explanation of how submitted protocols are being translated into machine-readable reporting structures.
The agency described taking protocols and converting them into JSON-based reporting schemas that define:
- expected signals
- operational reporting logic
- protocol-driven reporting structures
- event visibility requirements
Operationally, that has major implications.
Because once protocols begin functioning not only as scientific documents but also as structured operational reporting frameworks, oversight itself becomes more computable, standardized, and potentially more dynamic.
That opens the door to:
- standardized signal architectures
- machine-assisted operational monitoring
- more structured oversight visibility
- automated interpretation of predefined events
- increased cross-study comparability
- more scalable operational analytics
Ultimately, trial sponsors should pay close attention to this direction, because it fundamentally changes the operational architecture underneath oversight activities.
The FDA Is Intentionally Limiting Scope Right Now
The FDA also repeatedly clarified that the current RTCT proof-of-concept work and expanded pilot discussions remain focused on Phase I and early Phase II studies.
That limitation appears highly intentional.
Early-phase studies:
- involve smaller patient populations
- generate concentrated safety activity
- allow tighter operational control
- create more manageable signal environments
- move more quickly operationally
Importantly, the FDA explicitly stated that Phase III studies are not currently the target area for this initiative.
At the same time, speakers acknowledged that the long-term vision is broader and could eventually extend into later-phase environments if the concepts prove successful.
Operationally, that distinction matters because scaling RTCT concepts into Phase III and Phase IV environments changes the complexity model dramatically:
- larger patient populations
- global site networks
- broader vendor ecosystems
- significantly higher signal volume
- more complex governance structures
- greater interoperability demands
Ultimately, the fact that the FDA is constraining scope so carefully right now suggests the agency recognizes how operationally significant broader deployment could become.
Oncology’s Involvement Matters
Another important signal from today’s webinar was the involvement of the Oncology Center of Excellence (OCE).
That matters because many of the FDA’s more progressive operational modernization initiatives have emerged from oncology first:
- Real-Time Oncology Review (RTOR)
- Project Orbis
- collaborative international review models
- accelerated operational review approaches
RTCT appears philosophically aligned with many of those same efforts.
Collectively, this suggests the FDA may increasingly be exploring whether operational visibility itself can become more continuous, collaborative, and adaptive throughout the lifecycle of a study.
This is likely one reason the current proof-of-concept work is focused in oncology environments, where:
- timelines are compressed
- signal visibility is critical
- operational learning cycles move quickly
- earlier regulatory awareness can materially impact development decisions
The Inspection Readiness Implications Are Significant
For companies focused on inspection readiness, the most important takeaway may be this:
The FDA appears increasingly interested in operational awareness, not simply operational documentation.
Historically, many oversight narratives were reconstructed retrospectively:
- issues were contextualized later
- deviations were analyzed later
- reconciliation occurred later
- TMF narratives were clarified later
- operational timelines were rebuilt later
A signal-based oversight environment compresses that reconstruction window considerably.
Meanwhile, under ICH E6(R3), sponsors are already being pushed toward:
- contemporaneous oversight
- ongoing risk evaluation
- proactive issue management
- connected governance structures
- operational traceability
RTCT reinforces that direction.
Not because regulators suddenly expect perfect real-time operations, but because the architecture being discussed increasingly supports earlier visibility into:
- operational trends
- escalation responsiveness
- study-level risk signals
- oversight activity
- protocol-defined events
- decision timing
That raises the importance of:
- metadata quality
- interoperability
- signal governance
- escalation logic
- cross-functional operational visibility
- fit-for-purpose oversight systems
In other words, the operational maturity of the sponsor environment itself becomes increasingly important.
Final Thought
The FDA webinar was presented as a discussion about Real-Time Clinical Trials.
But the more important signal underneath the discussion was this:
The FDA appears to be moving toward a more event-driven, signal-oriented, and operationally continuous oversight philosophy.
Not overnight.
And not yet at enterprise scale.
But directionally, the shift was very clear.
What the agency described today was not simply a faster method for exchanging information.
It was an early framework for how operational oversight itself may evolve within increasingly connected, interoperable, and risk-informed clinical trial environments.
And for sponsors thinking seriously about inspection readiness under ICH E6(R3), that distinction matters.
