Why Washington Just Out-Paced Brussels on AI Device Rules
Why Washington Just Out-Paced Brussels on AI Device Rules
The slow regulator moved first. On 1 October 2026 the US FDA put AI device guidance near the top of its to-do list, while the EU gave itself another year.
The short answer: for AI-enabled devices, the FDA is now signalling the sooner and more detailed documentation bar. We think manufacturers should build their evidence files to that bar now, instead of planning around the EU's August 2028 date. Two caveats apply. The FDA is stating an intention, not a legal deadline, and the EU MDR already applies to your device today.
What did the FDA announce?
The FDA published its fiscal year 2027 guidance priorities, as MedTech Dive reported on 2 October 2026. Finalising its guidance on marketing submissions and lifecycle management for AI-enabled devices is on the top-priority list for the next 12 months. Fiscal year 2027 runs from 1 October 2026 to 30 September 2027.
The document being finalised is the draft guidance of January 2025. Last year's list treated finalising it as a second-tier goal, so it has moved up. A priority is not a promise, and the guidance stays non-binding until the FDA issues the final version.
What is the EU's actual timeline?
The EU AI Act (Regulation (EU) 2024/1689) classes most AI-enabled devices that need a notified body as high-risk. The Digital Omnibus on AI, Regulation (EU) 2026/1744, was published on 24 July 2026 and entered into force three days later. It moved the date for high-risk AI built into regulated products, such as devices, from 2 August 2027 to 2 August 2028.
Law firm commentary gives the reason as missing harmonised standards, guidance and conformity-assessment infrastructure (Freshfields). In other words, the system was not ready.
| FDA | EU | |
|---|---|---|
| Instrument | Guidance on AI-enabled device software | AI Act high-risk rules for devices |
| Status | Draft since January 2025, finalisation prioritised for FY2027 | Law, applies from 2 August 2028 |
| Nature | Non-binding recommendations | Legally binding |
Has Brussels really bought breathing room?
Only for the AI Act layer. AI-enabled devices still need CE marking under the MDR (Regulation 2017/745) or IVDR (Regulation 2017/746) now. Your clinical evidence, risk management and post-market duties did not move.
So the delay is smaller than the headline suggests. It pauses an extra layer of requirements, not the base one.
Why build to the FDA's bar first?
This is our judgement, not a rule. The FDA is likely to be the first to publish a final, detailed description of what a lifecycle-ready AI device file looks like. Once it does, notified bodies, investors and partners will use it as a yardstick, whatever the EU's formal dates say.
There is a cost argument too. Writing the evidence to a higher standard once is cheaper than reopening a finished file later. The risk is that the final FDA text changes, so treat the January 2025 draft as direction, not as settled content.
What should change in your technical documentation?
Three practical shifts follow:
- Document the whole lifecycle, not only the release. Describe how the model was built, validated and monitored, and how it will change after launch. The FDA's draft is framed around the total product lifecycle.
- Plan changes in advance. The FDA's list again includes guidance on predetermined change control plans, which set out in advance how a device may be updated. If your model will learn or be retrained, write that plan early.
- Tie the CER to the same evidence. Your Clinical Evaluation Report (CER) should draw on the same performance data, intended-use limits and post-market findings as the rest of the file. One evidence base, two submissions.
A US-shaped file does not satisfy the AI Act or the MDR by itself. The requirements differ, so you will still need a regional check. The aim is to avoid doing the hard thinking twice.
What is the next step for your team?
Run a gap check this quarter. Take the current technical documentation for one AI-enabled device and compare it, section by section, with the January 2025 FDA draft. List what is missing, rank the gaps by effort, and fix the cheapest high-value ones first.
Key takeaways
- The FDA made AI device guidance a top priority for FY2027, building on its January 2025 draft.
- The EU moved the AI Act date for devices to 2 August 2028, but the MDR and IVDR still apply now.
- An FDA priority is an intention, and its guidance is non-binding. The EU date is law.
- We think writing your file to the stricter, sooner bar is cheaper than retrofitting it later.
- Start with a gap check against the draft, then plan how the model will change after launch.
FAQ
Does the FDA's priority list set a binding deadline?
No. It lists what the agency intends to work on in the year ahead, and resources may change the outcome. The guidance itself is non-binding.
Is the AI Act deadline for medical devices now 2028?
For high-risk AI built into products covered by Annex I, Section A, such as devices, the Digital Omnibus sets 2 August 2028. Please check the final legal text for your exact device type.
Do we still need MDR compliance for an AI device today?
Yes. The AI Act delay does not affect MDR or IVDR requirements, including clinical evaluation.
Can one technical file serve both the FDA and EU?
Largely, for the shared evidence, but not entirely. Each regulator has its own format and rules, so plan a regional check.
Will the final FDA guidance match the January 2025 draft?
We cannot know. Use the draft as a guide, and re-check when the final version appears.
Want to test your AI device file against the stricter bar? Contact the Qmedify Regulatory Team.