How to Define IEC 60601-1 Essential Performance
By the end of this guide, you’ll know how to identify which device functions qualify as essential performance, connect them to your Risk Management File, and avoid mistakes that can delay submission.
Why Essential Performance Is Often Defined Incorrectly
Essential performance is often misunderstood because it sits between clinical function, risk management, and testing.
Some teams define it too broadly because they do not want to miss anything. Others define it too narrowly because they focus only on engineering behavior. Both approaches create problems.
The goal is not to list every function of the device. The goal is to identify the functions whose loss or degradation could result in unacceptable risk to the patient or operator.
Essential Performance Is Not the Same as Basic Safety
This is one of the most common mistakes in IEC 60601-1 testing.
Basic safety covers protection against electrical, mechanical, and thermal hazards. Examples include insulation, leakage current, enclosure strength, and protection from electric shock.
Essential performance covers clinical functions whose loss or degradation could lead to unacceptable risk.
For example:
- Leakage current is a basic safety requirement.
- Insulation resistance is a basic safety requirement.
- Accurate drug delivery rate may be essential performance.
- Alarm activation during a critical patient condition may be essential performance.
- Therapy output within a defined range may be essential performance.
When basic safety items are added to the essential performance list, auditors may question whether the manufacturer understands Clause 4.3. It also creates unnecessary test burden and confusion during documentation review.
Start With Clinical Function, Not Engineering Function
Before defining essential performance, you need four things ready:
- A complete list of the device’s clinical functions
- An active Risk Management File with hazard analysis underway or complete
- Access to IEC 60601-1 Clause 4.3 and applicable particular standards
- A clear internal risk acceptability policy with agreed thresholds
The starting point should always be clinical function, not engineering function.
A processor reset is an engineering event. But if that reset interrupts therapy delivery or suppresses an alarm, the impact must be assessed through patient harm.
A good test is this: Can you describe your device’s intended clinical use in one sentence without mentioning technical specifications? If not, revisit the intended use statement before defining essential performance.
Connect Every Clinical Function to Patient Harm
Start by listing every function your ME equipment performs that directly affects the patient or operator during intended use.
This may include drug delivery rate, alarm triggering, temperature measurement, waveform display, therapy output, physiological parameter monitoring, ventilation control, and infusion control.
Each function should be paired with a specific harm scenario.
For example:
“If the infusion rate deviates by more than ±5%, the patient receives an incorrect dose.”
That is useful.
“The pump motor speed changes” is not enough by itself because it describes an engineering issue, not the clinical harm.
Your list should explain what happens to the patient or operator if the function fails, degrades, or behaves incorrectly.
Use the Absence Test to Decide What Qualifies
IEC 60601-1 Clause 4.3 becomes practical when you apply the absence test.
For each clinical function, ask:
If this function is removed or degraded, does the patient or operator face unacceptable risk?
If yes, it may be a candidate for essential performance.
If no, it should not be included as essential performance.
After the absence test, apply hazard and harm scoring through the Risk Management File. If clinical data or risk analysis shows that a specific harm sequence is negligible, that rationale should be clearly recorded in the RMF.
A typical Class IIa device may end up with 3 to 10 essential performance characteristics. If the list still has 30 or more items, there is a good chance that basic safety, usability, convenience features, or engineering functions are being mixed into the EP list.
Set Measurable Performance Limits
Every essential performance characteristic needs a measurable limit.
“The alarm should work” is not enough. A stronger definition would be:
“The SpO2 alarm must trigger within 10 seconds when saturation drops below 88%.”
A measurable EP definition should include:
- The clinical function
- The acceptable performance range
- The failure or degradation condition
- The patient or operator risk
- The verification method
For software-dependent devices, teams may need to define performance envelopes instead of single-point thresholds.
Build RMF Traceability Before Testing
The Risk Management File is the backbone of essential performance definition.
Every EP characteristic should trace back to:
- A specific hazard in the risk analysis
- A harm severity rating
- Performance-related risk control measures
- A verification test method
- A pass/fail criterion
Clean traceability should look like this:
EP item → hazard → harm → risk control → verification method → test result
No orphaned entries. No EP items without hazards. No test methods without defined limits.
A useful internal check is to pick five random EP items and trace each one through the RMF. If you cannot reach a specific test protocol for each item in under two minutes, the documentation structure needs improvement.
Verify Essential Performance Under Fault and EMC Conditions
Essential performance must be verified under conditions that can reasonably affect the device’s clinical function.
That includes normal condition, single fault condition, and relevant EMC testing exposure.
Under single fault condition, one component may fail, one wire may break, or one power supply may short. The device must still meet its essential performance limits or fail safely.
During IEC 60601-1-2 EMC testing, essential performance may need to be monitored during radiated immunity, conducted immunity, electrostatic discharge, electrical fast transients, and surges.
For example, if an infusion rate drifts outside its EP limit during radiated immunity testing, that is a failure, even if the device recovers afterward.
Common Mistakes That Lead to Audit Findings
Mistake | Why It Causes Problems | Better Approach |
Including basic safety items in the EP list | It shows confusion between Clause 8 and Clause 4.3 | Filter out leakage current, insulation, enclosure strength, and other basic safety parameters |
Defining EP too broadly | It increases testing scope, timeline, and cost | Use hazard scoring and documented clinical rationale |
Defining EP without measurable limits | The test team cannot verify pass/fail clearly | Use quantitative thresholds wherever possible |
Leaving EP items disconnected from the RMF | Auditors cannot trace the risk logic | Link every EP item to hazard, harm, risk control, and verification |
Ignoring EMC exposure | Device performance may degrade during immunity testing | Monitor EP during relevant IEC 60601-1-2 tests |
Astute Labs Support for IEC 60601-1 Essential Performance Verification
Defining essential performance is only half the challenge. Manufacturers also need to verify that essential performance is maintained under relevant safety, fault, and EMC conditions.
Astute Labs provides medical device testing support for IEC 60601-1 and related standards, helping manufacturers evaluate safety and performance-linked requirements before formal submission.
For devices where essential performance depends on software behavior, alarms, therapy output, monitoring accuracy, or EMC immunity, early review and pre-compliance testing can reduce avoidable delays.
So the question worth asking is this: is your current EP list driven by genuine clinical risk analysis, or by fear of what an auditor might say?
Those two motivations produce very different lists and very different testing budgets. Contact us
