Medical Device Testing

Medical device testing shows that a device is safe for the patient and the user and maintains its intended performance. In this family safety is not only about avoiding harm; a device failing to perform its expected function is also treated as a risk. A monitor missing an alarm or a pump delivering the wrong dose is directly a patient safety event.

At the centre of the field is RISK MANAGEMENT, and this is what sets medical apart from other sectors. The risk management process run under ISO 14971 also determines which tests are required. The test list is not copied from a table of standards; it is derived and justified from the device's intended use, the nature and duration of patient contact, the use environment and foreseeable misuse.

Assessment consists of several separate bodies of work, each with its own set of standards. Biocompatibility runs through the ISO 10993 series, electrical device safety through the IEC 60601 series, sterilisation through ISO 11135/11137/17665, packaging through ISO 11607, software through IEC 62304 and usability through IEC 62366. The quality system (ISO 13485) is the framework that binds these together.

Which tests are required is determined by the device's CLASS and its MODE OF CONTACT WITH THE BODY. A product in brief contact with skin and an implant entering the bloodstream do not go through the same test set; the scope is set by a biological evaluation plan prepared under ISO 10993-1. That plan justifies in writing which endpoints are required and why the others are not.

Packaging and sterilisation are taken as seriously as the device itself in this field. For a sterile device the packaging is not a transport container but the barrier that maintains sterility; if the barrier is breached, the device is no longer sterile. Packaging processes are therefore validated and shelf life is supported by real-time ageing data.

For devices containing software, assessment shifts from testing towards PROCESS assurance. IEC 62304 defines which development and verification steps must be followed according to the safety class of the software; the evidence is the traceability of the development process. Testing software does not make it safe — the process record does.

The clinical side is a separate column of the technical file. Test reports show that the device is technically safe; clinical evaluation establishes that the device delivers the intended clinical benefit and that the benefit-risk balance is acceptable. Neither replaces the other.