EU Medical Devices: Why Harmonised Standards Matter for Technical Documentation

Harmonised standards help medical device manufacturers build stronger MDR technical documentation. Learn how standards connect risks, testing and compliance.

For medical device manufacturers, technical documentation is not just a collection of test reports and design files.

It needs to demonstrate that the device meets the applicable requirements of the EU Medical Device Regulation (MDR).

One of the most important tools for building this evidence package is the use of harmonised standards.

They do not replace the MDR.

However, they provide manufacturers with a structured way to demonstrate that specific regulatory requirements have been addressed.


What are harmonised standards?

Harmonised standards are technical standards developed by recognised European standardisation organisations, such as:

  • CEN
  • CENELEC
  • ETSI

When a standard is referenced in the Official Journal of the European Union, compliance with it can provide a presumption of conformity for certain requirements covered by that standard. [European Commission, Harmonised Standards, https://single-market-economy.ec.europa.eu/single-market/european-standards/harmonised-standards_en]

For medical devices, this means standards can help manufacturers demonstrate that their design, testing and quality processes align with recognised technical expectations.


Why standards matter for technical documentation

The MDR requires manufacturers to prepare technical documentation that demonstrates conformity with applicable requirements.

This documentation must cover areas such as:

  • device description
  • design and manufacturing information
  • risk management
  • verification and validation
  • clinical evaluation
  • labelling
  • post-market surveillance

The technical file needs to show not only what was done, but also why the chosen approach demonstrates safety and performance.

Standards provide a recognised framework for many of these decisions.


Standards connect requirements with evidence

A regulatory requirement often describes an objective.

For example:

The device must be safe and perform as intended.

A standard can provide a practical framework for demonstrating this.

The connection looks like:

MDR requirement

↓

Applicable harmonised standard

↓

Testing / evaluation method

↓

Technical documentation evidence

↓

Conformity assessment

This makes the reasoning behind compliance easier to follow.


Harmonised standards do not automatically guarantee compliance

This point is important.

Using a standard does not mean a manufacturer automatically complies with the MDR.

The manufacturer still needs to demonstrate that:

  • the standard applies to the device
  • the correct version was used
  • the relevant requirements were addressed
  • the device-specific risks were considered
  • the evidence supports the intended purpose

A standard is a tool.

It is not a replacement for regulatory judgement.


The role of standards under the MDR

The MDR introduced a stronger focus on:

  • risk management
  • clinical evidence
  • lifecycle monitoring
  • post-market surveillance

Therefore, standards need to be integrated into a broader compliance strategy.

A manufacturer should not ask:

“Which standards can we apply?”

The better question is:

“Which standards help us demonstrate compliance with the requirements relevant to our device?”


Example: Risk management and ISO 14971

One of the most important standards for medical devices is:

ISO 14971 – Medical devices — Application of risk management to medical devices

This standard provides a structured approach for identifying, evaluating and controlling risks throughout the device lifecycle.

Risk management is a central MDR requirement, and ISO 14971 is widely used to support compliance with these principles.

A technical file should therefore show the connection between:

  • identified hazards
  • risk evaluation
  • risk controls
  • verification activities
  • residual risks
  • benefit-risk analysis

A risk-management file without a clear connection to design and testing evidence is incomplete.


Example: Biological safety and ISO 10993

For devices that come into contact with the human body, biological evaluation is a major consideration.

The ISO 10993 series provides guidance for evaluating biological safety.

Depending on the device, assessment may include:

  • cytotoxicity
  • sensitisation
  • irritation
  • systemic toxicity
  • chemical characterisation
  • other biological endpoints

However, not every device requires every test.

The biological evaluation should be based on:

  • materials
  • contact type
  • contact duration
  • intended use
  • patient exposure

A risk-based approach is essential.


Example: Electrical safety and IEC 60601

For active medical devices, electrical safety and electromagnetic compatibility can be critical.

Standards such as the IEC 60601 series address requirements for medical electrical equipment.

Depending on the device, manufacturers may need evidence relating to:

  • electrical safety
  • essential performance
  • electromagnetic compatibility
  • environmental conditions

The applicable standard depends on the device type.

A wearable monitoring device and a hospital imaging system will not require the same technical approach.


Example: Software standards

Software has become increasingly important in medical devices.

For software-based devices, manufacturers may need to address:

  • software lifecycle processes
  • cybersecurity
  • usability
  • verification and validation

Standards such as IEC 62304 for medical device software lifecycle processes can provide a structured framework.

However, software compliance also depends on:

  • intended purpose
  • risk classification
  • cybersecurity risks
  • interaction with hardware
  • clinical function

A software standard supports the documentation.

It does not replace the MDR assessment.


Why Notified Bodies look closely at standards

During conformity assessment, Notified Bodies review whether manufacturers have demonstrated compliance.

Technical documentation is expected to provide a logical evidence chain.

Standards can make this easier because they create recognised evaluation structures.

However, Notified Bodies will still review:

  • whether the standard is appropriate
  • whether deviations are justified
  • whether testing reflects the actual device
  • whether risks are adequately controlled

Simply listing standards in the technical file is not enough.


Standards need to match the actual device

A common mistake is applying standards too broadly.

A manufacturer may think:

“This standard applies to medical devices, so we can use it.”

That is not always correct.

The relevance depends on:

  • device classification
  • technology
  • materials
  • intended use
  • patient contact
  • active components
  • software functions

The technical documentation should explain why each applied standard is relevant.


What happens if no harmonised standard exists?

Not every medical device has a directly applicable harmonised standard.

This does not prevent market access.

Manufacturers can still demonstrate compliance using:

  • international standards
  • recognised technical specifications
  • scientific literature
  • internal methods
  • risk-based justification

The MDR does not require every aspect of a device to be covered by a harmonised standard.

It requires manufacturers to demonstrate conformity with the applicable requirements.


Standards can become outdated

Another important point:

Standards evolve.

A manufacturer cannot simply apply a standard forever without review.

Changes may affect:

  • testing methods
  • acceptance criteria
  • terminology
  • risk approaches
  • technical expectations

A quality system should therefore include monitoring of relevant standard updates.

This is especially important for products with long lifecycles.


How standards support verification and validation

Verification and validation activities generate much of the evidence used in technical documentation.

Standards can support decisions around:

  • test design
  • acceptance criteria
  • evaluation methods
  • documentation structure

For example:

Requirement:
The device must maintain performance under expected conditions.

Standard-based approach:
Define test conditions and acceptance criteria.

Evidence:
Verification report.

Conclusion:
Performance requirement demonstrated.

This creates a traceable compliance argument.


The connection between standards and risk management

Standards should always connect back to risk.

A manufacturer should be able to explain:

What risk does this test address?

Why was this method selected?

What acceptance criteria were applied?

How does the result influence the safety assessment?

This prevents a common mistake:

Performing many tests without a clear regulatory purpose.

More testing does not automatically create stronger compliance.

Relevant evidence does.


Common mistakes manufacturers make

Using standards as a checklist

A standard is not just a box to tick.

The manufacturer must demonstrate how it applies.


Applying irrelevant standards

Not every medical-device standard applies to every device.


Ignoring deviations

If a manufacturer does not follow a standard, the reason should be documented and justified.


Forgetting lifecycle changes

A design change can affect which standards and tests are relevant.


Focusing only on pre-market evidence

The MDR also requires ongoing monitoring after market entry.


A practical review checklist

Before finalising technical documentation, ask:

Device

Is the device classification correct?

Requirements

Which MDR requirements apply?

Standards

Which standards support conformity?

Risk

Are standards linked to identified risks?

Testing

Do verification activities follow appropriate methods?

Evidence

Are results documented and traceable?

Deviations

Are differences from standards justified?

Updates

Are relevant standard changes monitored?

This creates a stronger technical file.


How standards influence regulatory strategy

The best time to consider standards is not at the end of development.

They should influence:

  • design decisions
  • material selection
  • testing plans
  • risk management
  • supplier requirements
  • documentation structure

Early consideration reduces the risk of discovering missing evidence shortly before conformity assessment.


Example: A new medical device entering the EU market

Imagine a company develops a connected wearable device.

Before market entry, the manufacturer needs to consider:

Risk management

Which hazards exist?

Electrical safety

How does the device perform safely?

Software

How is the software lifecycle controlled?

Biocompatibility

Are skin-contact materials suitable?

Cybersecurity

Are risks from connectivity addressed?

Clinical evaluation

Is performance supported by evidence?

Each area may involve different standards.

Together, they create a structured technical documentation package.


Standards and regulatory decisions should work together

The strongest technical files do not simply contain:

  • test reports
  • certificates
  • standard references

They tell a clear story:

The device has defined risks.

Those risks have been controlled.

The controls have been verified.

The evidence demonstrates safety and performance.

Standards help build that story.


The Makrolife perspective

For medical device manufacturers, standards are an important connection between regulatory requirements and practical testing strategies.

Makrolife supports companies by helping connect:

  • applicable regulations
  • harmonised standards
  • risk assessment
  • analytical testing
  • verification activities
  • technical documentation

The goal is not simply to perform tests.

The goal is to generate evidence that supports a clear regulatory conclusion.


The bottom line

Harmonised standards are one of the most valuable tools for medical device manufacturers preparing technical documentation for the EU market.

They help companies:

  • structure testing
  • define evaluation methods
  • support conformity claims
  • communicate with Notified Bodies
  • create traceable evidence

But standards are not a shortcut.

A compliant technical file requires more than a list of references.

It requires a clear connection between:

MDR requirements

→ device risks

→ applicable standards

→ testing and evaluation

→ documented evidence

When these elements work together, technical documentation becomes much stronger and the conformity assessment process becomes more predictable.