Encyclopedia · Subject area
Medical-device documentation
Medical-device documentation comprises the records with which manufacturers of medical devices and in vitro diagnostic devices demonstrate safety, performance and clinical benefit and keep that demonstration current. This subsection treats it as an evidence system and describes seven of its domains — the technical file, design controls and design history, risk management to labeling, clinical and performance evidence, software and AI lifecycle documentation, the comparison of EU and FDA documentation, and post-market evidence — and examines how their relationships form one chain of evidence.
By knowledge.aitechdoc.world · Last reviewed
Articles
- Technical documentation as an evidence systemThe technical file of a medical device as an evidence system: MDR and IVDR Annexes II and III, consistency as evidence, and what structure can provide.Read the article
- Design controls and design historyDesign controls and their records: DHF, DMR and DHR as practice terms after the FDA QMSR, and the medical device and design files of ISO 13485.Read the article
- Risk management to labelingFrom hazard to IFU warning: ISO 14971:2019 risk control priority, information for safety, IEC 62366-1 and the traceability of warnings in labeling.Read the article
- Clinical and performance evidenceClinical evaluation, PMCF and IVDR performance evaluation as evidence, the clinical benefit, and why claims are controlled statements that need evidence.Read the article
- Software and AI lifecycle documentationIEC 62304, SOUP, SaMD and AI-enabled device software functions; PCCPs, the AI Act and one technical file for AI medical devices.Read the article
- EU and FDA documentation comparedEU technical documentation and notified bodies vs. FDA 510(k), De Novo and PMA; QMSR vs. ISO 13485, PCCP vs. EU change rules, EUDAMED vs. GUDID.Read the article
- Post-market evidencePost-market surveillance, PSUR, PMCF, vigilance, trend reporting and CAPA, FDA medical device reporting, and how post-market signals update the documentation.Read the article
Scope and terminology
The subsection covers the EU Medical Devices Regulation (EU) 2017/745 (MDR), the In Vitro Diagnostic Medical Devices Regulation (EU) 2017/746 (IVDR), the requirements of the US Food and Drug Administration and, for devices that use artificial intelligence, the EU AI Act (Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744). It refers to the standards most often applied — ISO 13485, ISO 14971, IEC 62304 and IEC 62366-1 — without restating them. Pharmaceutical good practices (GxP) and ICH guidelines are covered in the glossary and are outside this subsection except where they meet device documentation.
The sources differ in status: regulations are binding law, MDCG documents and FDA guidance explain the law without being law, standards are voluntary unless a law makes them mandatory, and proposals such as the targeted revision of the MDR and IVDR are not applicable law. The articles state which kind of source each statement rests on and give facts as of their review date.
Common characteristics
All seven domains produce statements that depend on each other: the intended purpose determines classification, clinical evidence and risk management; risk controls determine warnings; verification and clinical data support claims; post-market data revise all of them. None of the domains, and no form of documentation, establishes conformity on its own; conformity is assessed against the applicable requirements and the evidence.
Comparison
| Type | Question answered | Central record | Main sources | Typical relationships | Main limitation |
|---|---|---|---|---|---|
| Technical documentation as an evidence system | Does the device meet its requirements? | Technical documentation (MDR/IVDR Annexes II and III) | MDR, IVDR, MDCG guidance | Intended purpose → GSPR → evidence | Completeness of documents ≠ completeness of evidence |
| Design controls and design history | How was the design derived and verified? | Design and development file, medical device file (DHF, DMR, DHR in practice) | ISO 13485, FDA QMSR | User need → input → output → verification → validation | Former QSR terms are no longer regulatory terms |
| Risk management to labeling | Which risks remain and how are they controlled? | Risk management file, usability engineering file | ISO 14971, IEC 62366-1, MDR Annex I | Hazard → hazardous situation → risk control → warning | Information for safety is the last option |
| Clinical and performance evidence | Does the device achieve its clinical benefit? | Clinical evaluation or performance evaluation report | MDR Article 61 and Annex XIV, IVDR Annex XIII | Claim → clinical data → benefit-risk | Evidence is specific to purpose and configuration |
| Software and AI lifecycle documentation | Which software and model produced which device? | Software lifecycle records, AI data and model records | IEC 62304, AI Act, FDA PCCP and CDS guidance | Model version → software version → device version | No format makes a changing model safe |
| EU and FDA documentation compared | How do the EU and the USA organize the evidence? | Technical file vs. premarket submission | MDR, IVDR, FD&C Act, 21 CFR | One body of evidence, several views | Same names, different scope |
| Post-market evidence | What has the market shown since? | PMS plan and reports, PSUR, PMCF/PMPF, vigilance records | MDR Articles 83–92, 21 CFR Parts 803 and 806 | Signal → affected versions → risks and claims → texts | Data are not evidence until evaluated |
How the domains interoperate
The seven domains form one chain: requirement → risk → control → verification → clinical evidence → claim → label and instructions for use → post-market evidence, with the product and software version running alongside every link. Each domain produces part of the chain and consumes the parts of others.
The intended purpose as reference point
The intended purpose is stated once and used everywhere: in classification, in the design inputs, in the risk analysis, in the clinical evaluation, in the instructions for use and in the post-market surveillance plan. When it changes, every dependent statement has to be checked. Documentation systems that hold it as a controlled element with links to its uses make this check possible; systems that repeat it as free text in many documents rely on manual comparison.
From risk to text
Risk management decides which risks are controlled by information for safety. Usability engineering verifies that the information works. The labeling then carries the text, and the clinical evaluation must be consistent with it. A warning in the instructions for use is therefore the visible end of a chain that runs back through the usability engineering file and the risk management file to the hazard.
From version to evidence
Design controls and software lifecycle records identify each released configuration. Verification, clinical evidence and claims hold for specific configurations. For AI-enabled devices, the model version and its training and test data become part of this identification, and a planned change under a PCCP or a predetermined change under the AI Act is documented against it.
From market back to the file
Post-market surveillance feeds signals back into risk management, clinical evaluation, labeling and design. The scope of each update follows the same relationships in reverse.
Retrieval and AI use
Where AI systems are used to search, summarize or answer from a technical file, the reliability of the answer depends on these relationships: on knowing which version a statement applies to, whether the text was released, which evidence supports it and who may see it. Structure, metadata and controlled terminology are preconditions; review and release remain human decisions. No retrieval or generation function changes what the evidence shows or what the law requires.