Glossary Updates16 new terms added to the glossaries · November 12, 2026, 21:23 CET
AI TechDocKnowledge

Medical-device documentation

Technical documentation as an evidence system

Also known as: Technical file (medical devices) · Technical documentation (MDR and IVDR) · Technical file as an evidence system

The technical documentation of a medical device or an in vitro diagnostic device is the body of information with which a manufacturer demonstrates that the device meets the general safety and performance requirements that apply to it. Under the EU MDR and IVDR its content is set out in Annexes II and III. Although it is often handled as a set of documents, its function is that of an evidence system: its value depends on whether its statements are consistent with each other and can be traced to the evidence behind them.

By knowledge.aitechdoc.world · Last reviewed

Definition

In the EU, the technical documentation required by Article 10(4) MDR and Article 10(4) IVDR describes the device and the evidence of its conformity. Annex II of each regulation lists its content: device description and specification, including the intended purpose; information to be supplied by the manufacturer (label and instructions for use); design and manufacturing information; the general safety and performance requirements (GSPR) with the methods used to demonstrate conformity; the benefit-risk analysis and risk management; and product verification and validation, including the clinical evaluation or performance evaluation. Annex III adds the technical documentation on post-market surveillance.

Historical development

Under the Medical Devices Directive 93/42/EEC and the IVD Directive 98/79/EC, the content of the technical file was described only in general terms, and practice varied between manufacturers and notified bodies. Summary formats such as the Global Harmonization Task Force's Summary Technical Documentation (STED) sought a common structure. The MDR and IVDR, applicable since May 26, 2021 and May 26, 2022 respectively (with transitional provisions for existing devices), fixed the structure in their annexes and linked it to the GSPR in Annex I.

Components

  1. Intended purpose and device description. The intended purpose (Article 2(12) MDR) defines the use for which the device is intended and is the reference point for classification, clinical evidence, risk management and labeling.
  2. GSPR checklist. A record of each applicable requirement, the standards or common specifications applied and the documents that contain the evidence.
  3. Risk management file. Hazards, hazardous situations, risk controls and the benefit-risk determination, usually following ISO 14971.
  4. Verification and validation. Test reports, software documentation, usability engineering and biocompatibility evaluation.
  5. Clinical or performance evidence. The clinical evaluation report (MDR) or performance evaluation report (IVDR) and their plans.
  6. Information supplied with the device. Label, instructions for use and, where required, the summary of safety and clinical performance.
  7. Post-market documentation. The post-market surveillance plan and its outputs, which feed back into all other parts.

Function and purpose

The technical documentation serves the manufacturer's own control of the device and the assessment by the notified body or the competent authority. Reviewers follow a statement — for example a performance claim in the instructions for use — to the risk management, the verification and the clinical data that support it. Where two parts of the file state different intended purposes, populations, contraindications or performance values, the evidence for at least one of them is missing. Consistency is therefore not an editorial property of the file but part of the evidence it provides.

Information architecture

The relationships within the file — between intended purpose, claims, GSPR, risks, controls, tests, clinical data, labeling and post-market data — can be held implicitly in cross-references between documents or explicitly in a traceability structure, a database or a content model with typed links. Explicit relationships make inconsistencies detectable and allow a change to be followed to every affected statement. They also determine what a retrieval or answer function can reliably return from the file: a warning found in an instructions-for-use text is reliable only when its link to the risk, the risk control, the verification, the device version and the released language version is known. Structure supports this; it does not replace the evidence or the review.

Limitations

A complete set of documents does not guarantee complete evidence. A checklist can name a test report that does not cover the configuration placed on the market, and a structured content model can reuse a warning in a version for which it was never verified. Conformity is assessed against the regulations and the evidence, not against the form of the documentation.

Conclusion

Treating the technical documentation as an evidence system shifts attention from the presence of documents to the relationships between statements and evidence. Those relationships are what reviewers navigate, what change control must maintain and what any automated retrieval from the file depends on.

Further reading

Cite this article

knowledge.aitechdoc.world. “Technical documentation as an evidence system.” Encyclopedia, AI TechDoc Knowledge. Last reviewed November 10, 2026. https://knowledge.aitechdoc.world/encyclopedia/medical-device-documentation/technical-documentation-as-an-evidence-system