Start here

A reading path through SaMD architecture

The posts here were written one at a time, but they build on each other. This is the order I would read them in. Diagrams enlarge when you click them, and every post links on to related ones.

3

Standards as architecture

Each standard is a design requirement in disguise.

Article · 1 min read

Standards are architectural requirements in disguise

A map of the core MedTech standards stack and why architects should care about each layer. Compliance is a Day 1 design decision.

StandardsComplianceArchitecture
Diagram series · 1 min read

ISO 13485 is the house. IEC 62304 is what lives inside it.

ISO 13485 governs the whole development process. IEC 62304 is the execution engine for software inside it. One without the other is an auditable gap.

ISO 13485IEC 62304DHF
Diagram series · 1 min read

Risk management is not a document. It is a design input.

ISO 14971 asks what happens to a patient when your system fails. Your architecture has to answer it, before you write code.

ISO 14971RiskCompliance
Diagram series · 1 min read

Cybersecurity is not a phase. It is a design requirement.

If your security architecture isn't documented in the DHF, then under SW96 it doesn't exist. What the standard asks of architects.

AAMI SW96CybersecurityDHF
Diagram series · 1 min read

The interface is not a design layer. It is a safety boundary.

Good UX makes an interface intuitive. Regulatory usability engineering proves it is safe. They are not the same thing.

IEC 62366UsabilityDHF
Diagram series · 1 min read

SOUP is an architecture decision

To engineers it is a dependency list. To a regulator it is a risk artifact. What stalls submissions and what good looks like.

SOUPIEC 62304Compliance
Diagram series · 1 min read

Your pipeline is your change control process

Build, test, board approval, deploy, verify. Evidence should be a by-product of the pipeline, not a documentation task.

DeliveryComplianceArchitecture
5

Patterns for connected systems

Messaging, modernization and trust, in a regulated setting.

Diagram series · 1 min read

Same pattern. Different contract.

In a clinical SaMD an event is not a notification. It is a clinical state transition: traceable, auditable and safe to replay.

Event-drivenIEC 62304ISO 14971
Diagram series · 1 min read

In a medical device platform, modernization is a regulatory strategy

Not just a technical one. Every module you replace is a change control event under IEC 62304.

ModernizationIEC 62304Change control
Diagram series · 1 min read

Zero Trust is an architectural principle. In a clinical platform it is also a regulatory one.

Never trust implicitly. Verify continuously. Enforce least privilege at every boundary, and document all of it in your DHF.

Zero trustAAMI SW96IEC 62304
13 Oct 2026 · 2 min read

Draw the trust boundaries before you pick the controls

Controls only mean something at a boundary. Map where trust changes first, and the threat model, the requirements and the verification scope follow from it.

CybersecurityThreat modellingArchitecture
20 Oct 2026 · 2 min read

A device identity should be born on the device

Where the private key is created decides how bad a breach can get. Generate it on the device, send only a CSR, and plan for stolen, spoofed, expired and rotated certificates before you ship.

CybersecurityDevice identityPKI
27 Oct 2026 · 2 min read

When a security control can hurt the patient

Security controls usually fail closed. In a medical device that default can be the hazard, so whether a function stops, keeps running degraded or refuses access has to be decided per function and written down.

CybersecurityISO 14971Risk management
Diagram series · 1 min read

RabbitMQ is not a queue. It is a routing engine with queues attached.

Most production failures come from treating it as a black box and discovering its failure modes under load.

RabbitMQMessagingArchitecture
30 Sep 2026 · 2 min read

"Saved" is not "received"

A cloud app says a record is saved. The device may never have got it. Where delivery guarantees stop on AWS IoT Core, and what to build on top.

Connected devicesMQTTAWS

Looking for the principles behind all of it? Read the Resilient MedTech Architecture Framework.

Question about something here?

Questions, corrections and counterexamples are welcome. Send a note or message me on LinkedIn.