9 signals this week: 8 Quality, 1 Clinical trials

RA and market access teams need a standing process for checking the JCA list on each update, because the Commission's page gives no advance notice of which categories move into scope, the spreadsheet is the only authoritative record.

Pull the published spreadsheet (hta_ongoing-jca_en.xlsx) and cross-check it line by line against your EU pipeline, the Commission's page does not narrate which categories were added, so the only way to know if a product is now in scope is to open the file.

Every economic operator placing devices on the EU market now has a mandatory-use obligation across all four modules dated to 28 May 2026, not a rolling voluntary transition, competent authorities can check registration, certificate, and surveillance status directly rather than requesting paper records.

Audit actor registration, UDI/device registration, notified body certificate records, and market surveillance data for every EU device line against the 28 May 2026 mandatory-use date, ahead of the next competent authority inspection.

EMA/67888/2026 gives RA teams a dated, named reference for what EMA and national competent authorities say about their own AI use, rather than the vaguer industry assumption that regulatory review is already AI-augmented end to end.

Read the Observatory report's four sections, guidance and policy, applications of AI, collaboration and engagement, and EU-funded initiatives, against your own submission workflow to see which regulator-side functions are already AI-touched versus fully manual.

Ten AI medical device manufacturers now have a route to regulator-supervised NHS testing ahead of UKCA marking, run jointly by MHRA, NHS England London, and three named Health Innovation Networks, a specific, capacity-limited programme, not an open-ended policy statement.

Check whether your AI device pipeline fits the initial 10-manufacturer cohort profile and has a real-world evidence gap London Region I could fill before the next intake round.

The comment window now runs through 29 June 2026, a five-week extension from the original deadline, giving RA and clinical development teams more time to prepare comments grounded in actual governance evidence rather than general capability claims.

Pull the original 29 April 2026 notice (91 FR 23100) for the actual RFI questions before drafting a comment, the 28 May notice only extends the deadline to 29 June, it doesn't restate what FDA is asking.

The 458-day median time to recall means devices with thin clinical evidence at authorisation don't fail immediately, they fail roughly 15 months in, after deployment decisions and procurement contracts are already in place. Evidence completeness at authorisation is the earliest point to catch this risk.

Check whether your AI device submissions carry complete clinical study information on file, the 1.39 hazard ratio in the JAMA cohort applies specifically to devices missing that information at authorisation, so gaps identified now can be closed through supplemental filings before a recall event forces the question.

The spreadsheet is the only authoritative record of JCA scope, market access teams checking only the Commission's web page, and not the linked file, will miss additions.

Build a recurring calendar check for the hta_ongoing-jca_en.xlsx file specifically, since the Commission does not publish change notes alongside it, a diff against the prior version is the only way to catch new entries.

The three-month window between the 10 April open and 10 July close is the only chance to shape the text before finalisation, FDA, EMA, TGA, Health Canada, and PMDA all sit on IMDRF and have historically referenced its finalised frameworks in national guidance, so comments submitted during the window have a direct line to future domestic requirements.

Submit consultation feedback before the 10 July 2026 close, after that date the framework moves toward finalisation and the window for shaping post-market monitoring and algorithm-change-management requirements closes.

Reuters attributes the letter to repeated lapses rather than a single incident, but confirming whether FDA treated this as multi-site or single-site enforcement requires the primary letter text, which is not reachable from the sourceUrl on file for this signal.

Locate the actual Medline warning letter on FDA's site (searchable by company name and 2026 date range, since the general landing URL does not surface it directly) before drawing site-specific conclusions, then assess whether comparable patterns exist across your own manufacturing sites.