9 signals this week: 2 Quality, 4 Clinical trials, 3 Regulatory

The three-document package, guidance, template, technical specification, is FDA's attempt at something narrower than "digital transformation": a protocol format regulators, sponsors, ethics bodies, and investigators can all read the same way. Sponsors who start their next protocol in the M11 template avoid rebuilding it for CTIS later.

Map your next new-study protocol to FDA's Common Protocol Template before drafting starts, not after, the companion technical specification is what lets that content move as structured data instead of a document someone has to re-key later.

Chief AI Officer Jeremy Walsh's comment on the pilot is the tell for how seriously FDA is treating this: "Real-time trials have been talked about for years. We demonstrated that it is not only possible, but also potentially transformative for the clinical trials ecosystem." Sponsors and EDC vendors who haven't commented yet still have the extended window to do so.

The RFI FDA is running is titled "AI-Enabled Optimization of Early-Phase Clinical Trials Pilot Program," tied to a pilot the agency says launches this summer. Comments should answer FDA's actual operational questions, data feed architecture, real-time data quality standards, access protocols, and patient privacy during live streaming, not general support for the concept.

Healthcare AI developers with EU-deployed systems should submit input before 23 July, the classification outcome, not the Act's text alone, determines whether full conformity assessment applies before 2 August.

The European Commission opened this consultation on 19 May and extended it once already: "The consultation was originally open for 6 weeks until 23 June. However, the Commission has received requests from several associations and other stakeholders to extend it further by 4 weeks," pushing the close to 23 July. Map each EU-deployed system against the draft Annex III criteria before that date, systems landing as high-risk need a conformity assessment programme finished by 2 August.

MHRA ran a 2025 pilot of this Scientific Dialogue programme "to assess whether early, structured regulatory engagement could support better evidence generation", this cycle extends that same pilot to devices for the first time.

Device sponsors should apply within the 20 May to 11:59pm BST 17 August window if both MHRA approval and NICE appraisal are planned, that's the deadline on the published programme page for the newly-opened device track.

The 40.5% recruitment-within-200-days figure is the number CROs should be citing in EU site-selection justifications going forward, it's ACT EU's own reported baseline, not a projection, and it's the kind of number a sponsor can defend to a steering committee.

Build both figures into EU site-feasibility assessments as the current baseline, not an aspirational target, they're ACT EU's own reported numbers, not a projection.

Teams preparing 510(k), De Novo, or PMA submissions should confirm they're on the current eSTAR version before relying on last cycle's template, the form itself is where FDA pushes new content requirements now.

Device teams should check eSTAR's version notes before every submission cycle, the most recent confirmed update folded in "the content of the Human Factors Content Guidance, published on May 29, 2026, and effective on August 1, 2026" directly into the nIVD and IVD templates.

Diabetes, metabolic disease, and obesity trial sponsors using CGM as a primary or secondary endpoint should map their data collection protocol against the specification before their next IND or NDA, a mismatched format is what generates the additional information request.

Sponsors with active CGM endpoints should validate submission file formats against FDA's specification before database lock, not after, this guidance is final, not draft, so there's no comment window left to wait out.

Health Canada expects manufacturers to describe the "processes, surveillance and performance monitoring plans and risk mitigations in place to ensure ongoing performance and inter-compatibility of the ML system", that belongs in the submission from device inception, not bolted on after a question comes back.

Build the change-type list and revalidation triggers into the PCCP before submission, the plan has to be pre-authorized, not written after the fact.

The recommended label covers adults with obesity, or overweight adults with at least one weight-related comorbidity, used alongside diet and physical activity, the same population as injectable Wegovy. Payer and market access teams should model the oral formulation's uptake among patients who previously declined an injectable as its own segment, separate from patients simply switching formulations.

Pharmacovigilance plans should track prior injectable GLP-1 exposure, comorbidities, and compliance history separately for the oral cohort, that's a different population than the one the injectable safety data was built on.