Two EU medical device shifts landed in the last 60 days. Together, they redraw how US device and diagnostic companies should be thinking about launch readiness, technical files, and AI/ML strategy through 2027.

The Bottom Line

On May 28, 2026, four EUDAMED modules stopped being optional. On the same regulatory desk, MedTech Europe put out a position paper arguing that AI-enabled medical devices should sit under MDR/IVDR conformity assessment, not the EU AI Act.

Read separately, they look like housekeeping. Read together, they change the launch checklist for every US company selling a device or diagnostic into the EU.

The next 90 days are decision days for five things: Actor SRN status, UDI data integrity, AI/ML technical file design, the EU authorized representative contract, and the post-market surveillance data pipeline.

Waiting to see how the AI Act question resolves is the wrong move. Structuring the technical file to work under either scenario is the right one.

Part 1: EUDAMED Is Now Law, and Actor Registration Is a Launch Gate

Four EUDAMED modules became mandatory on May 28, 2026:

  • Actor Registration
  • UDI and Devices Registration
  • Notified Bodies and Certificates
  • Market Surveillance

Any device placed on the EU market from May 28 onward needs the manufacturer, or the authorized representative for non-EU manufacturers, registered in the Actor module first. Device data has to be loaded to EUDAMED specifications before the launch date.

The failure mode is not a fine. The failure mode is a launch that cannot happen because the Actor SRN is not issued, or the device data does not validate against the EUDAMED schema, and the notified body cannot close out the certificate on time.

Three things most US manufacturers underweighted

Actor registration is a legal entity task, not an IT task. It has document requirements, sometimes a Single Registration Number turnaround measured in weeks, and it needs the authorized representative fully set up first. If the EU AR contract is new or in transition, expect friction.

UDI-DI and Basic UDI-DI data has to match the technical file, the labeling, and the notified body certificate. Any drift shows up in EUDAMED as a validation error and blocks the record. Labeling cycles that were tolerated internally for years suddenly matter externally.

Post-market surveillance and vigilance reporting flows through EUDAMED now. If your PMS system was built for local competent authority reporting only, the transition to EUDAMED-native reporting is not a switch flip. It is a data model project.

One thing that has not changed

The transitional MDR extension for legacy devices, typically December 31, 2027 or December 31, 2028, only holds if there are no significant design changes and an MDR-compliant QMS is in place. EUDAMED registration does not extend that runway. It tightens the operational overhead required to keep those devices on the market.

Part 2: MedTech Europe Wants AI Devices Under MDR, Not the AI Act. And It Matters Either Way.

The MedTech Europe MDR/IVDR revision position paper argues that AI-enabled medical devices should be regulated primarily under MDR/IVDR conformity assessment, with EU AI Act high-risk requirements not applying where MDR/IVDR already covers the same ground.

The industry position is coherent. AI-enabled medical devices already face clinical evaluation, risk management (ISO 14971), software lifecycle (IEC 62304), post-market surveillance, and cybersecurity requirements. Layering EU AI Act Article 6 obligations on top creates duplicate documentation, duplicate audits, and duplicate reporting into overlapping systems.

But the outcome is not decided.

Two scenarios to plan for

Scenario A: The Commission adopts the MedTech Europe position, in whole or in substantial part. AI devices stay in the MDR/IVDR lane. Technical files get an AI-specific annex. Notified bodies take on formal AI competency requirements. Dual-track compliance goes away for SaMD and AI/ML embedded devices.

Scenario B: The position does not carry, or only partially carries. AI-enabled devices continue to face both MDR and AI Act obligations. Expect a 2027–2028 wave of retrofits: risk management bolted onto AI Act Article 9, transparency documentation for Article 13, human oversight for Article 14, and post-market monitoring feeding both EUDAMED and AI Act monitoring obligations.

The wrong move today is waiting to see which way it lands. The right move is building the technical file so it can accommodate either outcome without a rewrite. That means AI/ML documentation structured to serve both frameworks: model description, training data lineage, performance evaluation, monitoring plan, and change control that can flex between MDR-only and MDR-plus-AI-Act reporting.

Part 3: What Both Mean Together

The two stories are not independent. They compound.

The EUDAMED record is a public statement of regulatory classification. Every AI-enabled device that goes into EUDAMED starting now carries an implicit statement about which regulatory framework governs it. That statement gets locked into the record. Changing the classification later is not free.

One PMS pipeline, two possible destinations. Post-market surveillance under MDR feeds EUDAMED. If AI Act obligations also apply, the same performance drift signals need to feed a second monitoring system. Build the data pipeline once, route it twice.

Notified body capacity is the constraint. Notified bodies certified for MDR AI competency are a small set. If Scenario B plays out, that set has to be re-certified for AI Act oversight as well, and the timeline is not measured in months.

US-first companies are the most exposed on both fronts. The EU authorized representative is the entity carrying the Actor registration and, in Scenario B, would be the point of contact for AI Act supervisory authorities as well. The contract that was signed once and never revisited is now a liability.

The takeaway is not that Europe is getting harder. It is that Europe is getting more integrated, and integration rewards companies that structure their technical files, PMS systems, and AR relationships to serve multiple regulatory frameworks from the same source of truth.

What To Do In The Next 90 Days

  1. Confirm Actor SRN status for every EU-market device and every planned launch through Q1 2027. If the SRN is not issued, the launch cannot start.

  2. Audit UDI-DI and Basic UDI-DI data against the technical file, the label, and the notified body certificate. Fix drift now, not at EUDAMED validation.

  3. Map every AI or ML component in the portfolio against both MDR/IVDR and EU AI Act Article 6 obligations. Structure the technical file to serve both.

  4. Review the EU authorized representative contract. Confirm it covers EUDAMED reporting obligations and, in Scenario B, AI Act supervisory contact responsibilities.

  5. Rebuild the PMS data flow so signal detection feeds EUDAMED, and can also feed AI Act post-market monitoring if that requirement lands.

Where NanoCoeur Consulting Fits

Most US medical device companies do not have a dedicated EU regulatory team. They have a US RA lead, a consulting notified body relationship, and an authorized representative contract that was signed once and has not been reviewed since MDR entered application.

That structure worked when EUDAMED was voluntary and the AI Act was theoretical. It does not work now.

NanoCoeur Consulting works with device and diagnostic teams on exactly this seam. Practical, operator-voice regulatory and CMC work, scoped to a specific decision or launch date.

Engagements we run

  • EUDAMED launch readiness assessment. Actor SRN status, UDI data integrity, PMS pipeline mapping, and a punchlist of what has to be true before the next EU launch date.

  • AI/ML technical file structuring. Model documentation, training data lineage, performance monitoring, and change control designed to serve MDR now and AI Act if it lands.

  • EU authorized representative contract review. Scope, SRN ownership, reporting responsibilities, escalation paths, termination terms.

  • Notified body engagement strategy. Which NBs have the AI competency to certify your device, what their queue looks like, and how to sequence submissions.

  • Post-market surveillance system design. A single source of truth that can feed EUDAMED today and AI Act supervisory reporting tomorrow without a rebuild.

  • Fractional program leadership. For companies that need a senior operator in the seat for 6 to 18 months, not a permanent hire.

Every project has a defined scope, a defined deliverable, and a defined decision it supports. No open-ended retainers.

Is EUDAMED or AI/ML regulatory strategy on your Q3 or Q4 launch checklist?

A 30-minute call is enough to identify where the friction lives.

Schedule a call →

Sources

  • MedTech Europe. EUDAMED reaches a major milestone: mandatory use of the first four modules begins. June 4, 2026. medtecheurope.org
  • Osborne Clarke. EU triggers mandatory Eudamed use for diagnostics and medtech from May 2026. osborneclarke.com
  • MedDeviceGuide. MedTech Europe MDR/IVDR 2.0 Position Paper: Proposed Changes. meddeviceguide.com
  • Dmed Technologies. 2026 MedTech Regulatory Outlook: MDR/IVDR and FDA QMSR. dmed-technologies.com
  • European Commission. EUDAMED implementing regulation and module documentation.
  • MedTech Europe. MDR/IVDR revision position paper on AI-enabled medical devices.

NanoCoeur Consulting LLC is a New Hampshire S-Corp providing life sciences operations advisory across biotech, pharma, and medical devices. Nothing in this article constitutes legal advice. Regulatory decisions should be validated with qualified counsel and your notified body.