The Medical Device File: What You Don’t Have to Include in This File
ISO 13485 requires a medical device file for each medical device type or medical device family. A lot of many manufacturers think that the medical device file is the same as the technical documentation required by the MDR or IVDR. But that isn’t entirely true.
Is one of the three files required by the FDA (DMR, DHF, DHR) the same as the medical device file? It's time for a comparison to end unnecessary discussions within your team and with auditors. With a free download.
1. The medical device file: what ISO 13485 aims for and demands
ISO 13485 has required a medical device file since the 2016 edition. The aim of this is to ensure that manufacturers create (and maintain) all the documents required to demonstrate compliance with the regulatory requirements.
The standard talks about “compliance with applicable regulatory requirements.” By this, it means the requirements of, for example, the MDR and IVDR, for medical devices placed on the market in Europe. For devices regulated by the FDA, this would refer, for example, the requirements of 21 CFR part 820.
However, ISO 13485 is not limited to referring to other regulations. In fact, it defines which documents the medical device file must (at least) contain, regardless of the jurisdiction.
2. Medical device file versus technical documentation versus “FDA files”
a) MDR, IVDR: Technical documentation
Annex II of the Medical Device Regulation (MDR) and Annex II of the EU Regulation on In Vitro Diagnostic Medical Devices (IVDR) both specify the requirements for the technical documentation. The post-market surveillance (PMS) plans defined in Annex III in both regulations are also considered part of the technical documentation.
Further information
Read more on the subject of the technical documentation here.
b) FDA: DHF DMR, DHR,
The FDA distinguishes between three different files:
- Design history file (DHF) according to 21 CFR part 820.30
- Device master record (DMR) according to 21 CFR part 820.181
- Device history record (DHR) according to 21 CFR part 820.184
c) Comparison of the files
The following table compares these requirements.
Document | Medical device file according to ISO 13485:2016 | Ref. ISO 13485 | Technical documentation according to MDR/IVDR | Ref. MDR | FDA: DMR, DHF, DHR |
General description of the device | X | 4.2.3 a) | X (incl. names) | II.1.1.a) |
|
Variants | X*) |
| X | II.1.1. i) |
|
Language versions | X*) |
| X |
|
|
Intended accessories and combinations with other devices | X*) |
| X | II.1.1. h) |
|
Intended purpose and intended use | X | 4.2.3 a) | X (incl. user, patient group, (contra-) indications) | II.1.1 a), c) | 21 CFR part 820.30 |
Warnings |
|
| X | II.1.1. c) |
|
Qualification as medical device |
|
| X | II.1.1.e) |
|
Classification | X*) |
| X | II.1.1. f) |
|
Mode of action, scientifically demonstrated if necessary, functionality |
|
| X | II.1.1. d) |
|
Description of novel features |
|
| X | II.1.1 g) |
|
Reference to previous and similar devices |
|
| X | II.1.2. a), b) | e.g., for 510(k) approval |
Description of the development stages |
|
| X | II.3. a) | 21 CFR part 820.30 b) |
Device specifications, e.g., drawings, calculations, components | X | 4.2.3 b) | X (incl. dimensions, performance attributes) | II.1.1. j), l) | 21 CFR part 820.181 a) |
Software specifications | X*) |
| X | II.6.1 b) | 21 CFR part 820.181 a) |
Relevant GSPR |
|
| X | II.4. a) |
|
Materials used, design drawings | X*) |
| X (incl. those in contact with the body) | II.1.1 j) | 21 CFR part 820.181 a) |
Medicinal products used | X*) |
| X | II.1.1. k), II.6.2. a) |
|
Tissues of human or animal origin used |
|
| X | II.6.2 b) |
|
Toxicity, biological safety, and biocompatibility | X*) |
| X | II.6.1 b), II.6.2. d) | (21 CFR part 820.181 c)), 21 CFR part 820.184 d) |
Physical, chemical, microbiological, electrical safety |
|
| X | II.6.1 b) | (21 CFR part 820.181 c)), 21 CFR part 820.184 d) |
Absorption, metabolism, excretion, interaction, tolerance of substances in the body |
|
| X | II.6.2 c) |
|
Lifetime, stability, shelf life |
|
| X | II.6.1 b) | 21 CFR part 820.184 d) |
Measurement accuracy (in case of measuring function) |
|
| X | II.6.2.ef)[A1] | 21 CFR part 820.184 d) |
Interoperability, compatibility |
|
| X | II.6.2.g) | (21 CFR part 820.181 c)) |
Software V&V results |
|
| X | II.6.1 b) | 21 CFR part 820.30 |
Specifications for manufacture, e.g., requirements for facilities, infrastructure, production methods | X | 4.2.3 c) | (incl. adjuvants, processes, validation) | II.3. b) | 21 CFR part 820,181 b) |
Quality assurance requirements, e.g., procedures, equipment, acceptance criteria | X*) |
| X | II.6.1 (and others) | 21 CFR part 820.181 c) |
Details of suppliers and contractors with their activities |
|
| X | II.3. c) |
|
Packaging specifications, e.g., methods, processes, materials | X | 4.2.3 c) | X |
| 21 CFR part 820.181 d) |
Specifications (procedures) for measuring and monitoring | X | 4.2.3 d) |
|
| (21 CFR part 820.181 c)) |
Requirements for post-market surveillance (PMS), particular the PMS Plan |
|
| X | III |
|
Design outputs | X*) |
| X | II.6. (and others) |
|
Tests, e.g., laboratory, simulation, animal testing |
|
| X | II.6.1 a) | (21 CFR part 820.181a)), 21 CFR part 820.184 d) |
Clinical data | X*) |
| X | II.6.1 c) |
|
Clinical evaluation incl. CER plan |
|
| X | II.6.1 c) |
|
PMCF plan |
|
| X | II.6.1 d) |
|
Risk management, e.g., risk analysis, risk-minimizing measures, list of residual risks, risk-benefit evaluation | X*) |
| X | II.5. a), b) |
|
Storage requirements | X | 4.2.3 c) |
|
|
|
Specifications for transport | X*) | 4.2.3 c) |
|
|
|
Specifications for distribution | X | 4.2.3 c) |
|
|
|
Requirements for installation | X | 4.2.3 e) |
|
| 21 CFR part 820.181e) |
Requirements for maintenance and servicing | X | 4.2.3 f) |
|
| 21 CFR part 820.181d) |
Instructions for use | X | 4.2.3 c) | X | II.2. |
|
Other labeling | X | 4.2.3 c) | X (packaging) | II.2. |
|
UDI | X*) |
| X (Basic UDI) | II 1.1. b) |
|
Changes to the device during its lifetime and related V&V | X*) |
| X | Article 10 (and others) |
|
List of standards (or “other methods”) used to demonstrate conformity | X*) |
| X | II.4. b), c) |
|
(Documents to) demonstrate conformity with GSPR | X*) |
| X | II.4. d) |
|
Table 1: X*) means that it is not ISO 13485 itself but rather the “Practical Guide” that recommends the document. You find IVDR references in the download version of this table.
NB!
Careful! Just because a cell is not marked with an X, it should not be concluded that the regulation does not require the document. It just doesn’t mention it explicitly.
The MDR and IVDR insist on more documents for the technical documentation than ISO 13485 does for the medical device file. For example, test results and PMS plans are mandatory components of the technical documentation but not of the medical device file. Put simply, the Technical Documentation is a superset of the medical device file.
If you compare the medical device file to the “FDA's files", it is most similar to the device master record.
You can download this table as an Excel file:
3. One medical device file for multiple devices?
a) Medical device family vs. generic device group
ISO 13485 allows to create a medical device file for several medical devices of the same medical device family.
Definition: medical device family
"Group of medical devices manufactured by or for the same organization and having the same basic design and performance characteristics related to safety, intended use, and function."
ISO 13485 Chapter 3.12
A look at the definition of "generic device group" in the MDR reveals that the two "groups" are not identical:
Definition: Generic device group
"Set of devices having the same or similar intended purposes or a commonality of technology allowing them to be classified in a generic manner not reflecting specific characteristics."
MDR Article 2 (7)
Conclusion: According to the MDR, the generic device group is somewhat broader defined than the medical device family. The medical device family must not include devices whose intended purpose is only similar.
b) Common file for the same medical device family and the same basic UDI-DI
The MDR and the IVDR allow to create a common technical documentation for several medical devices with the same basic UDI-DI. Note, with the same basic UDI-DI, not for a generic device group! A common basic UDI-DI, in turn, requires that
- the devices have the same intended purpose,
- their layout, i.e., the design, is essentially the same, and
- the manufacturing, i.e., production, is essentially the same.
If you compare the requirements for grouping, you will see that MDR and IVDR (see also MDCG 2018-3) further restrict the boundaries compared to ISO 13485:
| Consistency regarding | ISO 13485 | MDR, IVDR (Basic-UDI-DI) |
| Intended purpose | X | X |
| Design, performance characteristics | X (only regarding safety) | X |
| Manufacturing, production | X |
Table 2: Comparison of ISO 13485 and MDR/IVDR
Thus, the basic UDI-DI, rather than the medical device file, should determine for which devices manufacturers may create a common medical device file.
4. The medical device file as a file?
ISO 13485, like the EU regulations, does not insist on a physical file. Neither do manufacturers have to fill redundant file folders with paper, nor do they have to store digital documents redundantly in directories.
Instead, manufacturers are well advised to have a (digital) "introductory document" that includes the following:
- Context, especially a brief description and identification of the device,
- Table of contents (here, you can follow common formats such as STED),
- A short summary of the respective documents, and
- Link to these documents to identify the details.
The objective should be to provide readers (colleagues, auditors) an overview and efficient navigation to the desired documents.
5. Conclusion and tips
a) Criticism
Since the 2016 edition, ISO 13485 has insisted on a medical device file. It is debatable how useful this new concept is:
- Unnecessary
Manufacturers must generate technical documentation or FDA-compliant files (DMR, DHF, DHR) anyway. These are the superset of the medical device file. ISO 13485 additionally refers to these regulations in the same chapter. - Confusing
ISO 13485 introduces the term "medical device family." This term creates confusion with the term "generic medical device group." Even regulatory documents do not use both terms precisely. - Unspecific
The content required by the standard is too generic to be helpful to manufacturers. As a result, auditors use the more specific practical guide, which seems more aligned with the MDR/IVDR. It even refers to "General Safety and Performance Requirements." - Expensive
To remain on par with auditors, manufacturers do not only have to buy the standard but also the practical guide. Admittedly, the costs are manageable.
b) Benefits
Manufacturers are allowed to create a common medical device file for different devices in a medical device family. This can save work and is good news.
However, the MDR and IVDR permit a common technical documentation, only for devices with the same basic UDI-DI. Devices with the same basic UDI-DI must be "more similar" to each other than devices in the same medical device family.
There is also hope that the medical device file concept paved the way for the FDA to replace its 21 CFR part 820 by ISO 13485. That would be a real simplification. The medical device file is already the equivalent of the device master record.
c) Next steps
The Johner Institute recommends that manufacturers:
- Purchase the practical guide and use it during internal audits (not only regarding the medical device file).
- Download the Excel file and use it as a checklist to verify the completeness of the files.
- Check if files of very similar devices can be merged to simplify their future maintenance.
Do you have questions regarding the medical device file? Would you like someone to check your files for completeness or help you revise them so that the following audit and approval will go smoothly? Get in touch via our web form or benefit from the free micro-consulting.
Author:
Prof. Dr. Christian Johner
Back To Top
Privacy settings
We use cookies on our website. Some of them are essential, while others help us improve this website and your experience.