CAPA

Safety lead to: (1) perform a UK-clinical-trial safety reporting gap assessment against MHRA’s effective guidance sections (MedDRA coding; AE/SAE; RSI governance; SUSARs; annual safety reporting; USMs; serious breaches; temporary suspension), (2) update controlled SOPs/WIs and training records to reflect “effective” status as of 28 Apr 2026, and (3) document deviations/gaps and open CAPA where needed for ongoing UK trials and new submissions.

Safety/Device Vigilance owner to: (1) confirm SOPs and training link to MHRA’s “Medical devices: post-market surveillance” collection as the live index; (2) validate operational readiness to submit adverse incident and FSCA-related reports via MHRA’s referenced MORE route; (3) confirm device PSUR process uses MHRA-linked standardised PSUR format and PSUR guidance tied to the Regulations 2024 framework; (4) update internal regulatory intelligence trackers with the 16 June 2025 in-force date cited across MHRA guidance, and monitor related MHRA future regime pages for further updates.

1) Inventory AI use cases that could feed regulated decisions (including PV/safety-related analyses or summaries used in regulatory interactions) and map owners/vendors. 2) For each AI use case, document context of use, intended outputs, and controls (e.g., review/approval, traceability, change management) aligned to a draft-guidance tracking plan. 3) Track the Federal Register notice and plan whether to submit comments within the window described by FDA (90 days after Federal Register publication).

Fda update requires triage for Signal Validation, Local Affiliate Compliance, Device Vigilance; confirm local obligations and document follow-up actions.

Ema update requires triage for Local Affiliate Compliance, Vendor Oversight, Inspection Readiness; confirm local obligations and document follow-up actions.