Short answer
EU MDR technical documentation (the technical file) is the structured body of evidence, defined in Annex II, that shows a device meets the MDR; Annex III adds the post-market surveillance documentation: the PMS plan, and the PSUR for class IIa and above or the PMS report for class I. For SaMD it includes the device description with the Rule 11 classification rationale, IEC 62304 lifecycle records and a SOUP list, a GSPR checklist mapped to the software requirements of section 17, the ISO 14971 risk management file, a clinical evaluation following MDCG 2020-1, and usability and cybersecurity evidence. A Notified Body assesses it for class IIa, IIb and III.
1. What is EU MDR technical documentation?
EU MDR technical documentation — commonly called the technical file — is the complete body of evidence that demonstrates your medical device meets all applicable requirements of EU MDR 2017/745. It is not a single document but a structured collection of documents, test reports, analyses, and records that the manufacturer keeps up to date and that a Notified Body assesses as part of conformity assessment for class IIa, IIb and III devices.
The structure is defined by two Annexes of EU MDR:
- Annex II — Technical documentation. The main technical file covering device description, design, verification, clinical evaluation, and post-market planning.
- Annex III — Technical documentation on post-market surveillance: the post-market surveillance (PMS) plan, and the periodic safety update report (PSUR) or, for class I devices, the post-market surveillance report, maintained throughout the device lifecycle.
For SaMD, the technical file has the same mandatory structure as any medical device — but the content of each section looks fundamentally different from a hardware device. In our experience, many problems in Notified Body reviews start when software companies populate hardware-oriented templates without understanding what software-specific evidence each section actually requires.
All CE-marked medical devices need Annex II and Annex III technical documentation. For class I SaMD (without a measuring function), the manufacturer declares conformity itself (Article 52(7)) — no Notified Body reviews the file, but it must exist and be kept available to competent authorities. Class IIa, IIb and III SaMD go through Notified Body conformity assessment, which includes assessment of the technical documentation — for class IIa and IIb on a sampling basis (representative devices per category or generic device group), for class III for each device — before a certificate is issued and the CE mark can be affixed.
2. Annex II — complete section-by-section breakdown
Annex II of EU MDR 2017/745 contains six numbered sections. Here is what each requires, and what "complete" looks like for a SaMD:
| Annex II section | What it requires for SaMD | Key standards |
|---|---|---|
| 1. Device description & specification | Intended purpose, intended users, intended patient population, contraindications, device variants, software version(s), the rationale for qualification as a device, the risk class with justification of the classification rule(s) applied (usually Rule 11), Basic UDI-DI. For SaMD: algorithm description, input/output specification, hardware dependencies. | MDCG 2019-11 |
| 2. Information supplied by manufacturer | All labelling (including software version labelling), Instructions for Use. For SaMD: the IFU must state the minimum requirements concerning hardware, IT network characteristics and IT security measures needed to run the software as intended (Annex I §23.4(ab)); in practice it should also explain what AI/ML outputs mean and their limitations. | Annex I §23 |
| 3. Design & manufacturing information | For SaMD: software architecture description, development environment, programming languages, IEC 62304 software safety class justification, SOUP list with version and risk assessment, change management procedures, build and release process. | IEC 62304 |
| 4. GSPR — General Safety & Performance Requirements | A checklist mapping every applicable GSPR from Annex I of EU MDR to the specific evidence in your technical file. For SaMD: must address §17 (electronic programmable systems and software that are devices in themselves), the relevant parts of §18 (active devices — software is deemed an active device), §14 where the software interacts with IT environments, and §23 (label and IFU). For each requirement, state whether it applies (with a justification where it does not), the method used to demonstrate conformity and the specific document references. | Annex I |
| 5. Benefit-risk analysis & risk management | Complete risk management file per ISO 14971:2019, covering the full lifecycle. For SaMD: must include software-specific hazards (algorithmic errors, incorrect outputs, cybersecurity threats, usability failures). Risk management must address residual risks and demonstrate overall benefit-risk acceptability. | ISO 14971:2019 |
| 6. Product verification & validation | Results of all V&V activities: software verification and validation (Annex II §6.1(b)) — unit, integration, system and regression testing — usability engineering file with summative evaluation per IEC 62366-1, cybersecurity testing (guidance: MDCG 2019-16), the clinical evaluation plan and report, the PMCF plan and evaluation report (or a justification why PMCF is not applicable), and — for AI/ML — algorithm validation across the intended patient population. | IEC 62304, IEC 62366 |
In our experience, Section 4 (GSPR checklist) and Section 6 (V&V, especially the CER) attract the most Notified Body questions for SaMD. A superficial GSPR checklist with vague references and a CER that treats software like a hardware device will not hold up, however good the software itself is.
3. SaMD-specific requirements not in hardware files
The following documentation areas are either absent from hardware device templates or substantially more demanding for SaMD. If you are adapting an off-the-shelf technical file template, these sections need to be built from scratch:
Software architecture documentation
A description of the software's architecture is required under Section 3 and referenced throughout the technical file. For SaMD this means: architecture diagrams showing major components and their interfaces, data flow documentation, description of external systems the software communicates with, and identification of software items that contribute to safety. The architecture description is the backbone that the GSPR checklist, risk management, and V&V results all reference.
IEC 62304 software lifecycle documentation
EU MDR does not directly reference IEC 62304 — but Annex I §17.2 requires that software be developed and manufactured in accordance with the state of the art, taking into account the principles of development life cycle, risk management (including information security), verification and validation. IEC 62304 is the internationally recognised standard for this, and your Notified Body will expect it. The IEC 62304 documentation set includes: software development plan, software requirements specification, software architecture design, unit implementation and verification records, software integration testing records, and software system testing records. The class (A, B, or C) you assign to your software determines which of these are mandatory.
SOUP list (Software of Unknown Provenance)
Every open-source library, third-party component, operating system, database, and framework your software depends on must be listed with version number, published known anomalies, and risk assessment. In our experience, a missing or incomplete SOUP list is one of the most frequent Notified Body findings. If your software uses React, PostgreSQL, TensorFlow, or any other open-source dependency — it belongs in the SOUP list.
Cybersecurity documentation
The cybersecurity requirements themselves are in Annex I (§17.2, §17.4, §18.8 and §23.4(ab)); MDCG 2019-16 Rev.1 is the guidance on how to meet them. For SaMD, this means a dedicated security section covering: threat modelling, security risk assessment, secure development practices, penetration testing or vulnerability assessment, and post-market security monitoring plan. In our experience, a one-page reference to "following best practices" does not pass review.
Usability engineering file
Annex I §5 requires manufacturers to reduce risks related to use error as far as possible, and IEC 62366-1 is the recognised way to show this — Notified Bodies expect a usability engineering file for SaMD. It should include: intended use context analysis, identification of use-related hazards, formative evaluation evidence (user testing during development), and summative evaluation (final formal validation with representative users). The summative evaluation must demonstrate that use errors identified in the risk assessment are adequately mitigated. In our experience, this is one of the sections most often absent or incomplete in SaMD technical files.
Clinical evaluation report for SaMD
In our experience the CER is the most challenging section and the one most often sent back for rework. For SaMD, the clinical evaluation should follow MDCG 2020-1 guidance, which structures the evidence for software into three components: valid clinical association (scientific validity) of the output, technical performance, and clinical performance — each supported by appropriate sources such as literature, guidelines, verification and validation testing, real-world data or clinical studies. A CER that treats your software like a hardware implant — citing material biocompatibility studies, for example — will not convince a reviewer.
4. Annex III — post-market documentation
Annex III covers the technical documentation on post-market surveillance. The PMS plan must be in place before the device is placed on the market; the PSUR (or, for class I, the PMS report) is produced from the data collected once the device is on the market. A third document, the SSCP, is required by Article 32 for some devices — not by Annex III — and is covered here because it is closely linked.
PMS plan (all classes)
The Post-Market Surveillance plan defines how you will proactively collect and analyse real-world data on your device's safety and performance after market placement. For SaMD this must include: monitoring of bug reports and user-reported issues, tracking of software updates and their effect on clinical performance, monitoring of relevant scientific literature, and — for AI/ML software — continuous monitoring of algorithm performance metrics including accuracy drift and subgroup performance. The PMS plan must be specific and measurable; generic statements about "monitoring user feedback" do not satisfy the requirement.
PSUR (Class IIa, IIb, III)
The Periodic Safety Update Report (Article 86) summarises the results and conclusions of the analysis of the data collected under the PMS plan, including the conclusions of the benefit-risk determination, the main findings of the PMCF, and sales and user-population data. Class IIa devices: updated when necessary and at least every two years. Class IIb and III: at least annually (see also MDCG 2022-21). For class III devices the PSUR is submitted to the Notified Body via the electronic system; for class IIa and IIb it is made available to the Notified Body and, on request, to competent authorities. Class I devices need a post-market surveillance report (Article 85) instead.
SSCP (class III and implantable devices — Article 32)
The Summary of Safety and Clinical Performance is required for implantable devices and class III devices (other than custom-made or investigational devices). Its draft is validated by the Notified Body and it is made available to the public via EUDAMED. It summarises, among other things, the intended purpose, residual risks, the clinical evaluation and PMCF, written so that the intended user — and, where relevant, the patient — can understand it. For standalone software this in practice means class III SaMD; class IIa and IIb SaMD do not need an SSCP. Since 28 May 2026 the first four EUDAMED modules (actor registration, UDI/device registration, notified bodies and certificates, and market surveillance) are mandatory, with transition arrangements for devices already on the market; the vigilance module is not yet mandatory.
5. The 8 gaps we see most often in SaMD technical files
Based on technical file reviews and Notified Body feedback in our own SaMD projects, these are the reasons we most often see a technical file fail or require major revision:
6. Technical documentation checklist for SaMD
Use this checklist to assess the completeness of your technical file before submitting to a Notified Body. Every item must be present, current, and cross-referenced.
Annex II — core sections
- Device description — intended purpose, intended users, contraindications, software version(s), Basic UDI-DI, qualification rationale, Rule 11 classification justification with documented rationale
- Labelling & IFU — compliant with Annex I §23, version-controlled, includes minimum hardware, IT network and IT security requirements, AI/ML output limitations where applicable
- Software architecture — architecture diagram, component descriptions, external interfaces, data flows, identification of safety-critical software items
- IEC 62304 documentation set — development plan, SRS, architecture design, unit/integration/system test records, safety class justification
- SOUP list — all third-party components with version, licence, known anomalies review, risk assessment per component
- GSPR checklist — all Annex I requirements assessed (applicable / not applicable with justification / complied with via specific document reference), §17 and the relevant §18 items fully addressed
- ISO 14971:2019 risk management file — risk management plan, hazard identification, risk estimation, risk evaluation, risk controls, residual risk assessment, benefit-risk conclusion, includes software-specific hazards
- Cybersecurity documentation — threat model, security risk assessment, secure development evidence, penetration testing / vulnerability assessment results, post-market security monitoring plan (Annex I §17.2, §17.4, §18.8; guidance MDCG 2019-16)
- Usability engineering file — use context analysis, use-related hazard identification, formative evaluation records, summative evaluation protocol and results (IEC 62366-1)
- Clinical evaluation plan and report — MDCG 2020-1 approach (valid clinical association, technical performance, clinical performance), literature review, clinical performance data for the specific software, PMCF plan and evaluation report or justification why PMCF is not applicable
Annex III — post-market documentation
- PMS plan — proactive data collection methods, indicators and thresholds, complaint handling, vigilance and trend reporting procedures, PMCF plan or justification, AI/ML performance monitoring metrics where applicable
- PSUR / PMS report — process and schedule defined before market placement; PSUR for class IIa (at least every two years) and IIb/III (at least annually); PMS report for class I
- SSCP — class III (and implantable) devices only; validated by the Notified Body; made public via EUDAMED
SaMD-specific additions (AI/ML software)
- Algorithm description — model architecture, training methodology, performance metrics on validation dataset, subgroup performance analysis
- Training data governance — dataset description, inclusion/exclusion criteria, demographic representativeness, bias assessment. Expected today as part of MDR validation evidence; for AI medical devices that need Notified Body assessment, the EU AI Act's data governance requirements (Article 10) will also apply from 2 August 2028 (date set by Regulation (EU) 2026/1744)
- Change management procedure — defines when a software change or model update constitutes a significant change requiring NB notification or new conformity assessment
7. How long does it take — realistic timelines
How long the technical file takes depends heavily on what documentation already exists, on the device class, and on whether new clinical data has to be generated. Rather than quote generic durations, here is where the time usually goes for each starting point:
| Starting point | Main bottleneck |
|---|---|
| No prior regulatory documentation | Retrospective IEC 62304 documentation, risk management file, clinical evidence for the CER |
| ISO 13485 QMS in place, no technical file | CER, usability summative evaluation |
| Prior MDD technical file, transitioning to MDR | CER rebuild to MDR standards, GSPR mapping, cybersecurity gap |
| Existing MDR file with specific gaps | Depends on gap type — gaps in clinical evidence usually take longest |
In our experience, the Clinical Evaluation Report is the element that most often determines the overall schedule. Where suitable clinical performance data already exists, the work is mainly analysis and writing; where your class or claims require new clinical data, generating that evidence can take far longer than writing any other part of the file. Start the clinical evaluation first, in parallel with everything else. For the full certification picture, including Notified Body review time, see our guide to a realistic EU MDR timeline for software.
The fastest path to a complete technical file is a structured gap analysis at the start — before any writing begins. A technical documentation audit identifies exactly which sections exist, which need to be created from scratch, and which existing documents need to be updated. This prevents the most expensive mistake in SaMD certification: spending months writing documentation only to discover it doesn't meet NB requirements at submission.
For teams building their ISO 13485 QMS in parallel with the technical file — which is the typical path for software startups — coordinating QMS procedures with technical file requirements avoids writing the same content twice and shortens the overall programme. The SOUP management procedure, change management procedure, and risk management procedure in your QMS generate outputs that go directly into the technical file.