QMS ISO 13485

ISO 13485 Clause Map

Clause 8 is evidence-heavy: Auditors expect to pull individual CAPA records and trace from complaint or nonconformance through root cause analysis, corrective action, effectiveness check, and closure. Gaps in any step are findings.

Design Controls (Clause 7.3)

Design controls are the most cited nonconformance area in ISO 13485 audits. The clause defines a sequential, linked loop that must produce documented evidence at every stage:

The design control loop:

Design Inputs → Design Outputs → Verification → Validation → Transfer
       ↑                                                           ↓
       └──────────────── Design Changes (§7.3.9) ←───────────────┘

Design reviews (§7.3.5) must occur at planned stages throughout the loop and involve at least one participant independent of the design function.

Verification vs. validation — the precise distinction:

The common failure mode: Treating performance testing (bench test against specifications) as validation. It is not — that is verification. Validation must demonstrate suitability for actual use by intended users in the intended environment.

Traceability Requirements

Traceability in ISO 13485 operates at two levels: design traceability (DHF) and device traceability (DHR/DMR).

Design file traceability chain:

User Need → Design Input → Design Output → Verification result → Validation result

Each link must be documented in a traceability matrix. A user need with no design input, or a design output with no verification test, is an automatic finding.

Device history record (DHR) traceability — what must trace to what:

Why traceability gaps are high-severity findings: A missing link in the DHF-to-DHR chain means you cannot demonstrate that the device reaching a patient was built to the approved design. Notified bodies and FDA treat this as a potential patient safety issue, not a paperwork deficiency. Severity classification during audit is typically major or even critical depending on the product class.

Nonconformance Severity Classification

Classification drives CAPA requirements, audit outcomes, and regulatory notification obligations.

How classification affects ongoing operations: A critical finding during a surveillance audit typically triggers an unscheduled follow-up audit before the next certification cycle. A pattern of recurring minor findings in the same process area is often reclassified as a major at the next audit — auditors document repeat findings explicitly.

Self-classification during internal audits: Train internal auditors to classify conservatively. An internal finding classified as minor that an external auditor reclassifies as major signals that your internal audit function lacks rigor — itself an audit finding.

Audit Timing Strategy

Stage 1 — Readiness audit (document review): Focus: Does your documented QMS cover all required processes? Do you have the right documents?

Stage 1 preparation priorities:

• Quality manual complete, scope defined and justified
• All mandatory procedures present (document control, record control, internal audit, CAPA, nonconforming product, complaint handling)
• At least one complete internal audit cycle with records
• At least one management review with minutes showing required inputs were addressed
• Design control procedures in place even if no products are in active development

Stage 2 — Implementation audit (on-site verification): Focus: Are you actually doing what the documents say? Do your records prove it?

Stage 2 preparation priorities:

• Pull and review your own CAPA records for completeness before the audit
• Verify training records are current and linked to the current document versions
• Confirm all approved suppliers on your Approved Supplier List have evaluation records on file
• Check that DHRs exist for any devices built during the QMS period
• Brief all staff who may be interviewed — auditors routinely speak to operators, not just the QMR

The gap between stages: Typically 4–12 weeks. Use it to close Stage 1 findings, not to implement processes that should have been in place. Implementing a CAPA system for the first time between Stage 1 and Stage 2 signals that Stage 1 readiness was overstated.