MHRA

Ask the safety/device vigilance and PV CSV leads to: (1) confirm whether any marketed/fielded SaMD/AIaMD uses adaptive ML or planned updates that would fit a PCCP-like approach; (2) review current change-control SOPs and technical documentation to ensure change governance and transparency artifacts are captured and retrievable; (3) verify post-market/vigilance processes explicitly account for algorithm updates (e.g., monitoring after updates, escalation criteria).

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.

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