Many laws and standards require validation. However, these regulations define the term differently in various contexts.
Content
This article provides a quick overview and links to practical tips in further articles:
ISO 9000 defines the term validation as follows:
Confirmation by objective evidence that the requirements for a specific application or intended purpose have been met
As the term requirement is interpreted differently, this definition is helpful:
Confirmation by objective means of whether specified users achieve the specified objectives in the specified context of use
The article on verification and validation of medical devices provides a quick introduction to the topic.
The definitions do not determine which objects are validated. In the context of medical devices, these are, for example
For medical devices, validation occurs at the end of development (see Fig. 1). This applies not only to the V-model but to every development process.
Fig. 1: Validation takes place at the end of the development process.
This is referred to as design validation.
It must ensure that the stakeholders’ requirements are met and that the users achieve the intended purpose (see dashed red arrow in Fig. 1).
The most important methods in the validation of medical devices are clinical evaluation and usability validation, e.g., in the form of a summative evaluation or usability tests.
In the V&V of IVDs, the performance evaluation corresponds to the clinical evaluation.
Some manufacturers also include tests in test laboratories, such as biocompatibility tests (e.g., cytotoxicity tests) and electrical safety tests in validation. But these tend to be verification activities.
The term “validation” is also used in the context of components, such as machine learning libraries. However, these tend to be verification activities in the regulatory sense.
All important standards and laws require the validation of medical devices. These include:
ISO 13485 counts clinical evaluation as part of validation.
These notes on the clinical evaluation of software are helpful.
In its guidance, General Principles of Software Validation, the FDA describes software quality management rather than software validation.
In several instances, ISO 13485 requires manufacturers to validate their infrastructure and tools. Chapter 4.1.6, for example, obliges manufacturers to perform Computerized Systems Validation (CSV). Standards such as ISO 80002-2 and AMII TIR 36 assist with this.
This article describes the exact requirements of the standard for tool validation.
Laws and standards such as the MDR, IVDR, and ISO 13485 also oblige manufacturers to validate processes. All processes that have an impact on the conformity of the devices must be validated. These are not only development and production processes but also processes for dealing with customer feedback and post-market surveillance.
Do you still have questions about the validation of medical devices, computerized systems, and processes? Our free micro-consulting will provide you with answers.
You will learn how to validate processes in the internal auditor seminar and the certified auditor course. The computerized systems validation seminar provides you with all the knowledge you need to carry out CSV yourself.
A usability validation in the Johner Institute’s usability labs ensures the conformity and usability of your devices.
Contact us here if you would like support in determining and verifying all relevant requirements quickly, easily, and in compliance with the law. We will help you avoid hassle and delays in the approval process and quickly get your devices onto the market.
What is the difference between verification and validation, and how are these terms defined? Even standards and regulations use the terms incorrectly or misleadingly. This article 1. Verification a) Definition This definition does not explain what type of “requirements” need to be confirmed by verification. Limiting these requirements to product or component requirements is recommended to avoid…
DetailsThe term summative evaluation can be translated as “final evaluation.” A summative evaluation checks at the end of the development phase whether users can operate a device or a user interface safely. This article provides an overview of the regulatory requirements for the “summative evaluation” (sometimes also referred to as “summative assessment“) and gives you…
DetailsThe FDA describes its requirements for Human Factors Engineering in two documents: This article What the FDA calls “Human Factors Engineering” (HFE), IEC 62366-1 calls “Usability Engineering“. The FDA defines the term as follows: 1. How the FDA’s “Human Factors Guidances” interact In the introduction to the document “Content of Human Factors Information in Medical…
DetailsThe regulations relevant to usability engineering require formative evaluations. 1. Formative evaluation: Definition and differentiation a) Definitions In its guidance document, the FDA has published its own definition of the term: Thus, it replaces the old definition in the guideline Applying Human Factors and Usability Engineering to Medical Devices: „Process of assessing, at one or…
DetailsWe frequently get asked, “Do you also offer Computerized Systems Validation?” One of the reasons for the interest is certainly: Authorities and notified bodies increasingly address the Computerized Systems Validation (CSV) in audits. This article introduces regulatory requirements regarding “Computerized Systems Validation” and provides guidance on how you can best meet these requirements. Computerized Systems…
DetailsIf manufacturers don’t conduct a legally compliant performance evaluation of their in vitro diagnostic medical device (IVD), they aren’t just running the risk of problems during the authorization process: They are risking patient safety. Therefore, the IVDR sets strict requirements for this performance evaluation. Find out how the requirements of the IVDR for the performance…
DetailsCytotoxicity testing can be used to test a sample to determine how much it can damage, or even cause the death of, human cells. Standards and legislation require manufacturers to demonstrate that their devices are not cytotoxic. With a good test setup, it is possible to detect whether a sample is 100% cytotoxic, i.e., highly cytotoxic, or…
DetailsThe same legal requirements apply to the clinical evaluation of software as to the clinical evaluation of all medical devices. This means that as a Medical Device Software (MDSW) manufacturer, you must prepare a clinical evaluation for your product just like any other manufacturer. A performance evaluation must be carried out for software that is an in vitro diagnostic…
DetailsProcess validation is the verification that a process meets the requirements imposed on its process results. Learn when you must validate which processes (in the context of software) and how to ace validation. Furthermore, find out what process validation has to do with PQ, IQ, and OQ. Process validation: What is it exactly? a) Definition…
DetailsIEC 82304 is now available. This is a good reason to take a closer look at this standard for “health software products.” IEC 82304: Why another standard? Closing the IEC 62304 validation gap IEC 62304 was launched with the claim of being applicable to all medical device software – whether standalone or embedded. However, the…
Details