There are a number of issues here for which caution is required.
Many people confuse the clinical evaluation process with the clinical evaluation report. The report is one step in the process; conflating them can lead to confusion.
It is important to recognize the location of the clinical evaluation process in the device life-cycle. The clinical evaluation process is part of applying the CE Mark on the device. In this case, I infer that Version A has a CE Mark under the MDD. However, Version B does not have a CE Mark, since the clinical evaluation is not complete.
The clinical evaluation process is a requirement of MDD Annex X, Clause 1. MedDev 2.7.1 Rev. 3 and Rev. 4 provide methodologies to perform the process.
While the MedDev are guidance documents and not required, most people take them as requirements; I'll use that approach. As a requirement, MedDev 2.7.1 Rev. 4 has an effective date of July 1, 2016. In practice this means that any MDD Declaration of Conformity from July 1, 2016 is supported by a clinical evaluation using the process in MedDev 2.7.1 Rev. 4.
The role of the clinical evaluation process is important. Following MDD Annex X Clause 1.1 clinical evaluation confirms conformity with the requirements of:
- MDD Annex I Section 1 under normal use conditions
- MDD Annex I Section 3 under normal use conditions
- MDD Annex I Section 6 related to side-effects
- MDD Annex I Section 6 related to the acceptability of the benefit/risk ratio.
I infer that Device A satisfies these requirements based on a clinical evaluation.
Since Version B does not have a CE Mark, MedDev 2.7.1 Rev. 4 defines the applicable clinical evaluation process. One step in the clinical evaluation process determines if there an equivalent device about which one could use information to support the MDD Annex X conclusion. Note that MedDev 2.7.1 Rev. 4 does not require an equivalent device.
Since Version A does have a CE Mark, there may be additional information on Version A from post-market surveillance (PMS), Post-market Clinical Follow Up (PMCF), or Post-production information from EN ISO 14971:2012 Clause 9.
You ask, to paraphrase, whether in the clinical evaluation of Version B can Version A be considered as an identical device under MEDDEV 2.7.1 Rev 3. My answer is no. Since Rev. 3 is obsolete nothing in Rev. 3 applies to the clinical evaluation of Version B under Rev. 4. For Version B you must use the Rev. 4 process only.
Under the Rev. 4 process applied to Version B, you could evaluate Version A to determine if it is equivalent to Version B. If some of the data Version A data could apply, this makes the clinical evaluation process simpler. MEDDEV 2.7.1 Rev 4 Appendix A1 describes the process to determine whether Version A is equivalent to Version B.
If the design change were a material change, thereby causing Version B to falter in regards to fulfilling the biological equivalence criterion (i.e., MEDDEV 2.7.1 Rev 4 Appendix A1), then you could not claim that Version B is equivalent to Version A.
If Version A were not equivalent to Version B, however, much of the clinical evaluation data collected for Version A could also apply to Version B.
------------------------------
Dan O'Leary
Swanzey NH
United States
------------------------------
Original Message:
Sent: 21-Nov-2017 18:59
From: Kevin Randall
Subject: EU Clinical evaluation: Identical Devices vs. "Equivalent" Devices
A manufacturer has clinical data/literature for two versions of its device: Version A (original version) and Version B (resulting from a design change).
When doing a European Clinical Evaluation Report (CER) per MEDDEV 2.7.1 Rev 4 for Version B, can Version A (and its corresponding data) still be recognized as the identical device (vis-à-vis category D1 per MEDDEV 2.7.1 Rev 3), or does Version A instead need to be categorized/justified as an "equivalent" device (i.e., category D2)?
If the "equivalent" device route, then what if the design change was a material change, thereby causing Version B to falter in regards to fulfilling the biological equivalence criterion (i.e., MEDDEV 2.7.1 Rev 4 Appendix A1)?
Any thoughts/comments are appreciated!
------------------------------
Kevin Randall, ASQ CQA, RAC (U.S., Canada, Europe)
Principal Consultant
ComplianceAcuity, Inc.
Golden CO
United States
www.complianceacuity.com
------------------------------