What is the Technical File?

The Technical File is the collection of documents that provides the technical evidence that a medical device meets all applicable requirements of EU MDR Annex I (General Safety and Performance Requirements). For Class IIa and above devices, the Technical File is reviewed by a Notified Body as part of conformity assessment. For Class I self-declared devices, the Technical File must exist and be made available to market surveillance authorities on request — but is not proactively reviewed. The Technical File is not a static document: it must be updated throughout the device's commercial life whenever changes occur that affect safety, performance, or regulatory status.

MDR Technical Documentation Structure (Annex II)

EU MDR Annex II defines the required content of Technical Documentation. The main sections are: (1) Device description and specification — including accessories, variants, and previous generations; (2) Information to be supplied by the manufacturer — labelling, IFU, and promotional materials; (3) Design and manufacturing information — design stages, manufacturing processes, and production controls; (4) General Safety and Performance Requirements (GSPR) checklist — a clause-by-clause demonstration of compliance with Annex I; (5) Benefit-risk analysis and risk management — referencing the ISO 14971 risk management file; (6) Product verification and validation — performance testing, biocompatibility, sterility, shelf life, electrical safety, and all other applicable tests; (7) Clinical evaluation — the Clinical Evaluation Report (CER) and supporting clinical evidence; (8) Post-Market Surveillance documentation — PMS Plan and reports.

The GSPR Checklist: The Spine of the Technical File

The General Safety and Performance Requirements (GSPR) checklist is one of the most important documents in the Technical File. It maps each applicable requirement of MDR Annex I to the evidence demonstrating compliance — typically referencing harmonised standards, common specifications, test reports, and design documents. A complete GSPR checklist demonstrates to the Notified Body that the manufacturer has systematically considered every relevant safety and performance requirement and has documentary evidence for each. Requirements marked as 'not applicable' must include a justification for why they do not apply to the specific device.

Clinical Evaluation Report (CER): The Most Scrutinised Section

The Clinical Evaluation Report is typically the most intensively reviewed section of the Technical File for Class IIa and above devices. The CER must demonstrate that the device achieves its intended clinical performance and that the clinical benefits outweigh the risks. Under EU MDR MDCG 2020-6 guidance, the CER must include: a scope definition, a literature search protocol and results (systematic searches of PubMed, EMBASE, etc.), appraisal and analysis of the identified literature, clinical performance data (from clinical investigations or equivalent device data), and a benefit-risk conclusion. Notified Bodies consistently identify inadequate clinical evaluation as the most common Technical File deficiency for Class IIa and IIb devices.

Harmonised Standards: Using Them Correctly

Compliance with harmonised standards (published in the Official Journal of the EU) creates a presumption of conformity with the MDR requirements they cover. This means that if your device passes testing according to IEC 60601-1 (general electrical safety), EN ISO 11135 (EtO sterilisation), or IEC 62366-1 (usability engineering), you gain a presumption that the corresponding MDR Annex I requirements are met. The harmonised standard reference, the test report reference, and any deviations from the standard must be documented in the GSPR checklist. Note: standards must be current — citing superseded standard versions without justification is a common audit finding.

Common Technical File Deficiencies

The most frequently cited Technical File deficiencies in Notified Body reviews are: (1) Incomplete or generic GSPR checklist — requirements addressed with statements rather than evidence; (2) Inadequate CER — literature search not systematic, no search protocol documented, insufficient clinical evidence for the device's intended purpose; (3) Risk management file not aligned with ISO 14971:2019 — older versions used, benefit-risk analysis missing; (4) Outdated harmonised standards referenced — test reports citing superseded standard versions; (5) Labelling not fully compliant with MDR Annex I Section 23 — missing required symbols, missing UDI, incorrect language requirements; (6) No PMCF Plan or PMCF Evaluation Report; (7) Post-market surveillance documentation absent or generic.

Conclusion

The Technical File is the tangible evidence that a Turkish medical device manufacturer has done the work required to prove their device is safe and performs as intended. Manufacturers who invest in building a genuinely complete, well-evidenced Technical File — starting from a thorough GSPR checklist, systematic clinical evaluation, and current risk management file — will have faster, less expensive CE marking certification and a stronger foundation for market surveillance and post-certification audits throughout the device's commercial life.