Context card
One technical file, two sets of requirements: what the AI Act adds to an MDR or IVDR file
Does a medical device with AI need a second technical file for the EU AI Act?
The short answer
No. For a device that is a high-risk AI system, a single set of technical documentation is drawn up that holds the MDR or IVDR content and the AI Act information (Article 11(2) of the AI Act), and the AI Act quality elements can be added to the existing quality management system. What the AI Act adds is content — data governance, logging, transparency, human oversight, accuracy — not a second file.
For: Technical writers, regulatory affairs and quality managers of medical device manufacturers
Key points
- High-risk only when the AI system is a device or a safety component of one and the device needs a notified body (Art. 6(1), Annex I Section A).
- A single set of technical documentation is drawn up (Art. 11(2)); the QMS elements can join the existing QMS (Art. 17(3)).
- For devices, the AI Act high-risk requirements apply from August 2, 2028 (as amended by Regulation (EU) 2026/1744); MDR and IVDR apply now.
- The notified body assesses the AI Act requirements within the MDR or IVDR procedure.
- Substantial modification under the AI Act is its own concept; it doesn’t follow the MDR change rules automatically.
The context
Why "two documentation systems" is the wrong picture
The MDR and the IVDR are listed in Annex I Section A of the AI Act. For products under these laws the AI Act does not build a parallel route: an AI system that is a device, or a safety component of one, and whose device needs notified-body involvement is a high-risk AI system (Article 6(1)), and its AI Act requirements are checked inside the device conformity assessment (Article 43(3)).
Article 11(2) says it outright: for such products, a single set of technical documentation is drawn up that contains the information of the device law and of Annex IV of the AI Act (see single technical documentation). Article 17(3) lets the AI Act quality management elements become part of the existing system under ISO 13485 and the MDR. MDCG 2025-6 (adopted jointly with the AI Board as AIB 2025-1) encourages exactly that.
So the question for the documentation team is not "which file?" but "what is missing in the file we have?"
What the AI Act adds
The matrix below lists the twelve places where the AI Act adds content to an MDR technical file. Most of them are not new topics for a device maker — risk management, IFU, PMS — but they ask new questions: about the data the model learned from, about logs, about who can override the output and about declared accuracy. The AI Act technical documentation entry lists Annex IV in full.
Timing
The MDR and IVDR apply now, whatever the AI Act says. For devices, the AI Act high-risk requirements apply from August 2, 2028: Regulation (EU) 2026/1744 set that date for Annex I Section A. Check the consolidated text before quoting other dates.
What this card does not say
The crosswalk orders questions; it does not decide them for a product. Whether an AI system is high-risk follows from the device classification, never the other way round, and the AI Act does not change a device's MDR or IVDR class. Naming a requirement here never means a product meets it. The evidence chain behind the file is drawn on the medical-device evidence chain map; the encyclopedia topic explains the documents.
Where the AI Act adds content to the device file
Twelve questions, each with what it asks, the question it depends on, where it is decided and the dated reference. Numbers in brackets point to the sources below.
Scroll sideways to see every column.
| # | Cluster | Question | What it asks | Depends on | Where it is debated | Dated reference |
|---|---|---|---|---|---|---|
| 1 | Scope | Is the AI part a high-risk AI system? | Whether the AI system is a device or a safety component of one and the device needs notified-body conformity assessment. | Card question | MDCG/AI Board; notified bodies | AI Act Art. 6(1), Annex I Section A [1]; MDCG 2025-6 [5] |
| 2 | Purpose | Which intended purpose does the AI serve? | Whether the MDR/IVDR intended purpose also describes what the AI system is for, its users and its setting. | Row 1 | Manufacturers; notified bodies | MDR Art. 2(12) [3]; AI Act Art. 3(12) [1] |
| 3 | Risk management | Does the device risk file cover AI risks? | Whether the ISO 14971-based risk management also covers the AI Act risks to health, safety and fundamental rights. | Row 1 | Manufacturers; MDCG | AI Act Art. 9 [1]; MDR Annex I Ch. I [3]; MDCG 2025-6 [5] |
| 4 | Data | Where do data governance records go? | Training, validation and test data: origin, collection, preparation, representativeness and bias examination. | Row 3 | Data science and regulatory teams | AI Act Art. 10 [1]; MDCG 2025-6 [5] |
| 5 | Technical documentation | One file or two? | Whether the AI Act information of Annex IV can sit in the MDR/IVDR technical documentation as one set. | Row 1 | Notified bodies; technical writers | AI Act Art. 11(2) [1]; MDR Annexes II and III [3]; IVDR Annexes II and III [4] |
| 6 | Record keeping | What does the device log? | Automatic logging of events over the system lifetime and how long logs are kept. | Row 5 | Software engineering; deployers | AI Act Art. 12 and 19 [1] |
| 7 | Transparency and IFU | Do the IFU carry the AI Act information? | Whether the MDR/IVDR instructions for use also give the AI Act information: capabilities, limitations, accuracy, human oversight. | Row 5 | Technical writers; labelling | AI Act Art. 13 [1]; MDR Annex I Ch. III 23 [3] |
| 8 | Human oversight | Who can override or stop the AI output? | The design measures that let clinicians or other users understand, interpret, override and stop the output. | Row 7 | Usability engineering; clinical users | AI Act Art. 14 [1] |
| 9 | Accuracy and security | Are accuracy, robustness and cybersecurity declared? | Declared accuracy metrics in the IFU and the evidence for robustness and cybersecurity against AI-specific attacks. | Row 5 | Verification and validation; security | AI Act Art. 15 [1]; MDR Annex I 17 [3] |
| 10 | QMS | One quality management system? | Whether the AI Act QMS elements are added to the existing MDR/IVDR QMS instead of a second system. | Row 1 | Quality management | AI Act Art. 17(3) [1]; MDCG 2025-6 [5] |
| 11 | Post-market | One post-market system? | Whether AI post-market monitoring and serious-incident reporting fit into the MDR/IVDR PMS and vigilance system. | Row 10 | PMS and vigilance teams | AI Act Art. 72 and 73 [1]; MDR Art. 83–92 [3] |
| 12 | Conformity and timing | Who assesses, and from when? | The notified body assesses the AI Act requirements within the MDR/IVDR procedure; for devices they apply from August 2, 2028. | Row 1 | Notified bodies; Commission | AI Act Art. 43(3) [1]; Regulation (EU) 2026/1744 [2] |
| 13 | Changes | When does a model change need a new assessment? | Substantial modification under the AI Act vs. significant or substantial change under MDR/IVDR — two autonomous concepts. | Row 12 | Notified bodies; MDCG | AI Act Art. 43(4) [1]; MDCG 2025-6 [5] |
The matrix orders the questions; it never decides them for a product. Legal status as of November 10, 2026.
Dated anchors
Official documents that set or explain the interplay, newest first.
Last entry:
Scroll sideways to see every column.
| Date | Region | Development | Focal point | Matrix rows |
|---|---|---|---|---|
| EU | Regulation (EU) 2026/1744 (Digital Omnibus on AI) is published; for Annex I Section A products the high-risk requirements apply from August 2, 2028 [2]. | Timing | 12 | |
| EU | MDCG 2025-6 / AIB 2025-1, the FAQ on the interplay between MDR/IVDR and the AI Act, is adopted (non-binding guidance) [5]. | Classification, QMS, documentation, changes | 1, 3, 4, 10, 13 | |
| EU | The AI Act is published in the Official Journal; Article 11(2) requires a single set of technical documentation for Annex I Section A products [1]. | Documentation | 5, 6, 7, 8, 9, 11 | |
| EU | MDR and IVDR are published, with technical documentation in Annexes II and III [3] [4]. | Device file | 2, 5 |
The interplay is settled in the law; guidance explains it and may be updated as the AI Act is implemented.
Questions readers ask next
- Is every medical device with AI a high-risk AI system?
- No. It takes two conditions: the AI system is the device or a safety component of it, and the device needs a notified body for its conformity assessment. A class I device that the manufacturer assesses alone is not high-risk under Article 6(1).
- Do we need a separate AI Act technical file?
- No. Article 11(2) requires a single set of technical documentation for products under Annex I Section A. The AI Act information of Annex IV is added to the MDR or IVDR file.
- From when do the AI Act requirements apply to devices?
- From August 2, 2028, as amended by Regulation (EU) 2026/1744. The MDR and IVDR requirements apply already.
- Does a significant change under the MDR equal a substantial modification under the AI Act?
- Not automatically. MDCG 2025-6 treats substantial modification as an autonomous AI Act concept. Changes the provider pre-determined and documented at the initial assessment are not a substantial modification (Article 43(4)).
Sources
- Regulation (EU) 2024/1689 (Artificial Intelligence Act) — EUR-Lex, 12 July 2024Law in force: Binding legislation that applies as of the review date.
- Regulation (EU) 2026/1744 (Digital Omnibus on AI), amending Regulation (EU) 2024/1689 — EUR-Lex, 24 July 2026Law in force: Binding legislation that applies as of the review date.
- Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, 5 May 2017Law in force: Binding legislation that applies as of the review date.
- Regulation (EU) 2017/746 on in vitro diagnostic medical devices (IVDR) — EUR-Lex, 5 May 2017Law in force: Binding legislation that applies as of the review date.
- MDCG 2025-6 / AIB 2025-1: FAQ on the interplay between the MDR/IVDR and the AI Act — Medical Device Coordination Group and Artificial Intelligence Board, 19 June 2025Final guidance: Guidance published in its final form by an authority or an official body. Guidance explains the law; it is not law itself.
Review log and changes
Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.
Reviewed
No corrections or additions since publication.