Medical Device Electronics: The Standards That Shape the Design

Developing a medical device means working within a framework of standards covering quality management, risk, electrical safety and software. They are not paperwork added at the end; they determine how requirements are written, how software is structured and what evidence must exist before the product can be sold. This article maps the main standards to the parts of a project they govern. It is an overview, not regulatory advice.

At a glance

ISO 13485
Quality management system requirements for medical device organisations.
ISO 14971
Application of risk management to medical devices.
IEC 60601-1
Basic safety and essential performance of medical electrical equipment.
IEC 62304
Software life-cycle processes, with three software safety classes.

The problem

Teams new to medical work often build a working prototype first and turn to the standards afterwards. By then the architecture is fixed, and it may not provide the isolation, the separation of software by safety class or the traceability the standards expect.

The cost of compliance also scales with the classification. A software item whose failure could cause serious injury carries far heavier process and documentation requirements than one that cannot cause harm.

Classification drives the workload. Establish it before the architecture, because the architecture can change it.

Software safety classes

IEC 62304 assigns each software system a class from A to C according to the severity of harm its failure could contribute to. The required activities grow with the class: Class C demands detailed design, unit verification and more extensive documentation.

Architecture can contain the burden. If the safety-critical function is isolated in a small, separate item, with hardware measures limiting what the rest can do, the bulk of the software may justify a lower class.

What good looks like

Define the intended use and work with a qualified regulatory specialist to establish the device classification and applicable standards for each market.

Run risk management from the start and let its results drive requirements, architecture and software classification.

Build traceability as you go: each requirement linked to its design, its risk controls and the test that verifies it.

Which standard governs what
StandardSubjectAffects
ISO 13485Quality management systemHow the organisation develops and controls products
ISO 14971Risk managementHazard analysis and risk controls throughout
IEC 60601-1Electrical safety and essential performanceIsolation, leakage current, construction
IEC 60601-1-2Electromagnetic compatibilityEmissions and immunity
IEC 62304Software life cycleSoftware planning, design, verification, maintenance
IEC 62366-1Usability engineeringUser interface and use-related risk
An overview of commonly applied standards. The set that applies to your device depends on its classification and markets.
IEC 62304 software safety classes
ClassPossible consequence of failureProcess rigour
ANo injury or damage to healthLowest
BNon-serious injuryIntermediate
CDeath or serious injuryHighest
Classes as defined in the standard. Classification follows from the risk analysis.

What it changes

Fewer Surprises

Requirements that would force a redesign are known before the design is fixed.

Focused Effort

The heaviest processes are applied only to the parts that warrant them.

Audit Readiness

Evidence accumulates during development instead of being reconstructed afterwards.

Safer Product

Hazards are addressed by design, which is the purpose the standards serve.

Where to go next

Regulatory requirements differ by market and change over time. Confirm current requirements with a regulatory professional for each country you intend to sell in.

Connected devices bring cybersecurity expectations as well. Plan for threat modelling and for security updates across the product’s life.

Problems this prevents

  • A prototype built before classification was known
  • Safety-critical code mixed with everything else
  • Traceability reconstructed after the fact
  • Standards treated as final-stage paperwork

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.