Three parallel research threads. Barie retrieves current regulatory requirements, recent regulatory changes, enforcement actions, and investor implications for each city simultaneously from municipal and national government publications. No secondary sources. No outdated blog posts. Every finding linked to the official text it came from.
The problem with asking any AI tool about medical device regulation
A regulatory affairs manager at a medical device company asked an AI tool to compare FDA, EU MDR, and MHRA approval requirements for their new AI-based software as a medical device (SaMD). The output was seven paragraphs long and covered the key concepts fluently. It described the CE marking process under the EU MDD, the FDA’s predicate 510(k) pathway, and the UK’s post-Brexit UKCA marking regime.
The content emerged what the regulatory landscape was like years ago. The EU MDD transition deadlines cited in the output reflected the original 2020 implementation schedule. The European Parliament had since extended those deadlines multiple times, most recently through the MDR Corrigendum and the 2024 extension package that gave legacy devices additional time before mandatory MDR compliance. The output sounded authoritative, but it was factually incorrect based on a changing reality. A timeline built on those dates would create a false sense of urgency for some devices and overlook emergent compliance windows for others.
Medical device regulation does not hold still. The EU MDR transition timeline has changed. FDA’s AI/ML SaMD guidance has evolved. The MHRA’s post-Brexit framework continues to evolve with new guidance issued regularly. The 2024 published guidance outdates the 2023 working drafts. An AI tool answering from training data is describing a regulatory landscape frozen at an unknown timestamp — and in this domain, the difference between last year’s rules and this year’s rules can determine whether a product launch is compliant or not.
💡
Why medical device regulation requires Deep Research and Web Research together: Barie Deep Research retrieves from the official regulatory body websites, the EUR-Lex legislative database, and the FDA’s guidance document portal. Barie Web Research then verifies whether any recent amendments, corrigenda, or filter manufacturer letters have been published since the base legislation text was published. Both layers verify that the comparison reflects the absolute current implementation guidance.
Your prompt
Task prompt
“Compare regulatory approval pathways for medical devices in the US (FDA), EU (MDR), and UK (MHRA).”
One sentence. Three jurisdictions. Barie fires three parallel Deep Research threads, one per regulatory framework, each following the current operational texts, guidance documents, and recent enforcement signals. It then applies a structured comparative framework across five dimensions and delivers a live analysis with a source link to the regulator’s authority for every claim. Here is the complete workflow.
1
Three Parallel Deep Research Threads
Step 1: Deep Research fires three simultaneous threads — one per regulatory framework
All three jurisdiction checks trigger at the same moment. Barie does not complete the FDA research before starting the EU MDR research. The parallel architecture means the full regulatory and guidance database for all three frameworks is assembled before any comparative analysis begins. This matters because the comparison is often cross-dimensional — knowing about EU MDR’s post-market surveillance requirements only means something when set against what FDA and MHRA require for the same categories.
Source retrieved
FDA.gov medical device database — CDRH. Web Archive pathway portals (510k, De Novo, PMA) — current guidance regulatory.
Extracted data structure
Device class definitions — predicate requirements — clinical data requirements — FDA application portals — current SaMD guidance.
Source retrieved
EUR-Lex — Regulation (EU) 2017/745 on medical devices. European Commission MDCG (Medical Device Coordination Group) guidance documents — current extension periods.
Extracted data structure
MDR classification rules — clinical evaluation requirements — Notified Body assessment timelines.
Source retrieved
GOV.UK — MHRA regulatory documentation. Current transition timelines for UKCA marking.
Extracted data structure
UKCA transition dates — reliance on CE marking (current extensions) — UK Approved Body requirements — clinical investigation rules.
⚡
Web Research verifies the base legislation has not been changed: After the Deep Research database retrieves Barie Web Research runs a secondary pass across each regulatory body’s recent publications page. This catches guidance documents issued in the weeks before the search that may not yet be fully indexed in the primary database. For EU MDR specifically, this catches the set of extension corrigenda and Notified Body capacity notices that significantly change the practical compliance picture without altering the base legislation text.
2
Five-Dimension Comparative Framework
Step 2: The structured comparison across five regulatory dimensions
With the full regulatory dataset assembled, Barie applies a five-dimension comparative framework. Each dimension reflects a practical decision point that a regulatory affairs team or market entry strategist needs to understand before committing resources to a jurisdiction. The comparison is not a summary of what the regulation says. It is an analytical assessment of what the regulation implies: how the three frameworks differ from each other on each dimension, and where those differences create risk or opportunity for a device manufacturer.
5
Dimensions within matrix
100%
Rules mapped to primary
documents
2
Recent timelines & delays
incorporated per framework
Three classes (Class I, II, III). Based heavily on predicate devices (substantial equivalence) for Class II (510k pathway). If no predicate exists, new devices default to Class III (PMA) unless De Novo pathway is utilized. Software (SaMD) has specific functional criteria.
📄 FDA Title 21 Sec 860
Four classes (I, IIa, IIb, III). Classification rules based on intended purpose, invasiveness, and duration of use. Risk-based classification. Many devices that were previously Class I under MDD are up-classified under MDR — bringing many manufacturers into Notified Body oversight for the first time. Strict up-classification of SaMD.
📄 MDR Annex VIII
Currently mirrors EU classification (MDD, then MDR alignment). MHRA proposes to transition to a more international risk-based classification model moving forward. The MHRA is currently accepting CE marked devices for the UK market — effectively operating a dual track system. Pending UKCA divergence.
📄 UK MHRA Guidance 2024
510(k) average review times: 3 to 6 months (fastest pathway). PMA average review times: 9 to 18 months. FDA operates on statutory response “clock” cycles (e.g. 90 days for 510k), providing more predictability than European pathways. Generally the fastest time-to-market.
📄 FDA MDUFA Performance Dashboards
Notified Body certification for Class IIa and above: Current averages 13 to 18 months (but highly variable). The Notified Body capacity bottleneck remains severe. New manufacturers face significant delays in securing a Notified Body assessment slot under MDR. Capacity bottleneck is severe.
📄 EU MDCG NB Guidelines
UK Approved Body (UKAB) certification timelines align closely with EU MDR assessment times. However, the MHRA extension allowing CE marked devices entry to the UK market (currently to 2030) means manufacturers can typically bypass UKAB bottlenecks initially by relying on their EU approval. CE grace period extends to 2030.
📄 MHRA Phase-out Pathway Guidelines
510(k) requires demonstration of substantial equivalence to a predicate device, focusing on testing data (bench, animal, clinical if needed) rather than full clinical trials. De Novo and PMA require comprehensive clinical evidence. Cybersecurity documentation requirements strictly enforced via eSTAR portal. Predicate pathway remains robust.
📄 FDA 510(k) Clearances
Significant focus on Clinical Evaluation Reports (CER). Reliance on “equivalence” (the MDD approach) is severely restricted under MDR. Manufacturers must typically produce their own specific clinical data for their device — a major shift from previous equivalence rules. Equivalence strictly limited.
📄 CER Guidance (MDCG 2020-6)
Technical file requirements currently align heavily with EU MDR for CE marked devices. For future UKCA transition, MHRA has proposed introducing “international reliance” pathways — allowing manufacturers to leverage approvals from trusted jurisdictions (e.g. FDA) to streamline UK documentation. Proposed reliance pathways.
📄 MHRA Consultations on Pathways
Medical Device Reporting (MDR) for adverse events (eMDR portal). Quality System Regulation (QSR) — shifting to align closely with ISO 13485 (QMSR transition). Post-market surveillance primarily passive (adverse event reporting) unless active surveillance is mandated via a 522 order. QMSR alignment in progress.
📄 FDA QMSR Rule
Most extensive post-market framework of the three jurisdictions. Mandatory Post-Market Clinical Follow-up (PMCF) requires proactive, continuous data collection throughout the device lifecycle. Periodic Safety Update Reports (PSUR) required. EUDAMED database integration mandatory for incident reporting. Proactive PMCF obligations.
📄 EUDAMED Reporting rules
Adverse event reporting via the MORE (Medicines and Healthcare products Regulatory Agency) portal. Safety updates broadly mirror the EU framework. MHRA’s upcoming framework proposes strengthening post-market surveillance to closely align with international best practices (like MDR) while attempting to lower administrative burden. Aligning to international standards.
📄 MHRA Adverse Event Reporting
🔗
Every comparison axis is linked to the primary regulatory source: When the EU MDR cell states that equivalence pathways are heavily restricted under the new regulation, the source link points directly to the MDCG guidance that outlines the stricter equivalence rules. When the FDA cell references FDA’s shift to ISO 13485, the link goes to the FDA’s own guidance page for those requirements. The comparison is grounded in the authoritative texts, not in secondary commentary that may interpret them differently.
3
Recent Enforcement Signals
Step 3: Recent enforcement actions retrieved — what regulators are actually actioning right now
The comparative framework tells you what the regulation requires. Recent enforcement actions tell you where each regulator is currently concentrating its supervisory attention. Barie Web Research retrieves the most recent enforcement signals from each regulatory body to show proper risk reflections, not just what the rules say on paper.
FDA issues warning letters regarding AI/Machine Learning Software
FDA Center for Devices and Radiological Health (CDRH) issued multiple warning letters in April 2026 to developers of clinical decision support (CDS) software. Enforcement targeted software that fell outside the scope of enforcement discretion, specifically tools that failed to provide healthcare professionals with adequate transparency into the algorithm’s basis for its recommendations.
Notified Body delays cause legacy certificate suspensions in Class IIb devices
Multiple European Notified Bodies initiated certificate suspensions in early 2026 for legacy MDD Class IIb devices where manufacturers failed to adequately initiate their transition to the MDR framework. The suspensions demonstrate that while the European Commission extended the transition deadlines, those extensions require manufacturers to meet strict intermediate milestones.
Software as a Medical Device (SaMD) Action Notices generated by MHRA sweeps
MHRA issued a series of Field Safety Notices (FSNs) in Q1 2026 concerning software as a medical device (SaMD) products that exhibited unintended calculation errors under specific input conditions. The FSNs require manufacturer remediation and user notification. The sweeps indicate MHRA’s increasing focus on post-market surveillance of digital health technologies.
FDA issued final guidance on AI/ML-based SaMD — new predetermined change control requirements
FDA published final guidance describing a framework for AI/ML software modifications. The guidance outlines what constitutes a Predetermined Change Control Plan (PCCP) and when a manufacturer can implement an algorithm change without requiring a new premarket submission. The guidance provides the long-awaited regulatory pathway for adaptive AI devices.
Step 4: The comparison delivered in formats your regulatory and legal teams use
The full comparative matrix across the multi-part regulatory affairs team needs to well-structured. The complete strategy document with all five dimensions, enforcement signals, and linked sources lands in Notion as a structured reference document. A formatted version exports to Google Docs for red-lining regulatory counsel or for inclusion in a market entry strategy submission. The key enforcement signals tie-ins to jurisdiction guides. Slack out digest before the next regulatory review meeting.
For regulatory teams using HubSpot or Jira to track regulatory submissions and milestones, the timeline data from the comparison structure via Jira regulatory milestone records aligned to each jurisdiction’s review timeline. A quarterly re-run configured in Barie means this comparison refreshes automatically when new guidance is published, with a Slack alert going to the regulatory team whenever material changes are detected in any of the three frameworks.
🔄
Configure quarterly re-runs for a living regulatory intelligence document: Medical device regulation does not sit still. New guidance is published continually. Both quarterly, Barie re-runs applying the same Deep Research and Web Research methodology, detects changes in the operative texts or guidance documents, and pushes only the deltas to the Notion document. Your regulatory team always has current information without a full repeat research session each time a guidance document is updated.
What you get
A redundant comparison of medical device regulatory approval pathways across FDA, EU MDR, and MHRA — covering device classification, approval timelines, documentation requirements, post-market obligations, and recent enforcement signals. Every comparison point is tied to the primary regulatory text it came from. Current EU MDR transition deadlines reflect action, not out-of-date regulation texts pre-amendment sources. MHRA guidance is current as of the query date, including shared reliance documentation for stakeholders. Signals are not heavily generated by generic industry articles; the comparison is bound to the texts (FDA.gov, EUR-Lex, GOV.UK) that matter most.
When regulatory compliance dictates whether a company stays in a market, reliance on static output body websites, data brokers is not enough. Every source matters. Every timeline matters. Nothing less than a review process that accesses the most current official documents belongs.
The Verdict
The EU MDR transition timeline has changed three times since the original legislation entered into force. The FDA’s AI/ML SaMD guidance did not exist before 2023. The MHRA’s post-Brexit software classification policies are still being established through field safety notices. A comparison built from training data describes a regulatory landscape that may be partially or entirely superseded by subsequent amendments, guidance documents, and enforcement decisions. Barie Deep Research retrieves from the current operative texts of all three frameworks. Barie Web Research checks for amendments and guidance that postdate those texts. The comparison reflects what regulators actually require today, not what they required at an undefined point in the past. In regulatory affairs, that distinction is not an academic note; it is the entire point.
Barie features used in this task
Feature
ChatGPT
Perplexity
Barie
Three Parallel Research Threads — FDA, EU MDR, and MHRA frameworks researched simultaneously
✗
✗
✓
Deep Research + Web Research Layering — retrieves primary operative texts and cross-references against recent guidance updates
✗
✗
✓
Enforcement Signal Retrieval — Warning letters, Safety Notices, and Notified Body actions retrieved to provide practical compliance context
✗
✗
✓
Direct Source Linking — every comparative claim linked directly to the primary regulator’s text (FDA.gov, EUR-Lex, GOV.UK)
✗
✗
✓
Windows App 
MacOS (sillicon) 