IEC 60601 Compliance Is Not Clinical Evidence

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

The misunderstanding stems from how standards functioned under the Medical Device Directive (MDD). Demonstrating conformity to harmonized standards was often sufficient to presume compliance with essential requirements. But MDR changed this relationship fundamentally.

Under MDR Article 61, clinical evaluation must demonstrate safety and performance based on clinical data. This is not the same as technical compliance. IEC 60601-1 and its collateral standards define electrical safety requirements—isolation, leakage currents, protective earth integrity. These are essential, but they do not address clinical outcomes, intended use effectiveness, or residual risk acceptability in real-world use.

Manufacturers still need IEC 60601 compliance. That is not in question. The issue is that technical compliance alone cannot fulfill the clinical evidence obligation. Yet this gap is consistently underestimated.

Where the Confusion Begins

IEC 60601 standards are central to electrical medical device design. They provide quantitative thresholds for electrical hazards, define testing protocols, and establish pass/fail criteria. Compliance is typically verified through laboratory testing and documented in technical files.

Clinical evaluation, by contrast, requires evidence that the device performs as intended when used in the target patient population, that residual risks are acceptable, and that the benefit-risk profile is favorable. This evidence must come from clinical data—literature, clinical investigations, or PMCF.

The confusion arises because both processes involve risk. IEC 60601 addresses electrical hazards. Clinical evaluation addresses clinical risks—including those that electrical safety testing cannot detect.

So what happens during review?

Notified Bodies and competent authorities recognize the distinction immediately. They will ask: Where is the clinical data? Where is the evidence that this device, used by this operator, in this patient group, delivers the claimed benefit without unacceptable clinical risk?

The IEC 60601 test report does not answer these questions.

Why Electrical Safety Alone Is Not Sufficient

Consider a diagnostic ultrasound device. IEC 60601-1 and IEC 60601-2-37 establish requirements for electrical safety and acoustic output limits. Compliance testing confirms that the device does not pose electrical shock hazards and that acoustic output remains within defined safety margins.

But clinical evaluation must address different questions: Does the device produce images of sufficient quality for the intended diagnostic purpose? Can operators interpret those images reliably? Are there patient populations where the device performs inadequately? What is the rate of false positives or false negatives in clinical use?

These questions require clinical data. They cannot be answered by electrical safety testing.

The same principle applies to therapeutic devices. A neurostimulator might meet all IEC 60601 requirements for electrical isolation and leakage current. But clinical evaluation must demonstrate that stimulation parameters are effective for the intended condition, that adverse effects are acceptable, and that the device performs consistently across the target patient population.

The Intersection That Matters

There is a legitimate intersection between IEC 60601 and clinical evaluation, but it is not automatic. Standards like IEC 60601 inform the risk management process. They help define acceptable limits for certain hazards. But the clinical evaluation must still interpret those limits in the context of actual use.

Take patient auxiliary current limits. IEC 60601-1 defines maximum allowable leakage currents in normal and single-fault conditions. These limits are based on physiological thresholds for perception, startle, and ventricular fibrillation.

Clinical evaluation does not repeat this electrical testing. Instead, it considers whether the intended use conditions might introduce risks not fully addressed by the standard. For example, if the device is used in a wet environment, or with compromised skin integrity, or in patients with implanted conductive devices, are the standard limits still protective?

This analysis belongs in the clinical evaluation report, not just the risk management file. It demonstrates that the manufacturer has considered the standard’s limits in the context of real clinical use.

Another example: electromagnetic compatibility. IEC 60601-1-2 defines immunity and emission requirements. Compliance testing confirms that the device operates correctly in the presence of electromagnetic disturbances and does not interfere with other equipment.

But clinical evaluation must ask: In the intended use environment—operating rooms, intensive care units, home care settings—are there EMC risks not captured by the test conditions? Are there use cases where interference could compromise clinical outcomes?

This reasoning connects the standard to clinical reality. It shows that the manufacturer understands the standard as a tool, not as a substitute for clinical thinking.

How This Appears in Equivalence Claims

The confusion becomes particularly visible in equivalence-based clinical evaluations. Manufacturers often argue that their device is equivalent to a predicate device because both comply with the same standards, including IEC 60601.

Compliance with the same standard does not establish equivalence.

MDCG 2020-5 defines equivalence based on technical, biological, and clinical characteristics. The devices must be similar in design, materials, specifications, intended use, and clinical performance. Shared compliance with IEC 60601 might support technical similarity, but it does not address clinical characteristics.

Two neurostimulators might both comply with IEC 60601-1 and IEC 60601-2-10. But if they differ in stimulation waveform, frequency range, or electrode configuration, their clinical effects might differ significantly. The standard does not resolve this question.

So equivalence claims that rely heavily on shared standards are often weak. They confuse technical conformity with clinical similarity.

What Reviewers Actually Look For

When I review a clinical evaluation report, I expect to see IEC 60601 mentioned in the context of risk management and technical documentation. It should appear in the description of how electrical hazards are controlled. It should inform the residual risk assessment.

But I do not expect it to substitute for clinical data.

What I look for instead is a clear separation between technical verification and clinical validation. The report should acknowledge that electrical safety has been demonstrated through compliance with IEC 60601. Then it should proceed to address clinical safety and performance through literature, clinical investigations, or post-market data.

If the device is used in a way that might introduce risks beyond the scope of the standard, the report should explicitly address this. For example, if the device is used in pediatric populations, or in patients with comorbidities, or in uncontrolled home environments, the clinical evaluation should consider whether the standard’s assumptions still apply.

This level of reasoning signals that the manufacturer understands the difference between technical compliance and clinical evidence. It shows clinical thinking, not just regulatory box-checking.

How to Address This Correctly

First, recognize that IEC 60601 compliance is necessary but not sufficient. Include it in your technical documentation and risk management file. Reference it in your clinical evaluation report as part of the safety assurance framework. But do not treat it as clinical evidence.

Second, structure your CER to clearly distinguish technical verification from clinical validation. Use a section on electrical safety to summarize compliance with IEC 60601 and explain how this controls electrical hazards. Then proceed to separate sections on clinical performance, clinical safety, and benefit-risk that are based on clinical data.

Third, when claiming equivalence, do not rely on shared standards. Focus on demonstrating similarity in technical characteristics, biological interaction, and clinical performance. If both your device and the predicate comply with IEC 60601, mention it briefly as supporting technical similarity. But build your equivalence argument on clinical characteristics.

Fourth, use PMCF to validate that standard-based safety limits remain adequate in real-world use. Standards are based on assumptions about use conditions, patient populations, and operator competence. PMCF data can confirm or challenge those assumptions.

For example, if your device is used in home care, PMCF might reveal that electrical safety incidents occur at rates higher than expected, not because the device fails IEC 60601 testing, but because home environments introduce conditions the standard did not fully anticipate. This finding would inform both risk management and clinical evaluation updates.

The Bigger Picture

This issue reflects a broader shift under MDR. Standards remain important, but they are no longer sufficient on their own. Compliance with harmonized standards provides a presumption of conformity with certain essential requirements, but it does not replace the obligation to demonstrate clinical safety and performance through clinical data.

This distinction is not always intuitive, especially for manufacturers transitioning from MDD. Under the old framework, demonstrating conformity to standards was often the primary path to compliance. MDR raised the bar. Clinical evaluation is now a central, independent requirement that must be supported by clinical evidence.

IEC 60601 is a tool. It helps control electrical risks. It informs design decisions. It provides quantitative safety thresholds. But it does not answer clinical questions. Those questions require clinical data.

Manufacturers who understand this distinction produce stronger clinical evaluation reports. They avoid the common deficiency of conflating technical compliance with clinical evidence. They structure their documentation to clearly separate verification from validation, and they use standards appropriately—as inputs to clinical reasoning, not as substitutes for it.

Notified Bodies appreciate this clarity. They move through the review faster when the boundaries between technical compliance and clinical evidence are clearly drawn. They spend less time requesting clarifications and more time focusing on substantive clinical questions.

So the practical benefit is real. Getting this right does not just satisfy regulatory requirements. It makes the review process more efficient and reduces the risk of late-stage deficiencies.

In the next part of this series, I will address how usability standards like IEC 62366 interact with clinical evaluation, and why human factors validation is not the same as clinical validation.