Context card
A medical-device technical file is not a collection of documents. It is an evidence system.
What makes a medical-device technical file an evidence system rather than a set of documents?
The short answer
The links between its parts. MDR Annexes II and III ask for documents — device description, labeling, design and manufacturing information, GSPR, benefit-risk and risk management, verification and validation, post-market surveillance — but the file only works when each requirement points to the risk control, the test and the clinical data that answer it, and when those links are kept current. What a notified body navigates to follow that chain is what an answer function would need to retrieve.
For: Technical writers, regulatory affairs and quality managers in MedTech; documentation systems developers
Key points
- Annex II lists the content; the GSPR checklist is where the links become visible.
- Each applicable GSPR points to the method, the standard and the controlled document that demonstrates it.
- Risk management links hazards to controls and controls to their verification.
- Annex III adds the post-market side: PMS plan, PMCF and PSUR feed back into the file.
- A file is navigable when a reader can go from any claim to its evidence and back.
The context
Documents and links
MDR technical documentation is defined in Annex II (device description and specification, information supplied by the manufacturer, design and manufacturing information, the GSPR, benefit-risk analysis and risk management, product verification and validation including the clinical evaluation) and Annex III (the post-market surveillance documentation). The IVDR mirrors the structure. Read as a list, it is a set of documents. Read as the regulator reads it, it is a set of answers with their proof.
The chain inside the file
- The intended purpose sets what has to be proven.
- Each applicable GSPR names the method of demonstration, the standards applied and the controlled document that holds the evidence.
- ISO 14971 risk management links each hazard to its risk controls and each control to the verification of its implementation and effectiveness.
- Verification and validation and the clinical evaluation support the claims (claims matrix).
- Labeling and IFU carry the information for safety that is itself a risk control.
- PMCF, the PSUR and vigilance bring new evidence back.
In the USA, the QMSR now incorporates ISO 13485 by reference (from February 2, 2026); the design history file is a practice term there, and ISO 13485 speaks of the medical device file. The logic of the chain is the same.
What a notified body navigates
A reviewer starts from a GSPR or a claim and follows the references until the evidence is found — or not. Gaps appear as broken references, outdated document versions and wordings that do not match. An answer function asked "what proves that this warning works?" needs exactly the same chain: it can only answer if the links exist and are current.
Consequence for documentation work
Build the file as linked objects with identifiers and versions, not as a folder of PDFs. Keep the links in the quality system's change control, so a change shows every document it touches. The evidence chain map draws the stations; the encyclopedia topic explains the documents.
What this card does not say
It describes the structure of the evidence, not what is sufficient for a device. The MDR and IVDR annexes, the harmonized standards and the notified body's assessment decide that.
Questions readers ask next
- Is there a required structure for the technical file?
- The content is set by MDR Annexes II and III (IVDR Annexes II and III). The order and the tools are the manufacturer’s choice, as long as the file is clear, organized, readily searchable and unambiguous, as Annex II requires.
- Is the technical file the same as the design history file?
- No. The design history file is a practice term from the former FDA QSR for the design records; the EU technical file covers the whole device including labeling, clinical evaluation and post-market documentation.
Sources
- Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, May 5, 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, May 5, 2017Law in force: Binding legislation that applies as of the review date.
- EN ISO 14971:2019/A11:2021 Medical devices — Application of risk management to medical devices — ISO / CEN, December 2019Harmonized standard (cited): A harmonized standard whose reference is published in the Official Journal of the EU; applying it can give a presumption of conformity for the requirements it covers.
- 21 CFR Part 820, Quality Management System Regulation — eCFR, February 2, 2026Law in force: Binding legislation that applies as of the review date.
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.