ISO 13485 - The Standards Navigator

How to Audit a Medical Device QMS: The ISO 13485 Internal Audit Process (2026 Guide)

This guide walks medical device manufacturers through the ISO 13485 Clause 8.2.4 internal audit requirement — including audit program design, the six-step audit process, and the five most common findings auditors cite. It also covers what changed under the FDA QMSR and the new ISO 19011:2026 audit guidance.

A clause-by-clause guide to planning, conducting, and closing out ISO 13485 internal audits under the new FDA QMSR

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

The Internal Audit That Used to Be Private Isn’t Anymore

For years, medical device manufacturers treated the internal audit report as an internal document — useful for finding problems, but shielded from FDA inspectors under the confidentiality provision in the old 21 CFR 820.180(c). That protection is gone.

Since February 2, 2026, the FDA’s Quality Management System Regulation (QMSR) has been in effect, and it incorporates ISO 13485:2016 by reference rather than running a parallel U.S.-specific standard alongside it. FDA’s own Final Rule FAQ is direct about what that means for audits: “The QMSR gives the FDA the authority to inspect management review, quality audits, and supplier audit reports. The exceptions that existed in the QS regulation at § 820.180(c) are not maintained in the QMSR.” That’s not a third-party interpretation — it’s FDA’s own published position.

So this isn’t limited to internal audit reports. Management review minutes and supplier audit reports lost the same protection. A checklist you run through once a year to satisfy Clause 8.2.4 on paper is no longer a low-risk approach — it’s now a document an inspector may read line by line, and so are the meetings where leadership reviewed it.

From the Floor: I’ve built and run internal audit programs at facilities with 500-plus employees, and the finding that costs organizations the most isn’t a missing procedure — it’s a corrective action that gets closed on paper before the root cause is actually fixed. As a certified ISO 9001 Internal Auditor, I’ve sat across the table from auditors who catch that in about ninety seconds. Whether you’re auditing to ISO 9001 or ISO 13485, the internal audit only works if it’s harder on you than the external one will be.

Before your next surveillance audit, most quality teams don’t fail because they misunderstand Clause 8.2.4 — they fail because their audit program looks complete on paper but hasn’t been stress-tested against real objective evidence. Run your QMS through the free ISO 13485 Gap Assessment Checklist before an inspector or a Notified Body does it for you.

In This Guide

What ISO 13485 Clause 8.2.4 actually requires
How internal audits differ from supplier and certification audits
What Clause 6.2 actually requires of your auditors — and what “competent” really means
Building a risk-based annual audit program
The audit process: planning, evidence, reporting, and CAPA follow-up
A real finding-to-CAPA example, start to finish
The five most common internal audit findings — and how to avoid them
What changes if you’re audited under MDSAP
What changed under the FDA QMSR and ISO 19011:2026
Whether you need outside help or can run this internally

👉 Start Here (Top Resources)

9001Simplified — Build Your Audit Program Without a Consultant — documentation and procedure templates you can adapt for a Clause 8.2.4 internal audit program without hiring outside help.
ISO 13485:2016 — ANSI Webstore — the official standard, which every internal audit checklist should be built against directly, not from a secondhand summary. Use code CC2026 for 5% off your order through December 31, 2026.
ISO 13485 Training — BSI Group — formal internal auditor training if you need documented Clause 6.2 competence records for your audit team.

What Clause 8.2.4 Actually Requires

ISO 13485 requires internal audits under Clause 8.2.4 to verify that QMS processes are implemented and effective, catch nonconformities, and surface QMS deficiencies early enough that they don’t become product-safety or regulatory problems. That sounds close to ISO 9001’s internal audit clause, and it is — but ISO 13485 asks for more.

Clause 8.2.4 requires that internal audits determine conformity to planned arrangements, the requirements of the standard, the organization’s own QMS requirements, and applicable regulatory requirements — and unlike ISO 9001, ISO 13485 explicitly requires the audit program to account for regulatory requirements such as FDA 21 CFR Part 820, EU MDR, or MDSAP alongside the standard itself. Teams that build their audit program purely off the ISO 13485 clause structure, without folding in the regulatory layer, are the ones who get flagged.

Most common finding: auditors treat Clause 8.2.4 as a documentation-review exercise and skip the regulatory cross-reference entirely. If your audit checklist doesn’t ask “does this also satisfy 21 CFR Part 820 or MDR Article 10?” it isn’t finished.

Audits must assess conformity across critical processes — design and development under Clause 7.3, corrective action under Clause 8.5.2, preventive action under Clause 8.5.3, production under Clause 7.5, and document control under Clause 4.2 — using objective evidence like device history records, audit trails, and validation records. Auditors must be trained, qualified, and independent of the area they’re auditing, with that competence documented under Clause 6.2.

If you are already ISO 9001 certified → your internal audit infrastructure transfers directly, but your checklist needs a regulatory column added for every process area, not just a conformity column.

Internal Audits vs. Supplier Audits vs. Certification Audits

Comparison infographic showing internal audits, supplier audits, and certification audits under ISO 13485. — Understanding the differences between internal, supplier, and certification audits improves audit planning and regulatory compliance.

Manufacturers frequently conflate these three, and an auditor will notice immediately if your procedure does too.

Audit Type	Governing Clause	Performed By	Primary Purpose
Internal Audit	Clause 8.2.4	Trained internal personnel, independent of the area audited	Verify your own QMS conforms to the standard and your own procedures
Supplier Audit	Clause 7.4.1	Quality or supplier quality personnel	Verify external providers meet quality and regulatory requirements
Certification Audit	ISO/IEC 17021-1	Accredited third-party Notified Body or registrar	Determine whether the full QMS meets ISO 13485 for certification

ISO 13485 requires internal audits, just as its sister standard ISO 9001 does, and they exist for two reasons: to confirm the QMS meets the standard’s requirements, and to confirm the organization actually follows its own rules. A strong internal audit program is what makes a certification audit uneventful instead of a fire drill.

Auditor Competence: What Clause 6.2 Actually Requires

This is the section most audit programs get thin on, and it’s where a surprising number of otherwise solid internal audit programs fall apart under scrutiny.

Clause 6.2 requires that anyone doing work affecting product quality — and that includes auditors — be competent based on appropriate education, training, skills, and experience. ISO 13485 doesn’t spell out a fixed list of required knowledge areas the way a checklist would, but three areas consistently show up when a Notified Body reviews auditor files:

The standard itself. A working knowledge of ISO 13485:2016 clause structure, not just the SOPs written to satisfy it.
Audit methodology. Understanding of the audit cycle — planning, evidence gathering, reporting, follow-up — along with the difference between a minor observation and a major nonconformity. ISO 13485’s own note under Clause 8.2.4 points auditors toward ISO 19011 for this.
Applicable regulatory context. Basic familiarity with the regulations that apply to your product and markets — 21 CFR Part 820, EU MDR, MDSAP — not full legal mastery, but enough to recognize when a finding also touches a regulatory requirement.

Competence is not the same thing as certification. ISO 13485 does not require a certified internal auditor credential, and ISO 19011 doesn’t mandate formal training either — the standard’s actual requirement is that the audit process ensure objectivity and impartiality, and that competence be evaluated and documented. In practice, though, “read and understand the internal procedure” is not evidence Notified Bodies accept as sufficient. An auditor who can’t produce a training record, a completed course certificate, or documented on-the-job evaluation showing how their competence was assessed is a finding waiting to happen — even if that person is, in fact, good at the job.

What acceptable training records look like in practice:

A certificate of completion from an ISO 13485 internal auditor course (typically covering the standard itself plus ISO 19011 audit methodology) — see BSI vs. ISOQAR if you’re deciding where to send your team for that training
Internal on-the-job qualification records — a documented mentored audit or two, signed off by a qualified lead auditor
A training matrix that ties each auditor to the specific processes and clauses they’re qualified to audit, refreshed when the QMS or the standard changes

Auditor independence gets checked alongside competence. The most frequent failure here isn’t a skills gap — it’s a quality manager who owns a process auditing that same process, or an auditor rotation that never actually rotates the highest-risk areas like design controls.

If you are not confident your auditor files would hold up to this list → that’s a fifteen-minute file review, not a project, and it’s worth doing before your next Notified Body visit rather than during it.

Building a Risk-Based Audit Program

The audit program must cover every process, department, and site within your QMS scope, with audit frequency determined by the status and importance of each process along with the results of prior audits. High-risk processes — design and development, production, CAPA, and complaint handling — typically need at least annual coverage, while lower-risk support functions can be audited less frequently if previous results were consistently clean.

Most manufacturers get the frequency question backwards. They audit everything on a flat annual calendar instead of weighting toward where the last audit found something. If your CAPA process had a finding last year, auditing it again on the same twelve-month clock as your HR training records is a scheduling decision an inspector will question.

If you are preparing for your first surveillance audit under the new QMSR → build your program around the regulatory cross-reference first, then layer the standard’s clause structure on top of it — not the other way around.

The Internal Audit Process, Step by Step

Infographic illustrating the ISO 13485 internal audit process from planning through CAPA verification for medical device quality management systems. — The six-step ISO 13485 internal audit process helps medical device manufacturers identify nonconformities and verify corrective actions.

Prepare a checklist based on the relevant clauses of ISO 13485, your documented procedures, and applicable regulatory requirements — a good checklist prompts investigation rather than simply confirming what’s already assumed to be true.

1. Scope and schedule. Define which processes, sites, and clauses are in scope for this audit cycle.

2. Documentation review. Analyze the quality manual, procedures, and prior audit reports before setting foot on the floor — this is where checklists get mapped to specific clauses.

3. Opening meeting. Confirm scope, objectives, and methodology with the auditee before evidence-gathering begins — this sets the tone for the entire audit.

4. Evidence gathering. Collect objective evidence through interviews, direct observation, and document/record review — no finding should be written down without evidence behind it.

5. Reporting. Findings get written up, classified by severity, and routed to the process owner and management.

6. CAPA follow-up. Every corrective action needs documented root cause analysis appropriate to the significance of the nonconformity, with effectiveness verified before the CAPA is closed.

Most teams execute steps 1 through 5 competently. Step 6 is where programs fall apart — a CAPA gets marked closed the day the immediate fix is implemented, with no verification that the fix actually held.

Trigger: If your last three internal audits found the same category of nonconformity in different words each time, that’s not three separate findings — that’s one root cause your CAPA process never actually reached.

Before your next audit cycle, check your CAPA closure process against what auditors actually verify — most teams don’t realize how thin their effectiveness checks are until someone else reviews them.

A Real Finding, Start to Finish

Steps on a page are easy to nod along with. Here’s what a properly closed finding actually looks like end to end, using one of the most common design-control gaps auditors find.

Stage	What It Looked Like
Finding	During a design and development audit, three of twelve design verification records sampled were missing the reviewer’s signature. Work was completed and dated, but sign-off wasn’t captured.
Objective Evidence	Design History File records DHF-114, DHF-119, and DHF-122, cross-referenced against the design review meeting minutes showing the reviews occurred.
Nonconformity Statement	“Design verification records DHF-114, DHF-119, and DHF-122 lack the required reviewer signature per QMS-SOP-014, Section 6.2. Design and development control per ISO 13485:2016 Clause 7.3.6 requires verification results, including necessary actions, to be recorded.”
Root Cause	Investigation traced it to a recent SOP revision that moved the sign-off step later in the workflow. Staff hadn’t been retrained on the updated sequence — the procedure changed, but the training that should have accompanied it under Clause 6.2 didn’t happen.
Correction	The three records were completed retroactively with the reviewer’s signature and a note explaining the delay, reviewed and accepted by the quality manager.
Corrective Action (CAPA)	Retrain design team on the revised sign-off sequence; add a mandatory signature field to the design review template so records can’t be filed incomplete.
Effectiveness Check	Sample the next ten design verification records over the following quarter. Zero missing signatures required to close the CAPA as effective.

Notice what makes this closeable rather than cosmetic: the root cause isn’t “people forgot” — it’s a training gap tied to a specific procedure change, and the corrective action addresses the system, not just the three records. That’s the difference between a finding that stays closed and one that reappears with different reference numbers next year.

The Five Most Common Findings

Infographic highlighting the five most common ISO 13485 internal audit findings in medical device quality management systems. — The most common ISO 13485 internal audit findings often involve documentation, CAPA effectiveness, auditor competence, and risk-based planning.

Incomplete audit records — missing reports, plans, or linked CAPAs — is one of the most frequently cited internal audit issues. A close second is failing to apply a risk-based approach to audit planning, or simply not maintaining the internal audit schedule at all. Beyond that, auditors regularly find no timely follow-up on actions from internal audits, no records showing auditor competence against the applicable regulations, and auditors who weren’t actually impartial — reviewing work they had a hand in.

Design and development controls remain the single most frequently cited nonconformity area globally — incomplete design inputs, missing verification or validation records, undocumented design changes, or no formal design transfer procedure. See Validation & Verification Requirements for how this plays out in practice.

⚠️ If your auditor rotation lets the same person audit design controls year after year without ever being audited themselves on that same process, that’s an impartiality gap that a Notified Body will flag before you do.

If you are not confident your last internal audit would hold up under this list → that’s exactly what a structured gap assessment is for, not a guess.

Check your program against these five findings before your next audit — most gaps take under 45 minutes to identify →

MDSAP: What Changes for Multi-Market Audits

If your devices sell into more than one of the five MDSAP markets — the U.S., Canada, Australia, Brazil, or Japan — your internal audit program needs to account for a different audit model, not just an extra regulatory reference.

The Medical Device Single Audit Program lets one audit by an accredited Auditing Organization satisfy the requirements of all five participating regulators at once, in place of separate national audits. It’s built on ISO 13485:2016, but it isn’t a straight overlay — MDSAP uses a process-based audit model with a defined sequence, rather than working straight down the ISO clause list, and it maps every audit task to both the relevant ISO 13485 clause and each country’s specific regulatory requirement.

The grading system is the biggest practical difference. Where an ISO 13485 certification audit typically classifies findings as minor or major, MDSAP uses a points-based Grade 1–5 scale: nonconformities affecting clauses with indirect QMS impact start lower, direct-impact clauses start higher, and points are added for repeat findings or for a nonconforming product that was actually released. Grade 4 and 5 findings must be resolved before a certificate is issued or maintained — there’s no ambiguity about severity once the math is run.

What this means for your internal audit program: if you’re pursuing or maintaining MDSAP, your internal audits should follow the MDSAP process sequence — not just walk through ISO 13485 clauses in order — so that gaps surface in the same structure an Auditing Organization will use. The recurring findings across published MDSAP audits track closely with the same weak points internal audits should already be hunting for: open CAPAs left unclosed past a reasonable window, supplier and purchasing controls that don’t demonstrate follow-through, and root cause analysis that’s thin enough to not survive a second look.

One benefit worth knowing about: MDSAP audit reports can substitute for the FDA’s routine biennial device inspections. A well-run MDSAP program isn’t just multi-market efficiency — it can reduce how often FDA shows up separately.

What Changed: QMSR and ISO 19011:2026

Two regulatory shifts affect how internal audits get run in 2026, and both are recent enough that older internal procedures may not reflect them.

Since February 2, 2026, the FDA’s QMSR has incorporated ISO 13485:2016 by reference, replacing the former Quality System Regulation, and FDA inspections now run under Compliance Program 7382.850 rather than the old QSR framework. As covered above, the practical effect for internal audits is direct: the confidentiality safe harbor that used to apply to internal audit reports, management review records, and supplier audit reports under the old 21 CFR 820.180(c) has been removed, and FDA’s own FAQ confirms it in plain language.

Separately, ISO published the fourth edition of ISO 19011 — Guidelines for auditing management systems — on May 27, 2026, replacing the 2018 edition that had guided audit programs for nearly eight years. ISO 13485 doesn’t mandate ISO 19011 compliance directly — Clause 8.2.4 references audit principles in its own language — but Notified Bodies and experienced auditors widely treat ISO 19011 as the authoritative reference for structuring an audit program, so if your internal audit SOPs still cite the 2018 edition, expect your Notified Body to ask why.

Neither change requires rebuilding your program from scratch. Both are reasons to review your internal audit SOP this year rather than next.

Quick Audit-Readiness Checklist

✅ Audit program covers every process, site, and department in your QMS scope ✅ Audit frequency is risk-weighted, not a flat annual calendar
✅ Every checklist item maps to a specific ISO 13485 clause and the applicable regulatory requirement
✅ Auditors are independent of the area they’re reviewing, with Clause 6.2 competence records on file — not just “read and understand” sign-offs
✅ Findings are backed by objective evidence — interviews, observation, or documented records
✅ CAPA effectiveness is verified before closure, not assumed
✅ If pursuing MDSAP, internal audits follow the MDSAP process sequence, not just the ISO clause order
✅ Internal audit SOP references ISO 19011:2026, not the 2018 edition
✅ Design and development records are current — this is the single most-cited finding category

FAQ

How often does ISO 13485 require internal audits?

The standard doesn’t specify a fixed interval — it requires audits “at planned intervals” based on process risk and prior audit history. Most manufacturers audit high-risk processes like design controls and CAPA annually at minimum, with lower-risk support functions audited less frequently if history is clean.

Can the same person who performs a process also audit it?

No. Clause 8.2.4 requires auditors to be independent of the area being audited. A quality manager who owns the CAPA process, for example, shouldn’t be the one auditing CAPA compliance.

Do internal auditors need a formal certification?

No. ISO 13485 requires documented competence — education, training, skills, and experience — but doesn’t mandate a specific certification. In practice, most Notified Bodies expect more than an internal read-and-understand sign-off, so a course certificate or documented mentored-audit record is the safer standard to work toward.

Does the FDA QMSR require a separate internal audit program from ISO 13485?

No. Since the QMSR incorporates ISO 13485:2016 by reference, there isn’t a separate U.S.-specific internal audit requirement layered on top — your Clause 8.2.4 program is the audit program the FDA now expects, with the regulatory cross-reference built in.

Are internal audit reports confidential from FDA inspectors?

Not anymore. FDA’s own QMSR Final Rule FAQ confirms the confidentiality exceptions under the old 21 CFR 820.180(c) — covering internal audits, management review, and supplier audits — are not maintained under the QMSR.

What’s the difference between an internal audit and a supplier audit under ISO 13485?

Internal audits (Clause 8.2.4) evaluate your own QMS. Supplier audits (Clause 7.4.1) evaluate external providers’ ability to meet your quality and regulatory requirements. Both are required, but they’re separate programs with separate scopes.

Does MDSAP replace our ISO 13485 internal audit requirement?

No, but it changes the structure. MDSAP is built on ISO 13485 and layers in country-specific regulatory requirements from up to five markets, using a process-based sequence and a points-based Grade 1–5 nonconformity system rather than the minor/major classification used in standard certification audits.

What’s the most common reason internal audit programs fail a certification audit?

Incomplete records — missing audit reports, plans, or linked CAPAs — combined with no evidence of a risk-based approach to scheduling. Both are findings a Notified Body catches quickly because they’re procedural gaps, not technical ones.

Should we hire a consultant to run our internal audits, or can we do it ourselves?

Either can work if the auditor is properly trained and genuinely independent of the process. Many manufacturers use in-house auditors for most cycles and bring in an outside auditor periodically to test whether their internal program is actually rigorous or just familiar with its own blind spots.

📥 Free Resources

ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system
Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments
Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts
ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements
AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification

Not Sure What to Do Next?

🔹 Still researching your audit obligations? Start with ISO 13485 Documentation Requirements to understand what your QMS needs on paper before you audit it.

🔹 Ready to build or strengthen your audit program? 9001Simplified’s documentation templates can shortcut the SOP-writing process without a consultant retainer.

🔹 Need the standard itself to build your checklist against? Get ISO 13485:2016 from ANSI Webstore — code CC2026 takes 5% off through the end of 2026.

An internal audit program that only exists to satisfy Clause 8.2.4 on paper was already a risk before the QMSR removed the confidentiality safe harbor. Now it’s a document an inspector can read directly. The Standards Navigator will keep tracking what QMSR enforcement and ISO 19011:2026 mean for how medical device manufacturers actually run their audit programs — not just what the clause says.

Most manufacturers don’t lose a certification over one bad audit finding — they lose it over a pattern of findings their own internal audit program should have caught first. Organizations that treat Clause 8.2.4 as a paperwork requirement get surprised at surveillance. Organizations that treat it as their first line of defense rarely do.

The Standards Navigator tracks how ISO 13485, the FDA QMSR, and the standards that govern medical device audits actually work in practice — not just what the clause text says.

👉 Get updates on ISO 13485 audit requirements and QMSR enforcement changes 👉 Be first to access new medical device compliance checklists and gap assessment tools

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

MDR vs. ISO 13485: What’s the Difference and Which One Do You Actually Need in 2026?

EU MDR and ISO 13485 solve different problems — one is law, the other is a certifiable QMS standard. This guide breaks down the core differences, current 2026–2027 MDR transition timelines, and a decision framework for regulatory affairs teams navigating both.

A regulatory affairs guide to two rules that get confused constantly — and cost time when they are

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

The Question That Stalls Every EU Market Entry Meeting

Somewhere in almost every medical device compliance kickoff, someone asks it: “We already have ISO 13485. Doesn’t that cover MDR?”

It doesn’t. And the gap between MDR vs ISO 13485 — a certified quality management system and an EU-compliant technical file — is where CE marking timelines quietly slip by six to twelve months.

MDR (Regulation (EU) 2017/745) and ISO 13485 aren’t competing standards. They aren’t interchangeable either. One is EU law. The other is a voluntary international standard that EU law happens to lean on heavily. Confusing the two doesn’t just cost time — it costs Notified Body findings, delayed submissions, and in some cases, a device that can’t legally reach the European market on schedule.

From the floor: I’ve sat in a management review where a director insisted the ISO 13485 certificate meant the technical documentation was “basically done” for an EU submission. It wasn’t. The certificate covered their quality system — design controls, CAPA, document control. It said nothing about the clinical evaluation report, MDR classification requirements, or the device-specific evidence required for conformity assessment. They spent the next quarter closing that gap instead of reviewing it calmly six months earlier. That’s the exact mistake this article exists to prevent.

👉 Before you assume your QMS certification covers your EU submission, run the gap check. Most regulatory affairs teams don’t fail because they misunderstand ISO 13485 — they fail because they assumed certification and market access were the same milestone. Get the ISO 13485 Gap Assessment Checklist and find out before a Notified Body does.

In This Guide

What EU MDR 2017/745 actually regulates
What ISO 13485 actually certifies
The core differences, side by side
Why “ISO 13485 certified” doesn’t mean “MDR compliant”
Where the two genuinely overlap — risk management, CAPA, design controls, and more
Current MDR transition timelines and 2026 developments
Which one you need — and when you need both
Common documentation mistakes that surface in Notified Body reviews
FAQ

👉 Start Here

ISO 13485:2016 — Purchase the Official Standard — the current edition, direct from ANSI Webstore, available in multiple languages for international regulatory teams.
ISO 13485 Training Courses — BSI Group — structured training for teams building out clause-by-clause understanding ahead of certification or an MDR technical file build.

What Is EU MDR 2017/745?

MDR is law, not a certifiable management system standard. Regulation (EU) 2017/745 governs what a manufacturer must prove — about a specific device — before that device can carry a CE mark and legally reach the EU market.

It covers device classification (Class I through III), clinical evaluation and clinical data requirements, technical documentation per Annexes II and III, post-market surveillance and post-market clinical follow-up (PMCF), Unique Device Identification (UDI) and EUDAMED registration, and — for higher-risk devices — Notified Body conformity assessment under Annex IX.

MDR replaced the older Medical Device Directive (MDD) and Active Implantable Medical Devices Directive (AIMDD), and it raised the bar substantially on clinical evidence and post-market obligations compared to both.

What Is ISO 13485?

ISO 13485 is a voluntary, internationally recognized quality management system standard for organizations involved in the design, production, or servicing of medical devices. It’s certifiable — a Notified Body or accredited certification body audits your QMS against the standard’s clauses and issues a certificate if you pass.

ISO 13485 uses maintaining effectiveness language throughout, not the continual improvement language found in ISO 9001. It’s structured around risk-based thinking applied specifically to design controls, document and record control, supplier controls, CAPA, and management review — the operational backbone a device manufacturer needs regardless of which market it sells into.

Since FDA’s QMSR took effect February 2, 2026, 21 CFR Part 820 incorporates ISO 13485:2016 by reference — making it the enforceable quality management system standard for U.S. device manufacturers, not merely a reference point.

MDR vs. ISO 13485: Core Differences

Category	EU MDR 2017/745	ISO 13485
Nature	EU law — mandatory for CE marking	Voluntary international standard
Scope	Device-specific: classification, clinical evidence, technical file	Organization-wide: the QMS itself
Who assesses it	Notified Body (device-level conformity assessment)	Certification body (QMS audit)
Grants market access?	Yes — required for CE marking in the EU	No — supports it, doesn’t grant it
Geographic reach	EU/EEA market only	Recognized globally; now foundational to FDA QMSR
What it produces	Technical documentation, CER, PMS/PMCF plan, EUDAMED registration	A certificate covering your quality management system
Update cycle	Amended by EU legislative process (ongoing 2025–2027 reform)	Revised through ISO’s standard TC 210 process

Professional infographic comparing EU MDR 2017/745 and ISO 13485:2016, highlighting differences in regulatory requirements, quality management systems, CE marking, clinical evaluation, and technical documentation for medical device manufacturers. — This infographic compares EU MDR and ISO 13485, illustrating how one governs market access while the other establishes the quality management system that supports regulatory compliance.

Quick Answer:

Need CE marking? → MDR is required.
Need a compliant medical device QMS? → ISO 13485 is required.
Selling medical devices in the EU? → You almost certainly need both.

The stakes behind that table are real: the European Commission’s most recent Notified Bodies survey, published March 2026, showed roughly half of submitted MDR applications had reached certificate issuance — a gap driven largely by device misclassification, incomplete technical documentation, and thin clinical evidence, not by Notified Body capacity alone.

Why Manufacturers Conflate the Two

The most common objection I hear: “We’re ISO 13485 certified — why do we need a separate MDR effort?”

Here’s the resolution: ISO 13485 certification tells a Notified Body your quality system is sound. It says nothing about whether a specific device’s clinical evidence, risk classification, or technical file meets MDR’s requirements. A company can hold a spotless ISO 13485 certificate and still receive a Notified Body finding on a device submission because the clinical evaluation report was thin, the PMCF plan was missing, or the classification rule was misapplied under Annex VIII.

Think of it this way: ISO 13485 certifies the kitchen is clean and the process is controlled. MDR conformity assessment asks whether this specific dish meets the recipe, the nutrition label is accurate, and there’s a plan to keep checking it after it ships. You need both, but they answer different questions.

👉 If you are relying on your ISO 13485 certificate as your MDR readiness proof, that’s the gap to close first. Run the ISO 13485 Gap Assessment Checklist against your current technical files before your next Notified Body interaction.

Where MDR and ISO 13485 Overlap

Venn diagram infographic showing where EU MDR 2017/745 and ISO 13485:2016 overlap, highlighting shared quality management processes including risk management, design controls, CAPA, complaint handling, and supplier controls for medical device manufacturers. — This infographic illustrates the operational areas shared by EU MDR and ISO 13485 while distinguishing the unique regulatory and quality management requirements of each framework.

If they’re really two separate things, why does everyone talk about them in the same breath? Because the same five operational areas show up in both — just assessed from different angles.

Risk management — MDR requires risk management per Annex I general safety and performance requirements; ISO 13485 Clause 4.1.2 requires a risk-based approach throughout the QMS. Most manufacturers run one risk management process (typically ISO 14971-aligned) that satisfies both.
CAPA — ISO 13485 Clause 8.5 governs corrective and preventive action as a QMS requirement. MDR’s post-market surveillance and vigilance obligations feed directly into that same CAPA process when a field issue is identified.
Design controls — ISO 13485 Clause 7.3 sets design and development requirements; MDR’s technical documentation under Annex II leans on those same design records as evidence of a controlled development process.
Supplier controls — ISO 13485 Clause 7.4 requires supplier evaluation and monitoring; MDR expects that same supplier oversight to extend into the technical file wherever a supplier-controlled process affects device safety or performance.
Complaint handling — ISO 13485 Clause 8.2.2 sets complaint-handling requirements; MDR’s vigilance reporting obligations under Article 87 depend on that same complaint intake process to catch reportable events.

This is the practical reason ISO 13485 certification and MDR technical documentation feel like the same conversation even though they’re legally distinct: a well-run QMS produces most of the raw material an MDR technical file needs. The gap is rarely in these five areas — it’s in whether that raw material gets assembled into a device-specific technical file the way MDR expects.

MDR Transition Timelines: Where Things Stand in 2026

The transition provisions have shifted more than once since MDR took effect in May 2021, and manufacturers still working under legacy MDD or AIMDD certificates need to track the current deadlines carefully:

Class III custom-made implantable devices: compliance required by May 26, 2026
Class III and certain implantable Class IIb devices: transition extends to December 31, 2027
Most other Class IIb, IIa, and Class I devices: transition extends to December 31, 2028

Legacy device status under these extended timelines requires a valid MDD/AIMDD certificate, no significant design or intended-use change, continued compliance with the original directive, and a signed agreement with an MDR-designated Notified Body.

Separately, the European Commission published a proposal on December 16, 2025 to simplify and reduce administrative burden under both MDR and its IVDR counterpart — including changes to PRRC availability requirements and certificate validity limits. That proposal is still moving through the EU’s ordinary legislative process, and current projections put final adoption no earlier than the second quarter of 2027. Nothing in that proposal changes your obligations today. Manufacturers should keep building technical documentation to the current MDR text rather than waiting on a reform that hasn’t been adopted.

Timeline infographic showing the EU MDR transition deadlines for legacy medical devices in 2026, 2027, and 2028, along with ongoing requirements for technical documentation, clinical evaluation, post-market surveillance, and Notified Body agreements. — This timeline summarizes the current EU MDR transition deadlines for legacy medical devices while highlighting the ongoing compliance activities manufacturers must maintain throughout the transition period.

Do You Need Both? A Decision Framework

If you are selling into the EU market → MDR compliance is mandatory, full stop. ISO 13485 certification is not legally required by MDR text, but in practice Notified Bodies expect it as evidence your QMS can sustain the technical file over time.
If you are U.S.-only and not yet EU-bound → FDA’s QMSR incorporates ISO 13485:2016 by reference into 21 CFR Part 820, making alignment with ISO 13485 the foundation of U.S. medical device QMS compliance as of February 2, 2026. Third-party certification isn’t mandated by FDA, but the standard’s substance now is.
If you are already ISO 13485 certified and expanding into the EU → treat MDR as a device-level project layered on top of your existing QMS, not a QMS rebuild. The gap is almost always in clinical evidence and technical documentation, not in your quality processes.
If you are under customer or investor pressure to move fast → get the ISO 13485 gap assessment done first. It surfaces documentation gaps in days instead of finding them mid-audit.

Common Mistakes That Surface in Notified Body Review

Most common finding: Clinical evaluation reports that summarize literature but never tie evidence back to the specific device’s risk profile under Annex I general safety and performance requirements.

Other recurring gaps: PMCF plans that exist as a template but were never executed against real post-market data; UDI and EUDAMED registration treated as an afterthought instead of a parallel workstream; and design change records that don’t clearly show which MDR classification rule applied after a design modification.

⚠️ A Notified Body finding on any of these doesn’t necessarily mean your ISO 13485 QMS has failed — it usually means the QMS and the MDR technical file were built as two separate projects instead of one connected effort.

Quick Reference Checklist

✅ ISO 13485 certificate current and audit-ready
✅ Technical documentation mapped to current MDR Annex II/III requirements ✅ Clinical evaluation report tied to device-specific risk profile
✅ PMCF plan active and generating real post-market data
✅ UDI assigned and EUDAMED registration current
✅ Notified Body agreement in place if relying on legacy transition timelines
✅ Design change records show which classification rule applies post-modification

FAQ

Does ISO 13485 certification satisfy MDR requirements?

No. ISO 13485 certifies your quality management system. MDR requires separate, device-specific technical documentation, clinical evidence, and — for most devices — Notified Body conformity assessment. Certification supports MDR compliance; it doesn’t substitute for it.

Is ISO 13485 mandatory for the EU market?

MDR text doesn’t explicitly mandate ISO 13485 certification, but in practice, Notified Bodies expect a certified QMS as part of demonstrating your ability to sustain compliance. Most manufacturers pursuing MDR conformity hold ISO 13485 certification for this reason.

Do U.S.-only manufacturers need to worry about MDR?

Not directly, unless you plan to sell into the EU. However, FDA’s QMSR — effective February 2, 2026 — makes ISO 13485:2016 the operative U.S. regulation, so ISO 13485 alignment now matters regardless of whether MDR applies to you.

What’s the current MDR transition deadline for legacy devices?

It depends on device classification: Class III custom-made implantables faced a May 26, 2026 deadline, Class III and certain implantable Class IIb devices extend to December 31, 2027, and most other devices extend to December 31, 2028 — provided legacy status conditions are met.

Is the EU actually changing MDR requirements soon?

The European Commission proposed simplification changes on December 16, 2025, but the proposal is still in the EU legislative process, with final adoption not expected before the second quarter of 2027. Current MDR requirements remain fully in effect in the meantime.

What’s the biggest documentation gap Notified Bodies flag?

Clinical evaluation reports that summarize literature broadly without tying the evidence directly to the specific device’s risk profile under the general safety and performance requirements.

Can one gap assessment cover both ISO 13485 certification readiness and MDR technical file readiness?

A well-structured gap assessment should flag both, but they’re different reviews at their core — one audits your QMS against ISO 13485 clauses, the other audits your technical documentation against MDR annexes. Treat them as connected but distinct workstreams.

Where should a manufacturer start if pursuing both?

Start with the QMS. A certified, functioning ISO 13485 system gives you the document control, CAPA, and design control infrastructure that MDR technical documentation depends on. Building MDR documentation on top of a shaky QMS just relocates the problem.

📥 Free Resources

ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements before certification or a Notified Body review.
ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system from the ground up.
Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements across production environments.

Not Sure What to Do Next?

🔹 Still researching the difference between MDR and ISO 13485? Start with What Is ISO 13485? and FDA QSR vs. ISO 13485 to ground the fundamentals before your next planning meeting.

🔹 Ready to close the documentation gap? Review ISO 13485 Documentation Requirements and Validation & Verification Requirements against your current technical files.

🔹 Need to purchase the standard itself? Get ISO 13485:2016 directly from ANSI Webstore — available internationally, with multi-language editions for global regulatory teams. Use code CC2026 for 5% off through December 31, 2026.

MDR and ISO 13485 solve different problems, and treating them as one project is how audit-ready timelines slip by a quarter or more. The Standards Navigator will keep tracking both as EU reform proposals and FDA QMSR guidance continue to evolve through 2026 and 2027.

Stop Guessing Where Your MDR Gap Actually Is

Regulatory teams that treat MDR and ISO 13485 as one combined project usually discover the gap during a Notified Body review — the worst possible time to find it. Teams that separate the two, and check each on its own terms, walk into that review with documentation that already matches what’s being asked.

The Standards Navigator tracks EU MDR developments, FDA QMSR alignment, and ISO 13485 implementation detail so medical device teams aren’t relying on outdated guidance six months into a submission.

👉 Get updates on MDR, ISO 13485, and medical device regulatory changes as they happen
👉 Be first to access new gap assessment tools and documentation resources for regulatory affairs teams

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

Sterilization Standards Overview: ISO 11135, 11137, 17665, and 11607 Explained (2026 Guide)

This guide breaks down the four core sterilization standards governing medical devices — ISO 11135 (EtO), ISO 11137 (radiation), ISO 17665 (moist heat), and ISO 11607 (packaging). It covers validation requirements, Sterility Assurance Level, contract sterilizer responsibility, and the most common findings auditors cite in sterilization validation files.

What ISO Actually Requires for EtO, Radiation, Steam, and Sterile Packaging Validation

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

Your Sterilization Validation File Is the First Thing an Auditor Opens

A device that isn’t sterile doesn’t ship. That’s the entire premise behind four ISO sterilization standards most regulatory affairs teams only fully understand after a finding forces them to.

ISO 11135 governs ethylene oxide (EtO) sterilization. ISO 11137 governs radiation sterilization (gamma, e-beam, X-ray). ISO 17665 governs moist heat (steam). ISO 11607 governs the sterile barrier packaging that has to keep the device sterile until someone opens it. Supporting all four is ISO 11737, which governs bioburden determination and the sterility test methods used to validate and verify each method. None of them are optional if you’re claiming “STERILE” on a label, and under ISO 13485 and the FDA’s Quality Management System Regulation (QMSR), your device history record has to show a validated process behind that claim — not a one-time test result.

If you’re still building out your quality management system, our ISO 13485 Implementation Roadmap covers where sterilization validation fits into the broader QMS build. If you already have a QMS and are trying to close a specific gap, keep reading.

I’ve reviewed process validation files during ISO 9001 internal audits where the finding wasn’t that the process failed — it was that nobody could produce the record proving why the acceptance criteria were set the way they were. While I haven’t personally validated a sterilization process, I’ve evaluated documentation, traceability, and process validation evidence like this as part of broader QMS audits, and the pattern holds across every process type: auditors don’t just want a passing result, they want the rationale that came before it. Miss that documentation trail and it doesn’t matter how many lots passed — the finding still lands.

Most teams miss this step — check your sterilization documentation against the full standard before your next audit →

In This Guide

The four core sterilization method standards and what each one actually requires
How ISO 11607 packaging validation fits alongside method validation
Sterility Assurance Level (SAL) and why 10⁻⁶ is the number that matters
Contract sterilizer relationships — who’s responsible for what
Common audit findings in sterilization validation files
How these standards connect to ISO 13485, ISO 14971, and the FDA QMSR

👉 Start Here (Top Resources)

ISO 13485:2016 — Official Standard (ANSI Webstore) — the QMS standard that governs how sterilization validation records are controlled and maintained.
ISO 13485 Training — BSI Group — structured training on the QMS clauses that sterilization validation must satisfy.

Why Sterilization Standards Sit Inside Your QMS

Sterilization validation isn’t a standalone technical exercise — it’s a QMS output. ISO 13485 Clause 7.5.7 specifically requires validation of sterilization processes before routine use. The FDA’s Quality Management System Regulation (QMSR), effective February 2, 2026, makes ISO 13485:2016 the core requirement set for device manufacturers marketing in the U.S., with a defined set of FDA-specific additions layered on top — it’s not a loose reference to “many” of the standard’s requirements, it’s the operative regulation. That means your sterilization validation protocol, your acceptance criteria, and your revalidation schedule all have to trace back into your document control and CAPA systems — the same systems we covered in ISO 13485 Documentation Requirements and CAPA Requirements in ISO 13485.

If you are still finalizing your core QMS documentation → get the sterilization validation SOP structure right before you run your first qualification batch. Retrofitting documentation after the fact is where most rework happens.

The Standards Aren’t Interchangeable

Infographic comparing ISO 11135, ISO 11137, ISO 17665, and ISO 11607, showing the appropriate sterilization method, typical applications, and validation focus for medical devices. — Compare the four primary medical device sterilization standards and see when each ISO standard applies based on the sterilization method and validation requirements.

One of the biggest misconceptions in this space is that manufacturers can choose whichever sterilization standard fits their production schedule best. In reality, the applicable standard is dictated by the sterilization modality itself — not preference. ISO 11135 cannot substitute for ISO 11137, and neither one replaces the packaging validation requirements in ISO 11607. Method selection is a design and materials decision made early in development, and it determines which standard — and which validation pathway — applies for the life of the product.

Real-world example: a disposable syringe is commonly validated under ISO 11137 using gamma or e-beam radiation, while the sterile barrier system around it is separately validated under ISO 11607. An orthopedic power drill with onboard electronics, by contrast, often can’t tolerate radiation dose without degrading — which is why EtO validation under ISO 11135 becomes the practical path, even though it carries a longer aeration and residual-testing burden than radiation would.

Standard	Covers	Validation Focus	Typical Products
ISO 11135	Ethylene oxide (EtO)	Gas cycle validation	Electronics, plastics, mixed-material assemblies
ISO 11137	Radiation (gamma / e-beam / X-ray)	Dose validation	Disposable, polymer-based devices
ISO 17665	Moist heat (steam)	Temperature/pressure qualification	Reusable surgical instruments
ISO 11607	Sterile packaging	Seal & sterile barrier validation	All terminally sterilized devices

ISO 11135: Ethylene Oxide Sterilization

ISO 11135 covers development, validation, and routine control of EtO sterilization — the most common method for devices with mixed materials, electronics, or complex geometries that can’t tolerate radiation or heat.

The standard requires:

Process definition — establishing gas concentration, temperature, humidity, and exposure time that reliably achieves the target sterility assurance level
Installation and performance qualification — proving the chamber and load configuration actually deliver the defined process
Routine monitoring — biological indicators and process parameter records for every production cycle
EtO residual testing — confirming aeration reduces residual gas and byproducts to acceptable levels before release

Watch-outs specific to EtO: aeration time, residual limits, and material compatibility all need documented justification, not just a passing result. If you need the current edition for your validation team, ISO 11135:2014 is available through ANSI Webstore.

ISO 11137: Radiation Sterilization

ISO 11137 covers gamma, electron beam, and X-ray sterilization in three parts: requirements (Part 1), dose setting (Part 2), and dose auditing (Part 3). Radiation is common for single-use, polymer-based disposables produced at volume.

Element	What It Covers	Why It Matters in an Audit
Dose setting	Establishing the minimum dose that achieves the target SAL (e.g., VDmax or Method 1 approaches)	Auditors want to see the substantiation data, not just the final dose
Dose auditing	Ongoing verification that the substantiated dose remains effective as product or process changes occur	A missed dose audit is a common nonconformance
Material compatibility	Polymer aging, discoloration, and embrittlement risk at the selected dose	Ties directly into design verification records

If you are switching from gamma to e-beam or X-ray for the same product → you need new dose substantiation data. The modality change is not a paperwork formality. ISO 11137:2025 is the current edition covering dose-setting and dose-auditing requirements.

ISO 17665: Moist Heat Sterilization

ISO 17665 covers steam sterilization — pressurized saturated steam, typically 121°C to 134°C. It remains the preferred method for reusable surgical instruments and devices that tolerate heat and moisture, largely because it’s simple, fast, and doesn’t carry the residual or dose-substantiation burden that EtO and radiation do.

Validation under ISO 17665 centers on physical qualification (proving the autoclave load reaches and holds temperature throughout) paired with biological indicator challenge testing. The standard also requires routine control — meaning every production cycle needs monitored, recorded parameters, not just periodic spot checks. ISO 17665:2024 is the current edition.

ISO 11607: Sterile Packaging

Sterilization validation doesn’t end when the device comes out of the chamber. ISO 11607 — in two parts — governs the sterile barrier system that has to maintain sterility through distribution, storage, and shelf life until the point of use.

Part 1 covers materials, sterile barrier system design, and preformed barrier requirements. Part 2 covers validation of the forming, sealing, and assembly processes used to create that barrier. A device can pass every sterilization requirement in ISO 11135, 11137, or 17665 and still fail on the market if the package seal isn’t validated to hold sterility through the labeled shelf life.

Packaging validation goes well beyond confirming a seal exists. A complete ISO 11607 validation file typically includes seal integrity testing, burst testing, dye penetration testing, and peel strength testing to confirm the barrier holds under mechanical stress — plus transit simulation testing (ASTM D4169 is the common reference standard) to prove the package survives real-world distribution handling, and accelerated aging studies to substantiate the labeled shelf life before real-time aging data exists. Skipping any one of these doesn’t just create an audit finding — it creates a product that may not actually stay sterile on the shelf.

Most common finding: manufacturers validate the sterilization cycle thoroughly but treat packaging validation as an afterthought — seal strength testing without the accompanying shelf-life and transit simulation data auditors expect to see referenced together. ISO 11607:2019 covers both parts of the packaging validation requirement.

Sterility Assurance Level: The 10⁻⁶ Standard

Infographic illustrating the medical device sterilization validation workflow from product design and risk assessment through bioburden testing, process validation, packaging validation, Sterility Assurance Level (SAL), routine monitoring, and periodic revalidation. — Follow the complete sterilization validation workflow, from initial product design through routine monitoring and revalidation, to maintain ISO 13485 and FDA QMSR compliance.

Every one of these standards is built around the same target: a Sterility Assurance Level of 10⁻⁶, meaning no more than a one-in-a-million probability that a viable microorganism survives the sterilization process. SAL isn’t a claim you assert — it’s a number you prove through bioburden testing, biological indicator challenges, and the validation approach specified in the relevant method standard.

This is where ISO 11737 (microbiological methods) connects in. Bioburden testing under ISO 11737-1 establishes your starting point; the sterility test methods in ISO 11737-2 support validation and ongoing verification. If you haven’t mapped your bioburden data into your sterilization validation protocol, that’s a gap worth closing before your next surveillance audit.

Using a Contract Sterilizer Doesn’t Transfer the Risk

The most common objection we hear: “We use a contract sterilizer — isn’t this their responsibility?”

No. Under ISO 13485’s supplier control requirements — covered in detail in Supplier Controls for Medical Devices — the device manufacturer retains ultimate responsibility for the validated state of the sterilization process, even when a contract sterilizer physically performs it. Your quality agreement with that sterilizer needs to define who owns revalidation triggers, who reviews dose audit data, and who gets notified of process deviations. An FDA or notified body auditor will ask you these questions directly — “we outsource it” is not an acceptable answer.

Common Findings in Sterilization Validation Files

Infographic highlighting the five most common sterilization validation audit findings, including dose substantiation, packaging validation, EtO aeration and residual data, revalidation triggers, and contract sterilizer oversight. — Discover the five sterilization validation issues auditors most frequently identify during ISO 13485 and FDA QMSR assessments of medical device manufacturers.

Missing or incomplete dose substantiation rationale (radiation)
Aeration and residual data not linked to the specific product configuration tested (EtO)
Packaging validation treated as separate from — rather than integrated with — sterilization validation
Revalidation not triggered after a documented process, material, or supplier change
Contract sterilizer quality agreements that don’t specify deviation notification requirements

Common Sterilization Myths

Sterile packaging isn’t optional. It’s a validated element of the sterilization claim, not a shipping convenience.
Contract sterilizers don’t assume regulatory responsibility. The device manufacturer does, regardless of who runs the cycle.
Passing one validation run doesn’t eliminate revalidation requirements. Process, material, or supplier changes reset the clock.
SAL isn’t measured by a single sterility test. It’s established through bioburden data, biological indicator challenges, and the validation approach specified in the method standard — not one passing sample.

Quick Audit Checklist

✅ Process definition and qualification records on file for the sterilization method used
✅ Dose substantiation and dose audit data current (radiation only)
✅ Residual and aeration data linked to product-specific testing (EtO only)
✅ Packaging validation (ISO 11607-1 and -2) referenced alongside sterilization validation
✅ Bioburden data mapped to SAL 10⁻⁶ justification
✅ Contract sterilizer quality agreement defines revalidation and deviation ownership
⚠️ Revalidation schedule reviewed after any process, material, or supplier change

Not sure your current documentation would hold up? Run it against the ISO 13485 Gap Assessment Checklist before your next scheduled audit →

FAQ

What’s the difference between ISO 11135 and ISO 11137?

ISO 11135 governs ethylene oxide (EtO) sterilization, a gas-based low-temperature method suited to mixed-material and electronic devices. ISO 11137 governs radiation sterilization — gamma, e-beam, and X-ray — typically used for high-volume, polymer-based disposables. They require different validation approaches: dose substantiation for radiation, and gas concentration/exposure/aeration qualification for EtO.

Does ISO 17665 apply to reusable devices?

Yes. ISO 17665 covers moist heat (steam) sterilization, which is the most common method for reusable surgical instruments and devices that tolerate heat and moisture without degradation.

Is ISO 11607 required if I use a contract packaging supplier?

Yes. ISO 11607 validation requirements apply regardless of whether packaging design and sealing are performed in-house or by a contract supplier. The device manufacturer is responsible for confirming that validation data exists and is current for the specific packaging configuration used.

What is Sterility Assurance Level (SAL) and why is 10⁻⁶ the target?

SAL is the probability that a single viable microorganism survives a sterilization process. A SAL of 10⁻⁶ means no more than a one-in-a-million chance — the internationally recognized benchmark for terminally sterilized medical devices across ISO 11135, 11137, and 17665.

Do I need to revalidate if I switch contract sterilizers?

In most cases, yes. A change in sterilizer, chamber configuration, or load pattern can affect cycle parameters even when the method and standard stay the same. Revalidation requirements should be defined in your change control procedure, not decided case by case.

How does ISO 14971 relate to sterilization validation?

ISO 14971 risk management informs the acceptance criteria and failure mode analysis behind your sterilization validation protocol — particularly for identifying what happens if sterility assurance isn’t achieved. See our breakdown in Risk Management in Medical Devices for how the two standards connect.

Does the FDA QMSR require anything beyond ISO 13485 for sterilization?

The QMSR incorporates ISO 13485 by reference, so the core sterilization validation requirement flows through Clause 7.5.7. FDA also maintains a Recognized Consensus Standards database mapping specific editions of ISO 11135, 11137, 17665, and related standards — always confirm current recognition status before citing a specific edition in a submission.

What’s the most common reason sterilization validation fails an audit?

Missing documentation trail — not process failure. Auditors most often cite an inability to produce the rationale behind acceptance criteria, dose substantiation, or revalidation triggers, even when every routine monitoring record shows a passing result.

Not Sure What to Do Next?

🔹 Still researching your sterilization pathway? Read What Is ISO 13485? to see how sterilization validation fits into the full QMS picture.

🔹 Ready to close documentation gaps before your next audit? BSI Group’s ISO 13485 training walks through the clauses that govern sterilization validation records.

🔹 Need the actual standard text for your validation team? If you’re purchasing more than one, the ANSI Webstore Medical Device Packages bundle covers ISO 13485, ISO 14971, and the sterilization standards together — often at a lower combined cost than buying each individually.

📥 Free Resources

ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system.
Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments.
Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts.
ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements.
AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification.

The Documentation Trail Is the Real Deliverable

Sterilization validation isn’t a lab exercise you complete once and file away — it’s a living record your QMS has to maintain across every process, material, and supplier change. Get the documentation structure right the first time, and the biological indicator result becomes the easy part. The Standards Navigator will keep tracking updates to ISO 11135, 11137, 17665, and 11607 as FDA recognition status evolves, so you’re not caught citing a superseded edition.

📬 Stay Ahead of Your Next Sterilization Audit

Most sterilization validation findings don’t come from a failed cycle — they come from a documentation trail an auditor can’t follow six months later. Manufacturers who treat sterilization validation as a one-time project end up scrambling before every surveillance audit; the ones who build revalidation triggers into their change control process rarely get surprised.

The Standards Navigator tracks sterilization, packaging, and QMS standard updates specifically for medical device manufacturers navigating ISO 13485 and the FDA QMSR.

👉 Get updates on sterilization and medical device compliance standards 👉 Be first to access new ISO 13485 gap assessment tools and checklists

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

Validation & Verification Requirements: What ISO 13485 and the New FDA QMSR Actually Demand (2026 Guide)

ISO 13485 Clause 7.3 requires distinct verification and validation evidence — and the FDA’s new QMSR, effective February 2, 2026, makes the distinction matter more than ever. This guide breaks down design verification, design validation, process validation, and software validation requirements, and shows manufacturers how to build a traceability matrix that survives an audit or inspection.

ISO 13485 verification and validation requirements explained for medical device manufacturers navigating the QMSR transition

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

The Documentation Gap That Fails Design History Files

A design verification report that confirms the device meets its own specifications is not the same thing as a validation report that confirms the device meets the user’s actual needs. Auditors know the difference. Regulatory affairs teams sometimes don’t find out until an FDA inspector or notified body assessor pulls the Design History File and asks for both — and only one exists.

That gap has gotten more consequential, not less. The FDA’s Quality Management System Regulation took effect February 2, 2026, formally incorporating ISO 13485:2016 into 21 CFR Part 820 by reference. Verification and validation records that used to satisfy QSR expectations are now being evaluated against ISO 13485 Clause 7.3 directly — and the two frameworks don’t document V&V identically.

From the Floor: As a certified ISO 9001 Internal Auditor, I’ve sat across the table from teams who could produce a stack of test reports but couldn’t answer a simple question: which of these prove the design meets the specification, and which prove it meets the user’s need? Verification and validation get treated as interchangeable paperwork until an auditor separates them — and by then it’s a finding, not a conversation. The QMS documentation discipline that catches this before an audit is the same discipline that catches it before a submission.

If your last internal audit didn’t clearly separate verification evidence from validation evidence, that’s the gap worth closing first.

Run a clause-by-clause gap check before your next surveillance audit or FDA inspection — the ISO 13485 Gap Assessment Checklist below is built for exactly this kind of documentation review. Most teams miss the verification/validation split until it’s flagged.

👉 ISO 13485 Gap Assessment Checklist

In This Guide

What verification and validation mean under ISO 13485 Clause 7.3, and why they are not interchangeable
How process validation (Clause 7.5.6) differs from design validation
Software validation requirements for devices and manufacturing/QMS software
What changed under the FDA QMSR effective February 2, 2026
The most common V&V documentation failures found in audits and inspections
How to structure a verification and validation plan that survives scrutiny

👉 Start Here (Top Resources)

If you’re building or auditing a verification and validation process, these are the two resources worth starting with:

Get ISO 13485 training from BSI Group — BSI’s ISO 13485 training programs walk quality and regulatory teams through Clause 7.3 requirements in detail, including how design controls map to verification and validation evidence.
Purchase the official ISO 13485:2016 standard from ANSI Webstore — the authoritative source for Clause 7.3 language. ANSI Webstore serves international buyers and offers the standard in multiple formats. Use code CC2026 for 5% off.

Verification vs. Validation: The Core Distinction

Comparison infographic explaining the differences between ISO 13485 verification and validation requirements under ISO 13485:2016, including design inputs, intended use, testing methods, timing, applicable clauses, and common audit findings. — This comparison illustrates how verification and validation serve different purposes under ISO 13485 and why both are required for compliant medical device design controls.

Verification confirms that design outputs meet design inputs. Validation confirms that the finished device meets user needs and intended use. That one-sentence distinction is where most documentation failures start, because the two activities can look procedurally similar — testing, measuring, comparing results against criteria — while answering completely different questions.

Element	Design Verification	Design Validation
Question answered	Did we build the design correctly?	Did we build the correct design?
Compared against	Design inputs / specifications	User needs / intended use
Typical methods	Bench testing, inspection, analysis, comparison to similar designs	Clinical evaluation, simulated use testing, human factors studies
Timing	Throughout design and development	Under defined operating conditions, on initial production units or equivalent
ISO 13485 clause	7.3.6	7.3.7
Common failure	Testing against internal spec only, no traceability to input	Validating on prototypes instead of production-equivalent units

Most common finding: auditors and FDA investigators repeatedly cite validation performed on non-representative units — bench prototypes, early builds, or units built on equipment that doesn’t match production. ISO 13485 Clause 7.3.7 specifically requires validation on production or production-equivalent units, under defined operating conditions.

Verification and Validation in Practice: An Infusion Pump Example

Take a manufacturer developing an infusion pump. Design verification confirms the device meets its own engineering specifications:

✅ Flow rate accuracy within the specified tolerance
✅ Battery life meets the stated runtime under load
✅ Alarm volume meets the decibel specification

Design validation confirms something different — that the device works safely in the hands of the people who will actually use it:

✅ Nurses can operate the pump correctly and safely during simulated or actual clinical use
✅ The alarm is audible and distinguishable in a realistic hospital environment, not a quiet test lab
✅ Labeling and instructions for use are understood by the intended users without additional training

A pump can pass every verification test and still fail validation — accurate flow rate and long battery life mean nothing if a nurse under time pressure misreads the alarm or misinterprets the instructions. That’s the gap Clause 7.3.7 is built to catch, and it’s why validation has to happen on production-equivalent units under conditions that resemble actual use.

Design Verification Requirements

Clause 7.3.6 requires that design verification confirms outputs meet input requirements, with results and conclusions recorded, including the methods, dates, and individuals performing the verification. In practice, that means every design input needs a traceable verification activity — not a general statement that “the device was tested.”

If you are building a Design History File from scratch → start with a traceability matrix that maps every design input to its verification method and result before writing a single test protocol. Retrofitting traceability after testing is where most rework happens.

If you are already ISO 9001 certified and adding ISO 13485 → your existing design control process likely covers verification structurally, but it almost certainly lacks the input-to-output traceability rigor ISO 13485 auditors expect. That’s the gap to close first, not the documentation format.

👉 Before You Build Another Test Protocol

Most verification failures aren’t testing failures — they’re traceability failures. Run your design inputs against your current verification records now and find the gaps before an assessor does. →

Design Validation Requirements

Design validation under Clause 7.3.7 must be performed on production or production-equivalent units, under defined operating conditions, and must include risk analysis where applicable — which is where ISO 14971 risk management intersects directly with design controls. Validation isn’t complete until it addresses actual clinical or user-environment conditions, not lab conditions that approximate them.

Objection: “Our device is low-risk — do we really need formal simulated-use validation?” Even Class I and low-risk Class II devices need validation evidence proportional to risk, and “proportional” still means documented, traceable, and tied to intended use. A shorter validation plan is defensible. No validation plan is not.

Clinical evaluation, when required, and human factors/usability testing both fall under validation, not verification — a distinction that matters for regulatory submissions referencing FDA guidance on human factors engineering.

Process Validation Under Clause 7.5.6

Infographic explaining the three phases of process validation under ISO 13485, including Installation Qualification (IQ), Operational Qualification (OQ), and Performance Qualification (PQ), with key activities, outputs, and compliance requirements. — This infographic explains the roles of IQ, OQ, and PQ in process validation, helping manufacturers understand how each qualification stage supports ISO 13485 and FDA QMSR compliance.

Separate from design validation, ISO 13485 Clause 7.5.6 requires validation of processes where the resulting output cannot be verified by subsequent monitoring or measurement — sterilization, certain sealing and bonding processes, injection molding parameters, and software used in production are the classic examples.

Process validation requires:

✅ Defined criteria for review and approval of the process
✅ Approval of equipment and qualification of personnel
✅ Use of specific methods, procedures, and acceptance criteria
✅ Requirements for records (Clause 4.2.5)
✅ Revalidation criteria, including criteria for triggering revalidation

Most auditors and FDA investigators expect this evidence structured around three stages: Installation Qualification (IQ), Operational Qualification (OQ), and Performance Qualification (PQ).

Installation Qualification (IQ) confirms that equipment and supporting systems are installed correctly, according to the manufacturer’s specifications and the site’s own installation requirements — including verified utilities, calibration status, and documentation of the as-installed configuration, not just a checklist that the equipment arrived and was plugged in.

Operational Qualification (OQ) confirms that the equipment operates as intended across its full specified operating range, not just at a single nominal setting. For a sterilization process, that means testing at the upper and lower bounds of temperature, time, and pressure defined in the process specification — not only the target parameters.

Performance Qualification (PQ) confirms that the process consistently produces conforming output under actual production conditions, typically across multiple runs and, where risk warrants it, multiple operators, shifts, or lots. PQ is where most revalidation triggers get defined, since it establishes the baseline the process must continue to meet.

If you are validating a sterilization or bonding process for the first time → build your IQ/OQ/PQ protocol before ordering test units. Retrofitting an IQ after OQ testing has already started is a common finding, and it undermines the traceability an assessor is looking for.

If your process hasn’t changed but your equipment or facility has → IQ typically needs to be repeated even when OQ and PQ parameters stay the same, since IQ is tied to the specific installation, not the process design.

Skipping straight to PQ — running production and calling the passing output “validation” — is one of the most common shortcuts auditors flag, because it skips the evidence that the equipment itself is capable of consistently meeting the operating range the process depends on.

If you are outsourcing sterilization or bonding processes → your supplier controls documentation needs to show that you’ve verified the supplier’s process validation, not just received a certificate of conformance.

Software Validation Requirements

Software validation shows up in two places under ISO 13485, and conflating them is a recurring audit finding: software that is part of the device (or used in its production) versus software used for quality management purposes, such as electronic QMS platforms or CAPA tracking tools. Both require validation appropriate to their use, application, and risk — but the depth and method differ substantially, and design-control software validation should be traceable back to the same input/output structure as hardware verification.

What the FDA QMSR Changed for U.S. Manufacturers

The FDA’s Quality Management System Regulation replaced the legacy Quality System Regulation under 21 CFR Part 820, effective February 2, 2026, incorporating ISO 13485:2016 by reference rather than maintaining a separately worded U.S. regulation. For manufacturers who were already ISO 13485 certified, the operational impact on verification and validation practices is smaller than the documentation-mapping impact: DHF, DMR, and DHR content doesn’t necessarily need renaming, but it does need a clear mapping showing where ISO 13485 Clause 7.3 requirements are satisfied within existing U.S. records.

If you were operating under legacy QSR language only → this is the trigger to formally adopt ISO 13485 Clause 7.3 verification/validation terminology and structure, since FDA inspectors are now trained against the ISO clause structure, not the old Part 820 subparts.

Common V&V Documentation Failures

The same handful of gaps show up repeatedly in ISO 13485 QMS audits:

No traceability matrix linking design inputs to verification methods and results
Validation performed on prototypes rather than production-equivalent units
Missing revalidation criteria for processes that later change equipment, materials, or parameters
Software validation treated as one-size-fits-all instead of scaled to risk and application
Verification and validation dates, methods, and personnel not fully recorded, leaving conclusions without traceable support

👉 Before Your Next Notified Body Assessment

If you’re not confident your traceability matrix would hold up under document review, that’s the exact gap the ISO 13485 Gap Assessment Checklist was built to catch — in under 45 minutes. →

Building a Verification & Validation Plan That Holds Up

A defensible V&V plan starts with the traceability matrix, not the test protocols. Build it in this order:

List every design input and requirement
Map each input to a specific verification method and acceptance criterion
Identify which requirements also require validation evidence, and under what conditions
Define production-equivalent unit criteria before validation begins
Build revalidation triggers into the plan up front — not as an afterthought after a process change

This structure is what turns a stack of individual test reports into a Design History File that answers an assessor’s questions instead of prompting more of them.

Workflow infographic illustrating how verification and validation fit into the ISO 13485 design control process, from user needs and design inputs through production-equivalent units, validation, and Design History File documentation. — This workflow shows how verification and validation integrate into ISO 13485 design controls to produce a complete, traceable Design History File for regulatory compliance.

Quick Audit Checklist

✅ Every design input has a documented verification method and result
✅ Validation was performed on production or production-equivalent units
✅ Risk analysis is referenced in the validation rationale
✅ Process validation records include revalidation criteria
✅ Software validation is scaled to intended use and risk
✅ Verification and validation records include dates, methods, and personnel
⚠️ Watch for validation evidence copied from an earlier device without device-specific justification

FAQ

What is the difference between verification and validation in ISO 13485?

Verification confirms design outputs meet design inputs — did we build it correctly. Validation confirms the finished device meets user needs and intended use — did we build the correct thing. They require separate evidence and cannot substitute for each other.

Does ISO 13485 require validation on production units?

Yes. Clause 7.3.7 requires design validation on production or production-equivalent units under defined operating conditions, not on early prototypes or bench models that don’t reflect final manufacturing.

What processes require process validation under Clause 7.5.6?

Any process where output cannot be fully verified by later inspection or testing — common examples include sterilization, certain welding and bonding processes, injection molding, and adhesive curing.

How did the FDA QMSR affect verification and validation requirements?

The QMSR, effective February 2, 2026, incorporates ISO 13485:2016 into 21 CFR Part 820 by reference. Manufacturers now need documentation that maps clearly to ISO 13485 Clause 7.3, even if internal DHF/DMR/DHR naming stays the same.

Do low-risk devices still need design validation?

Yes, though the depth can scale with risk. A shorter, risk-justified validation plan is acceptable; skipping validation entirely is not.

Does software need separate validation from the device it’s part of?

Software validation is required both for software that’s part of or used in producing the device, and for software used for quality management purposes — but the required depth and method differ by application and risk.

What’s the most common finding auditors cite for validation?

Validation conducted on non-representative units — prototypes or early builds that don’t match production configuration or manufacturing conditions.

Where does risk management fit into verification and validation?

ISO 14971 risk management activities feed directly into what needs validation and how rigorously, particularly for design validation rationale and process revalidation triggers.

📥 Free Resources

ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements, including design control and V&V documentation gaps
ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system
Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments
Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts
AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification

Not Sure What to Do Next?

🔹 Still researching your V&V documentation gaps? Start with the ISO 13485 Gap Assessment Checklist — it maps directly to Clause 7.3 verification and validation requirements.

🔹 Ready to build a compliant V&V process? BSI Group’s ISO 13485 training covers Clause 7.3 requirements in the depth a design control rebuild needs.

🔹 Need the standard itself to build your traceability matrix against? Get ISO 13485:2016 from ANSI Webstore — code CC2026 takes 5% off, and international formats are available.

Verification proves your engineers met the specification. Validation proves your customers can safely use the product. Auditors expect both. Regulators require both. A complete Design History File demonstrates both through traceable evidence — not one comprehensive-sounding report that tries to do both jobs at once.

Stay Ahead of the Next V&V Finding

Design History File gaps rarely surface during routine work — they surface during an audit or inspection, when there’s no time left to fix them. Manufacturers who catch the verification/validation split early walk into assessments with a traceability matrix that answers questions before they’re asked. Manufacturers who don’t spend the assessment explaining why validation was performed on a prototype.

The Standards Navigator tracks ISO 13485, QMSR, and medical device compliance requirements as they develop — including changes that affect how verification and validation get documented.

👉 Get updates on ISO 13485 and QMSR compliance changes
👉 Be first to access new medical device gap assessment tools and checklists

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

UDI Requirements for Medical Devices: What Manufacturers Must Know in 2026

Medical device manufacturers must maintain a Unique Device Identification (UDI) system under 21 CFR Parts 801 and 830. This guide covers the DI/PI structure, GUDID submission requirements, FDA-accredited issuing agencies, direct marking for reusable devices, and how UDI compliance integrates with ISO 13485 and the FDA QMSR — including the audit findings that catch teams off guard.

What UDI requirements for medical devices mean and how to build a compliant Unique Device Identification system under FDA QMSR and ISO 13485

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

Your UDI System Has More Moving Parts Than You Think

Most medical device manufacturers know they need a UDI on their label. What most don’t account for until an audit is how many systems, procedures, and records that single barcode touches.

Your UDI isn’t just a labeling requirement. It links to your Device History Record, your GUDID submission, your CAPA system, your design change controls, and your post-market surveillance process. Miss any of those connections, and you have a UDI that looks right on the label but falls apart the moment an FDA investigator starts pulling threads.

That’s the compliance gap this article closes.

The FDA’s Unique Device Identification system, mandated under 21 CFR Part 801 and Part 830, requires medical device manufacturers to assign a standardized identifier to every device, submit key data to the Global Unique Device Identification Database (GUDID), and maintain records that connect that identifier throughout the product lifecycle. As of February 2, 2026, UDI compliance is also explicitly woven into the FDA Quality Management System Regulation (QMSR) framework under 21 CFR Part 820 — meaning your QMS and your UDI system are no longer separate compliance tracks.

I’ve walked through FDA QMSR inspections where the UDI records looked clean on paper but couldn’t be tied back to the Device History Record for a specific lot. The inspector didn’t raise a UDI finding — she raised a recordkeeping finding under QMSR. That’s how connected these systems have become. If your UDI implementation lives in a spreadsheet outside your QMS, you have an audit finding waiting to happen.

If you are building or auditing your ISO 13485 QMS and aren’t sure whether your traceability documentation covers UDI requirements, run a clause-by-clause gap check before your next audit.

👉 Download the ISO 13485 Gap Assessment Checklist — free tool for medical device QMS teams assessing compliance before a certification or surveillance audit

In This Guide

What UDI is and why the FDA created it
The two components of every UDI: Device Identifier and Production Identifier
Who counts as the “labeler” and what that means for your responsibilities
GUDID: what to submit, when, and how to stay current
FDA-accredited issuing agencies: GS1, HIBCC, and ICCBBA compared
Direct marking requirements for reusable devices
UDI exemptions and exceptions — what’s actually covered
How UDI integrates with ISO 13485, QMSR, and your QMS
Common UDI audit findings and how to avoid them
UDI for SaMD and combination products

👉 Start Here: Top Resources for UDI Compliance

Before diving in, here are the tools most useful for teams building or auditing a UDI system:

ISO 13485:2016 — ANSI Webstore — The QMS standard that governs traceability, device identification, and labeling controls for medical device manufacturers. Use code CC2026 for 5% off.
ISO 13485 Training — BSI Group — Structured training for QA professionals building or auditing a medical device QMS.

What Is the FDA UDI System?

The Unique Device Identification (UDI) system is an FDA-mandated framework requiring medical device manufacturers to assign a standardized, globally unique identifier to every device placed on the US market. The legal authority comes from Section 519(f) of the Federal Food, Drug, and Cosmetic Act. The implementing regulations live in two places:

21 CFR Part 801, Subpart B — labeling requirements for UDI placement on device labels and packaging
21 CFR Part 830 — UDI system specifications, including issuing agency accreditation and GUDID data submission

The FDA published its final UDI rule in September 2013 and phased in compliance requirements by device class. As of December 2022, enforcement delays for Class I and unclassified devices have largely expired. Any device entering the US market in 2026 should operate under full UDI compliance unless a formal exemption applies.

Why UDI exists. The system creates a single, unambiguous way to identify a medical device across its entire lifecycle — from manufacturing through distribution, clinical use, post-market surveillance, and recall. Before UDI, adverse event reports frequently identified devices by trade name only, making it difficult or impossible for FDA to link events to specific device versions, lots, or manufacturing runs. UDI closed that gap.

The practical impact is straightforward: every adverse event, complaint, CAPA, recall, or MDR filed with FDA can now be linked to an exact device version via its UDI. That connection runs both directions — your GUDID record and your internal Device History Record need to tell the same story.

The Two Components of UDI Requirements for Medical Devices

Every UDI consists of two segments. Both must appear on the label for most device types.

Device Identifier (DI)

The Device Identifier is the fixed, mandatory portion of the UDI. It identifies the labeler and the specific version or model of the device. The DI is:

Issued by an FDA-accredited issuing agency (GS1, HIBCC, or ICCBBA)
The primary key for GUDID submissions — all device attribute data is registered under the DI
Searchable in the public AccessGUDID database hosted by the National Library of Medicine

A new DI is required when:

A device change results in a new version or model
A change affects the intended use of the device
A change introduces major differences in safety or performance
A new FDA regulatory submission (510(k), De Novo, PMA) is triggered

The DI assignment decision is a change control issue. Your QMS procedures need to define the threshold at which a design or manufacturing change triggers a new DI — and that procedure needs to be followed consistently.

Production Identifier (PI)

The Production Identifier is the variable portion of the UDI. It identifies specific production characteristics of a device unit and must be included whenever the corresponding information appears on the device label.

PI Element	Include When…
Lot or batch number	Lot number appears on label
Serial number	Serial number appears on label
Manufacturing date	Manufacturing date appears on label
Expiration date	Expiration date appears on label
Distinct identification code	Required for HCT/P devices regulated as medical devices

Diagram showing the two components of UDI requirements for medical devices, including the Device Identifier (DI) and Production Identifier (PI) with key data elements used for FDA UDI compliance. — Every UDI consists of two parts: the Device Identifier (DI), which identifies the device version and labeler, and the Production Identifier (PI), which captures lot, serial number, expiration date, and manufacturing date information.

Class I devices are not required to include a PI — the DI alone satisfies UDI requirements for Class I. All dates on labels must follow the YYYY-MM-DD format per 21 CFR 801.18.

Who Is the Labeler?

Under 21 CFR Part 830, the labeler is the entity that causes the label to be applied to the device. In most cases, that is the manufacturer. But contract manufacturers, specification developers, repackagers, and relabelers can all become the labeler depending on who is responsible for what appears on the final label.

This matters because the labeler is responsible for:

Assigning the DI through an accredited issuing agency
Submitting device attribute data to GUDID before the device is placed on the market
Maintaining and updating GUDID records when device attributes change
Ensuring the UDI appears correctly on the label, packaging, and (where required) directly on the device

If your organization contracts out labeling, or if you are a specification developer whose devices are manufactured and labeled by a contract manufacturer, establish in writing who holds labeler responsibility. Ambiguity here surfaces as a finding in both FDA inspections and ISO 13485 audits.

FDA-Accredited Issuing Agencies

Three organizations are accredited by FDA to issue UDIs for medical devices distributed in the US:

Agency	Standard Used	Code Type	Best For
GS1	GTIN (Global Trade Item Number)	Numeric	Most medical device manufacturers; broadest global compatibility
HIBCC	HIBC (Health Industry Bar Code)	Alphanumeric	Healthcare-specific supply chains; common in hospital settings
ICCBBA	ISBT 128	Alphanumeric	Blood products, HCT/Ps, and products of human origin

Comparison chart of FDA-accredited UDI issuing agencies for medical devices including GS1, HIBCC, and ICCBBA with code types and recommended use cases. — Visual comparison of the three FDA-accredited UDI issuing agencies showing code formats and ideal implementation scenarios for medical device manufacturers.

GS1 is the most widely used issuing agency among medical device manufacturers and provides the broadest compatibility across global regulatory systems, including the EU’s EUDAMED. GS1 charges an initial enrollment fee and an annual renewal based on company revenue. HIBCC charges a one-time Labeler Identification Code (LIC) fee. ICCBBA is category-specific and is the required issuing agency for ISBT 128-regulated products.

Your issuing agency choice has long-term implications. It affects how your UDI is structured, what barcode symbology you use, how your labels integrate with distributor and hospital systems, and how you manage multi-jurisdiction compliance. Most manufacturers establish this relationship during product development, not during pre-market submission — don’t defer this decision.

GUDID: Submission Requirements and Timelines

GUDID — the Global Unique Device Identification Database — is FDA’s public repository for device identification data. The AccessGUDID platform, hosted by the National Library of Medicine, makes this data publicly searchable by clinicians, regulators, and purchasing organizations.

What You Must Submit

For every DI, you must submit:

Device description and proprietary name
Device class (I, II, III)
Whether the device contains latex or DEHP
Whether the device is labeled sterile
Whether the device is a single-use device
Packaging quantity and configuration
MRI safety information (where applicable)
Issuing agency and DI
Company contact information

Submission must occur before the device is placed on the market — not after the label is printed, not concurrent with distribution, before.

Submitting to GUDID

There are two submission paths:

Manual entry via the FDA GUDID web interface — suitable for small product portfolios
Electronic submission via XML upload through the Electronic Submissions Gateway (ESG) — required for larger portfolios; validated interface required under 21 CFR Part 11 where applicable

If electronic submission is not technologically feasible, a waiver may be requested in writing to FDA’s Center for Devices and Radiological Health.

Keeping GUDID Current

GUDID records must be updated whenever device attribute data changes. This is where most manufacturers fall short. A device name change, a sterilization method update, a packaging configuration change — each triggers an obligation to update GUDID. Build that trigger into your change control procedure, not as an afterthought.

If your QMS doesn’t currently have a documented procedure connecting design and manufacturing changes to GUDID update obligations, that is a gap auditors will find.

👉 Download the ISO 13485 Gap Assessment Checklist — includes traceability and labeling controls relevant to UDI compliance

Labeling Format Requirements

Under 21 CFR Part 801, the UDI must appear on the device label in two forms:

Human Readable Interpretation (HRI) — plain text that can be read without scanning equipment
Automatic Identification and Data Capture (AIDC) — a machine-readable format, typically a barcode or 2D data matrix, that can be electronically captured

Both formats must appear on the label and on all packaging levels intended for commercial distribution. Shipping containers used solely for logistics are exempt.

Barcode readability is a compliance issue, not just a quality issue. In 2026, “it looked fine when we printed it” is not a defensible audit response. Barcode print quality must be verified against ISO/IEC quality grades, and your label verification records must be maintained in the Device History Record. If your production line doesn’t include end-of-line barcode scan verification, that is an audit exposure.

Direct Marking for Reusable Devices

Reusable devices — those intended to be used more than once and reprocessed between uses — must bear the UDI directly on the device itself, in addition to the label and packaging. This is called direct part marking (DPM).

Direct marking methods vary by device material and design:

Laser etching
Chemical etching
Electrochemical etching
Inkjet or dot peen marking

The DI (not necessarily the full UDI with PI) must be permanently marked on the device. The marking must remain legible after reprocessing for the expected service life of the device. Validation records for the direct marking process, including legibility after simulated reprocessing cycles, belong in the Design History File and should be cross-referenced in the Device Master Record.

UDI Exemptions and Exceptions

Not every device is required to bear a UDI. Exemptions under 21 CFR 801.30 include:

✅ Class I devices exempt from GMP requirements under 21 CFR Parts 862–892 ✅ Individual single-use devices packaged together in a single device package, not intended for individual commercial distribution (the outer package must still bear a UDI)
✅ Devices used solely for research, teaching, or chemical analysis — not for clinical use
✅ Custom devices under 21 CFR 812.3(b)
✅ Investigational devices under 21 CFR Part 812
✅ Veterinary devices not intended for human use
✅ Devices intended for export from the United States
✅ Devices held by the Strategic National Stockpile under approved alternatives

What is not exempt: accessories. Even if the primary device is exempt, accessories regulated as medical devices require a UDI unless they independently qualify for an exemption.

If you believe a device qualifies for an exemption or need an alternative approach, 21 CFR 801.55 provides a formal process for requesting an exception from FDA.

UDI and Your ISO 13485 QMS

ISO 13485:2016 doesn’t mention UDI by name. It doesn’t need to. The standard’s traceability and labeling requirements create the documented control infrastructure that UDI compliance depends on.

The relevant ISO 13485 clauses that intersect with UDI:

Clause	Relevance to UDI
7.5.8 — Identification	Devices must be identified throughout production and storage — UDI is the primary identification mechanism for marketed devices
7.5.9 — Traceability	Records must enable tracing of device identity, components, and processing history — the DI/PI structure directly supports this
7.6 — Control of monitoring and measuring equipment	Barcode scan verification equipment must be calibrated and maintained
8.3 — Control of nonconforming product	UDI enables precise identification of affected lots in nonconformance handling
4.2.4 — Control of records	GUDID submission records, AIDC verification logs, and change control documentation are QMS records

As of February 2026, the FDA QMSR under 21 CFR Part 820 aligns US quality system requirements with ISO 13485:2016. That alignment means FDA inspectors now assess QMS infrastructure — including traceability controls — through the lens of ISO 13485 clause structure. Your UDI system needs to fit inside that framework, not sit beside it.

If you are building your ISO 13485 QMS from the ground up, the BSI Group ISO 13485 training program covers design controls, traceability, and labeling requirements in the context of FDA regulatory expectations — a practical foundation for teams that need to connect QMS infrastructure to UDI compliance.

UDI for Software and Combination Products

Software as a Medical Device (SaMD)

Software devices follow the same UDI principles as hardware devices, with adaptations for how the identifier is displayed. For standalone software distributed in packaged or downloaded form:

The UDI must be displayed when the software is launched, or accessible through a menu
Software distributed in packaged form and as a download may display the same DI
A new DI is required when software changes affect the intended use or introduce a new regulatory submission
For AI/ML-enabled devices operating under a Predetermined Change Control Plan, algorithm updates within approved boundaries may require only PI updates; changes outside the approved plan require a new DI

Combination Products

Combination products — products that combine two or more of a drug, device, and/or biological — carry UDI requirements on each device constituent part. The specifics depend on how the combination product is classified (device-led or drug-led) and whether the constituent parts would independently require UDI. FDA issued draft guidance in June 2025 addressing UDI requirements for combination products with device constituent parts — review the current guidance on FDA.gov for your specific product configuration.

Common UDI Audit Findings

These are the gaps most frequently identified during FDA inspections and ISO 13485 audits related to UDI:

⚠️ GUDID records not updated after a design or manufacturing change. The change control procedure doesn’t include a UDI/GUDID review step.

⚠️ Barcode verification records not maintained in the DHR. Labels are printed and inspected visually, but scan verification results aren’t documented.

⚠️ No documented procedure defining when a design change triggers a new DI. The threshold for DI reassignment is ambiguous.

⚠️ Direct part marking not validated. Reusable device marking process was implemented without legibility testing after reprocessing.

⚠️ UDI not linked to CAPA or complaint records. When a CAPA is opened, the affected device version is identified by trade name only — not by DI/lot.

⚠️ UDI submission timing. Device reached distribution before GUDID submission was completed.

Most of these findings have one root cause: UDI compliance was treated as a labeling project rather than a QMS integration project. Getting it right requires connecting your UDI system to change control, CAPA, complaint handling, and post-market surveillance — not just to your label artwork approval process.

Most auditors don’t find UDI problems in the labeling department. They find them in the QMS.

✅ UDI Compliance Quick Checklist

Before your next audit, verify:

[ ] DIs assigned through an FDA-accredited issuing agency (GS1, HIBCC, or ICCBBA)
[ ] GUDID records complete and submitted before device placement on market
[ ] Both HRI and AIDC formats present on all commercial distribution labels and packaging
[ ] Barcode print quality verified and records maintained in DHR
[ ] Change control procedure includes a UDI/GUDID review trigger
[ ] Direct marking validated for all reusable devices (legibility after reprocessing documented)
[ ] UDI (DI + lot/serial) linkage established in CAPA and complaint records
[ ] GUDID records updated after any applicable device attribute change
[ ] Exemption rationale documented for any device or packaging level excluded from UDI
[ ] UDI training completed and documented for personnel responsible for labeling, change control, and GUDID management

Frequently Asked Questions

What is a UDI in medical devices?

A UDI — Unique Device Identifier — is a standardized code assigned to medical devices that enables consistent identification throughout the device’s distribution and use. It consists of a Device Identifier (fixed, identifies the labeler and device version) and a Production Identifier (variable, identifies lot, serial number, expiration date, or manufacturing date). The FDA requires UDIs under 21 CFR Parts 801 and 830, and the system is enforced as part of the broader FDA QMSR quality system framework.

Is UDI required for all medical devices?

Most medical devices distributed in the United States are required to bear a UDI. Exemptions exist for certain Class I devices exempt from GMP requirements, custom devices, investigational devices, devices used solely for research, and devices intended for export. Individual single-use devices packaged in bulk are also exempt (but their outer packaging is not). Check 21 CFR 801.30 for the complete exemption list, and document any exemption determination in your quality system records.

What is GUDID and what do I need to submit?

GUDID — the Global Unique Device Identification Database — is FDA’s public repository for device identification data. Manufacturers (labelers) must submit Device Identifier data for each version or model of a device before it is placed on the market. Required data includes device description, device class, packaging information, single-use status, sterility, latex content, and MRI safety information. Records must be kept current whenever device attributes change.

What is the difference between a Device Identifier and a Production Identifier?

The Device Identifier (DI) is the fixed portion of the UDI — it identifies the labeler and the specific device version or model. It is issued by an FDA-accredited issuing agency and is the primary key in GUDID. The Production Identifier (PI) is the variable portion — it captures specific production data such as lot number, serial number, expiration date, or manufacturing date. The PI must be included whenever the corresponding information appears on the device label.

Which issuing agency should I use — GS1, HIBCC, or ICCBBA?

Most medical device manufacturers use GS1, which offers the broadest global supply chain and regulatory system compatibility. HIBCC is common in hospital-centric supply chains and is preferred by some healthcare systems. ICCBBA (ISBT 128) is required for blood products, tissues, and human-derived products. Select based on your product category, existing supply chain barcode infrastructure, customer requirements, and multi-jurisdiction needs. The decision has long-term implications — establish your issuing agency relationship during product development.

What are the UDI requirements for reusable devices?

Reusable medical devices — those intended for use more than once and reprocessed between uses — must bear the UDI directly on the device itself (direct part marking), in addition to the label and packaging. The DI must be permanently marked and must remain legible after reprocessing for the device’s expected service life. Validation records for the marking process, including legibility testing after simulated reprocessing, are required.

How does UDI connect to my ISO 13485 QMS?

UDI compliance depends on the same documented control infrastructure required by ISO 13485:2016 — traceability (Clause 7.5.9), device identification (7.5.8), control of records (4.2.4), and nonconforming product management (8.3). Under the FDA QMSR effective February 2026, FDA inspectors assess quality system infrastructure through ISO 13485 clause structure. Your UDI system must be integrated into your QMS — change control, CAPA, complaint handling, and post-market surveillance — not maintained as a separate labeling function.

What happens if my GUDID record is out of date?

An outdated GUDID record is a regulatory violation and an audit finding. It can also create downstream problems: if a recall is issued, FDA uses GUDID data to identify the scope of affected devices. If your records don’t accurately reflect the current device configuration, the recall scope may be incorrectly defined. Keep GUDID current by building a GUDID review trigger into your change control procedure.

📥 Free Resources

ISO 13485 Gap Assessment Checklist — free clause-by-clause gap assessment tool for medical device QMS teams preparing for certification, surveillance audits, or FDA QMSR alignment. Covers traceability, labeling, CAPA, and design controls.

AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause gap assessment for aerospace suppliers — included here for teams operating in both medical device and aerospace quality systems.

ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system.

Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments.

Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts.

Not Sure What to Do Next?

🔹 Still building your UDI knowledge base? Start with What Is ISO 13485? for an overview of the QMS standard that governs your traceability and labeling systems, then review ISO 13485 Documentation Requirements to understand what records your UDI system needs to generate.

🔹 Ready to assess your current QMS against ISO 13485 requirements? Download the ISO 13485 Gap Assessment Checklist and work through the traceability and labeling sections before your next audit or inspection.

🔹 Need to purchase the standard? ISO 13485:2016 is available from the ANSI Webstore — the authorized source for US manufacturers. Use code CC2026 for 5% off through December 31, 2026. The ANSI Webstore serves international buyers and offers standards in multiple languages.

UDI isn’t a checkbox. It’s the data backbone that connects your device to every regulatory touchpoint across its lifecycle — from your first GUDID submission to a potential recall years after launch. Getting the system right means integrating it into your QMS from day one, not retrofitting it after an audit finding.

The Standards Navigator covers medical device quality and compliance requirements with the same direct, practitioner-grounded approach you need to make good decisions — not just check boxes.

Subscribe and Stay Ahead

Teams that struggle with UDI compliance share one common trait: they treat it as a labeling project. Teams that pass FDA inspections treat it as a QMS integration project — and they built the documentation before the auditor walked in.

Organizations that build UDI compliance into their change control, CAPA, and post-market surveillance from the start don’t scramble before inspections. They already have the records. Organizations that don’t maintain connected systems spend inspection days searching for GUDID submission confirmations and barcode verification logs across disconnected folders and spreadsheets.

The Standards Navigator covers ISO 13485, FDA QMSR, UDI, risk management, and the full spectrum of medical device compliance requirements — for quality professionals who need the detail, not the overview.

👉 Get updates on medical device compliance and QMS implementation
👉 Be first to access new ISO 13485 resources and checklists

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

Risk Management in Medical Devices: How to Build an ISO 14971-Compliant Process in 2026

Medical device risk management is the thread that connects every element of your ISO 13485 QMS — and the first place an auditor looks. This guide covers all five stages of the ISO 14971:2019 process, required documentation at each step, how to set defensible acceptability criteria, and the most common findings in notified body and FDA audits.

A step-by-step implementation guide for medical device manufacturers building or strengthening a risk management framework under ISO 14971:2019 and ISO 13485:2016

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

Your Risk Management File Is the First Thing an Auditor Opens

Not your QMS manual. Not your SOPs. Your risk management file.

That is where a notified body auditor or FDA inspector starts — because risk management in medical devices is the thread that connects every other element of your quality system. If your risk file is thin, incomplete, or disconnected from your design and production controls, the rest of your documentation will not save you.

Most medical device companies understand that ISO 14971:2019 requires a risk management process. Fewer understand what that process actually looks like when it is fully implemented — the outputs required, the decisions that must be documented, and the points where ISO 13485:2016 Clause 7.1 and ISO 14971 intersect in ways that catch teams off guard during audits.

This article walks through the complete risk management process for medical devices: what ISO 14971 requires at each stage, how those requirements connect to your QMS, and where most teams fall short.

I have spent 25 years in heavy industrial manufacturing running quality systems under ISO 9001, managing nonconformances, and building risk-based approaches to process control. When I transitioned into the ISO 13485 space, the discipline was familiar — but the regulatory stakes were different. In manufacturing, a process failure costs you time and scrap. In medical devices, the same gap in your risk file can cost you a 483 observation, a warning letter, or a market withdrawal. The rigor required is not optional, and it is not theoretical. Every output described in this article is something auditors actively look for.

Before you read further: If you have not yet assessed where your current risk management process stands against ISO 14971:2019 requirements, start there. A structured gap assessment takes less time than an audit finding.

📥 Download the ISO 13485 Gap Assessment Checklist — Free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements, including risk management obligations under Clause 7.1.

In This Guide

What ISO 14971:2019 actually requires — the full process, not just the outputs
How ISO 13485 Clause 7.1 connects to your risk management file
The five stages of the ISO 14971 process with required documentation at each step
How to set acceptable risk criteria — the decision most teams get wrong
Post-production surveillance and why it feeds back into your risk file
The most common audit findings in risk management reviews
Training options for teams building or rebuilding a compliant process

👉 Start Here: Top Resources for Medical Device Risk Management

If you are building or rebuilding your risk management process, these are the resources that will move you fastest:

ISO 14971:2019 — ANSI Webstore — The current edition of the standard. Required reading for anyone responsible for a device risk management file. Use code CC2026 for 5% off at checkout.
ISO 13485 Training — BSI Group — BSI offers ISO 13485 implementation and auditor training that covers risk management integration in depth.
ISO 13485 Training — ISOQAR — ISOQAR provides training and certification services for ISO 13485, with risk-based thinking woven throughout their courses.

What ISO 14971:2019 Requires

ISO 14971 risk management lifecycle infographic showing the seven stages of risk management in medical devices and required outputs from planning through post-production surveillance. — A visual overview of the ISO 14971 risk management lifecycle and the documentation outputs auditors expect to see.

ISO 14971:2019 is the international standard for the application of risk management to medical devices. It applies throughout the full device lifecycle — from concept through post-market surveillance.

The standard does not prescribe a specific risk analysis method. It does not tell you to use FMEA, FTA, or a risk matrix of a particular format. What it requires is a documented, systematic process that produces specific outputs at each stage.

The core framework in ISO 14971:2019 includes:

Stage	What ISO 14971 Requires
Risk management plan	Define scope, responsibilities, criteria for risk acceptability, and review activities
Risk analysis	Identify intended use, reasonably foreseeable misuse, and associated hazards and hazardous situations
Risk evaluation	Compare estimated risk against criteria — determine if risk reduction is required
Risk control	Select and implement controls; verify effectiveness; assess residual risk and any new risks introduced
Benefit-risk analysis	Where residual risk remains, evaluate whether the overall benefit outweighs remaining risk
Risk management report	Summarize the process and confirm residual risks are acceptable
Post-production information	Collect and review field data; feed findings back into risk management

Every output — the plan, the analysis, the controls, the report — must be captured in a risk management file.

How ISO 13485 Clause 7.1 Connects

ISO 13485:2016 Clause 7.1 requires that your organization document risk management requirements throughout product realization. This is not a standalone obligation — it is a QMS-level requirement that ties your risk file to your design controls, supplier management, production processes, and CAPA system.

The key connection points:

Design and development (Clause 7.3): Risk management inputs and outputs must be included in design planning. Design reviews, verification, and validation activities must all reference and be consistent with the risk management file.

Purchasing and supplier controls (Clause 7.4): Supplier-introduced risks must be identified and addressed. If a supplier failure creates a patient hazard, that scenario belongs in your risk analysis.

Production and service provision (Clause 7.5): Special processes — sterilization, labeling, software-dependent controls — require risk-based validation. Your risk file should identify where these controls are critical and what happens if they fail.

CAPA (Clause 8.5): Post-market findings, complaints, and nonconformances are data sources for your risk management process. A complaint that reveals a hazardous situation not previously identified in your risk analysis must trigger a risk file update.

Most common finding: Auditors frequently cite a disconnect between the CAPA system and the risk management file — complaints and CAPAs are processed and closed without evaluating whether the risk file needs to be updated.

If you are evaluating your current QMS against these connection points, the gap assessment checklist above covers all of them.

The Five-Stage Risk Management Process

Stage 1: Risk Management Plan

Your risk management plan is not a form — it is a governing document for the entire risk process for a specific device. It must define:

The scope of activities (which device, which lifecycle phases)
Roles and responsibilities for risk management activities
Requirements for review of risk management activities
Criteria for risk acceptability — what level of residual risk is acceptable and on what basis

The last item is where most teams take shortcuts. Acceptability criteria cannot simply reference “ALARP” or “as low as reasonably practicable” without defining what that means for your device and patient population. Auditors will push on this.

Stage 2: Risk Analysis

Risk analysis begins with a thorough description of the device — its intended use, intended users, and reasonably foreseeable misuse. From there, you identify:

Hazards (potential sources of harm)
Hazardous situations (circumstances in which people could be exposed to a hazard)
Harm sequences (how the hazardous situation leads to harm)

ISO 14971 Annex C provides a non-exhaustive list of hazard categories: energy hazards, biological hazards, environmental hazards, hazards related to incorrect output, and others. Use it as a prompt, not as a complete list.

Common analysis methods include FMEA (Failure Mode and Effects Analysis), FTA (Fault Tree Analysis), and HAZOP. Most device teams use FMEA as the primary tool. None of these methods is required by the standard — but whatever method you use must be documented and consistently applied.

Stage 3: Risk Evaluation

Once you have estimated the probability and severity of each harm, you evaluate whether each risk requires reduction. This evaluation is made against the acceptability criteria defined in your risk management plan.

If a risk exceeds your acceptable threshold, risk reduction is required. If it falls below the threshold, you still need to document the evaluation decision — not just assume silence means acceptable.

📥 If you are not confident your current risk file covers these evaluation decisions consistently, download the ISO 13485 Gap Assessment Checklist and work through Section 7 — it maps directly to these requirements.

Stage 4: Risk Control

ISO 14971 infographic showing the risk control hierarchy and residual risk evaluation process for medical device risk management. — ISO 14971 requires organizations to prioritize design controls first, verify effectiveness, and document residual risk decisions before closing risk.

ISO 14971 requires you to follow a three-level hierarchy when selecting controls:

Inherent safety by design — eliminate or reduce the hazard through design choices
Protective measures — add guards, alarms, or protective barriers in the device or manufacturing process
Information for safety — labeling, instructions for use, training requirements

You must implement controls in this order of preference. You cannot jump to warnings and labeling as your primary control if a design solution is practicable.

After implementing each control:

Verify the control was implemented as intended
Verify the control is effective at reducing risk
Assess whether the control introduces any new hazards
Re-evaluate residual risk after all controls are applied

Stage 5: Residual Risk and Benefit-Risk Analysis

After controls are in place, residual risk will remain for most devices. If residual risk exceeds your acceptability criteria even after all practicable controls have been applied, you must perform a benefit-risk analysis: does the clinical benefit of the device outweigh the remaining risk?

This analysis must be documented. “We believe the benefit outweighs the risk” is not documentation. The analysis must reference clinical evidence, intended use, and the nature and magnitude of remaining harm.

Setting Acceptable Risk Criteria

This is the decision most risk management teams get wrong, and it is the one auditors examine most carefully.

Your risk acceptability criteria must be:

Defined before you begin risk analysis — not after you have already seen your risk estimates
Based on relevant policy, standards, and guidance applicable to your device category
Specific enough to make clear decisions — a matrix with defined severity and probability ranges, not a narrative statement

What Auditors See	What They Want to See
“We aim to reduce risk ALARP”	A defined matrix with probability/severity scales and explicit acceptable/unacceptable zones
Criteria defined after the analysis was completed	Criteria established in the risk management plan before analysis began
One set of criteria applied across all device types	Criteria appropriate to the specific device and patient population
No documented basis for the criteria chosen	Reference to applicable guidance documents (IMDRF, EU MDR, FDA guidance)

Reference points that support defensible criteria include FDA guidance on risk management for device software, IMDRF guidance documents, and the introductory notes in ISO 14971:2019 itself.

Risk Control Options and Residual Risk

One of the most common gaps in risk files is incomplete residual risk documentation. Teams identify hazards, apply controls, and then fail to document the post-control risk estimate.

Every control must have:

A documented implementation record (the control was actually applied)
A verification record (the control works as intended)
A post-control risk re-estimate (residual probability × severity)
An evaluation of residual risk against acceptability criteria

If your controls introduce new hazards — which software controls, sterilization processes, and combination products frequently do — those new hazards must be analyzed through the full process. There is no shortcut.

If you are preparing for your first ISO 13485 certification audit, verify that every risk control in your file has all four of these elements documented before your Stage 1 audit. Incomplete residual risk documentation is one of the most common major nonconformances found in initial certification audits.

BSI Group offers ISO 13485 implementation training that specifically addresses risk file documentation structure, including residual risk evaluation requirements. ISOQAR provides similar training with a certification pathway.

The Risk Management File

The risk management file is not a single document. It is a collection of records that demonstrates the complete risk management process was followed for a specific device. What it must contain:

Risk management plan
Risk analysis outputs (hazard list, probability/severity estimates)
Risk evaluation records (acceptability decisions)
Risk control records (implementation, verification, new hazard assessment)
Residual risk evaluation
Benefit-risk analysis (where required)
Risk management report
Post-production information review records

The risk management report is the capstone document. It confirms that the risk management plan was followed, all residual risks are acceptable, and appropriate methods were used to obtain relevant production and post-production information.

Your risk management file must be maintained and updated throughout the product lifecycle. It is not a one-time certification exercise.

ISO 14971 risk management file infographic showing required records and how the file integrates with ISO 13485 quality management requirements. — The risk management file is the central evidence package that demonstrates ISO 14971 compliance across the medical device lifecycle.

Post-Production Information and Surveillance

ISO 14971 Clause 9 requires a systematic process to collect and review post-production information. This includes:

Customer complaints and feedback
Field service and repair reports
Medical device reports (MDRs) and vigilance reports
Published literature and adverse event databases
Post-market clinical data

This information must be evaluated to determine whether it:

Indicates previously unidentified hazards
Changes the estimated probability or severity of a known harm
Invalidates earlier risk control decisions

If it does, your risk file must be updated. Your CAPA process must have a defined trigger for escalating post-market findings to the risk management team.

Most common finding: Post-market surveillance is treated as a regulatory reporting obligation rather than a risk management input. Complaints are processed through CAPA, but the risk file is never reviewed against complaint trends. This is a major nonconformance under both ISO 13485 Clause 8.2.1 and ISO 14971 Clause 9.

Common Audit Findings in Risk Management Reviews

These are the findings that appear most frequently in ISO 13485 and EU MDR notified body audits:

✅ Incomplete risk analysis scope — Reasonably foreseeable misuse not identified or analyzed. Risk analysis covers intended use only.

⚠️ Acceptability criteria defined after the analysis — Criteria were back-filled to match the estimates, rather than established as the decision framework before analysis began.

⚠️ Missing residual risk evaluation — Controls were implemented and verified, but no post-control risk estimate was documented.

✅ Disconnected CAPA and risk file — Complaints and CAPAs processed and closed without triggering a risk file review.

⚠️ Labeling used as the primary control — Instructions for use are cited as the risk control when a design solution was practicable.

✅ Risk file not maintained post-launch — The risk file was complete at certification but has not been updated since. Design changes, new complaint data, and field findings are not reflected.

⚠️ No benefit-risk analysis where residual risk is above acceptability threshold — Teams acknowledge residual risk exceeds their criteria but do not formally document the benefit-risk justification.

Training for Your Risk Management Team

Risk management competence is a requirement, not a preference. Your team members responsible for risk management activities must be trained — and that training must be documented.

Both BSI Group and ISOQAR offer ISO 13485 training that covers risk management integration. BSI also offers a dedicated Risk Management — Requirements (ISO 14971) e-learning course for teams who need focused training on the standard itself.

If you are already certified under ISO 13485 and preparing for a surveillance audit:

If your risk team has not been formally trained on ISO 14971:2019 since the 2019 edition was published, now is the time to close that gap. The 2019 edition introduced changes to state-of-the-art requirements and manufacturer benefit-risk responsibilities that differ from the 2007 edition.

If you are building your QMS from scratch and need structured implementation support across all 8 clauses:

If you are evaluating implementation support options, review what documentation a compliant ISO 13485 QMS requires before investing in training. It will help you scope what your team actually needs to build.

FAQ

What is the difference between ISO 14971 and ISO 13485 for risk management?

ISO 13485:2016 Clause 7.1 requires that risk management be applied throughout product realization. ISO 14971:2019 is the standard that defines how to do it — the process, the required outputs, and the documentation. ISO 13485 tells you that you must manage risk. ISO 14971 tells you how. Most medical device manufacturers must comply with both.

Is ISO 14971 mandatory?

ISO 14971 is not directly mandated by law in most markets, but it is referenced as a harmonized standard under the EU MDR 2017/745 and EU IVDR 2017/746. For FDA-regulated devices in the US, compliance with ISO 14971 supports conformance with 21 CFR Part 820 design controls requirements. As a practical matter, no notified body or FDA inspection team will accept a risk management process that does not align with ISO 14971.

What is a risk management file?

A risk management file is the complete collection of records that documents the risk management process for a specific device. It includes the risk management plan, risk analysis outputs, evaluation records, control records, residual risk documentation, benefit-risk analysis (where required), the risk management report, and post-production surveillance records. The file must be maintained and updated throughout the device lifecycle.

How often should a risk management file be updated?

Your risk management file must be updated whenever there is a change to the device, its intended use, or new information that could affect risk estimates — including complaints, adverse events, published literature, or design changes. Many organizations establish a formal periodic review (annually or at defined product lifecycle milestones) as part of their post-market surveillance process.

What risk analysis methods does ISO 14971 require?

ISO 14971 does not mandate a specific method. FMEA, FTA, HAZOP, and preliminary hazard analysis are all acceptable approaches. What the standard requires is that the method be documented, systematic, and capable of identifying hazards and estimating risk. Most medical device manufacturers use FMEA as their primary method.

What is the difference between a hazard, a hazardous situation, and harm in ISO 14971?

A hazard is a potential source of harm — for example, excessive electrical energy in a device. A hazardous situation is a circumstance in which people, property, or the environment could be exposed to the hazard — for example, a patient contact point that can carry excessive current under a specific failure condition. Harm is the physical injury or damage to health that results. ISO 14971 requires that you trace the full sequence from hazard to harm for each risk identified.

How does ISO 14971 relate to CAPA in ISO 13485?

Your CAPA process should have a defined trigger for escalating complaints, adverse events, and nonconformances to the risk management team for evaluation. If a post-market finding reveals a previously unidentified hazard or changes the estimated probability of an existing risk, your risk file must be updated. Closing a CAPA without evaluating its implications for the risk file is one of the most common major findings in ISO 13485 surveillance audits.

What changed in ISO 14971:2019 compared to the 2007 edition?

ISO 14971:2019 introduced several substantive changes: clarified the concept of state-of-the-art and how manufacturers must use it; expanded and clarified the benefit-risk analysis process; updated the overall residual risk evaluation process; and revised the structure of the standard to align with ISO management system high-level structure conventions. Teams trained only on the 2007 edition may have gaps in their current process.

📥 Free Resources

These tools are available at no cost to support your ISO 13485 and risk management implementation:

ISO 13485 Gap Assessment Checklist — Free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements, including risk management obligations under Clause 7.1
ISO 9001 Roadmap — Step-by-step implementation guide for manufacturers building or improving a quality management system
Manufacturing Compliance Checklist — Practical compliance reference covering key ISO, OSHA, and quality requirements for production environments
Supplier Quality Checklist — Evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts
AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification

Not Sure What to Do Next?

🔹 Still building your understanding of ISO 13485 requirements? Start with the ISO 13485 Implementation Roadmap — it walks through all 8 clauses and how they connect before you invest in building documentation.

🔹 Ready to implement and need training for your risk management team? Both BSI Group and ISOQAR offer ISO 13485 training with risk management integration. BSI also has a dedicated ISO 14971 e-learning course.

🔹 Need to purchase ISO 14971:2019 for your quality team? Get it from the ANSI Webstore — use code CC2026 for 5% off through December 31, 2026.

Risk management is not a documentation exercise you complete before certification and revisit every few years. It is the living framework that keeps your device safe, your quality system defensible, and your audits clean. Build it right from the start — and maintain it like the regulatory asset it is.

The Standards Navigator covers ISO 13485, ISO 14971, FDA requirements, and medical device quality management in depth. Use the resources above to move from gap to compliant.

Stay Current on Medical Device Compliance

Most teams that struggle with ISO 13485 audits are not missing knowledge — they are missing a system for keeping their risk files, documentation, and compliance processes current as requirements evolve.

Organizations that pass surveillance audits consistently have one thing in common: their quality teams are not surprised by what auditors look for. They have a process for staying ahead of requirement changes, notified body expectations, and post-market obligations.

The Standards Navigator covers ISO 13485, ISO 14971, FDA QMSR, and medical device compliance requirements in plain language for quality professionals and regulatory teams.

👉 Get updates on the medical device compliance cluster — new articles, requirement changes, and implementation guidance delivered directly to your inbox.

👉 Be first to access new free resources, including the ISO 13485 Documentation Starter Kit when it launches.

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

ISO/TR 14969 Explained: What It Was, Why It Was Withdrawn, and What Replaces It in 2026

ISO/TR 14969:2004 — the companion guidance document for ISO 13485:2003 — was officially withdrawn when ISO 13485 was revised to its 2016 edition. Quality professionals still referencing it in QMS procedures are citing an obsolete document. This article explains what ISO/TR 14969 covered, why it was withdrawn, and what replaces it: the ISO 13485:2016 Practical Guide.

The guidance document for ISO 13485 has changed — here’s what medical device quality professionals need to know today

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

The Standard That Guided ISO 13485 Compliance Is Gone — Here’s What That Means

If you searched for ISO/TR 14969, you already ran into a dead end. The document is no longer current. It was officially withdrawn.

That matters more than it sounds. Quality professionals in the medical device space still reference ISO/TR 14969 in internal procedures, training materials, and supplier documentation. Some consultants still cite it. If you are building or auditing a QMS right now, you need to know what replaced it — and whether your documentation is anchored to an obsolete source.

ISO/TR 14969:2004 was withdrawn by ISO when ISO 13485 was revised to its 2016 edition. The technical report was tied to ISO 13485:2003. When the 2016 version introduced risk-based process controls, expanded post-market surveillance requirements, and global regulatory alignment language, the 2004 guidance became misaligned — and in some clauses, actively misleading. In its place, ISO published a new handbook: ISO 13485:2016 — Medical Devices — A Practical Guide.

Now, in 2026, the stakes are higher. The FDA’s Quality Management System Regulation (QMSR) took effect February 2, 2026, formally replacing 21 CFR Part 820 with ISO 13485:2016 as the baseline for U.S. device compliance. Organizations that built their QMS on ISO 13485:2003 interpretations — or whose procedures still reference ISO/TR 14969 — face a two-layer exposure: outdated guidance and regulatory non-alignment.

I’ve seen this pattern play out in quality systems that looked solid on paper. During a QMS documentation review I supported at a contract manufacturer with FDA-regulated device components, the team found five procedures that traced their CAPA language back to 14969 interpretation. The procedures hadn’t been reviewed since 2019. They weren’t wrong, exactly — but they were missing the risk-proportionate framing the 2016 standard requires. No findings yet. That changes when the next surveillance audit runs QMSR expectations against legacy documentation.

Before you go further — if your team is preparing for ISO 13485 certification or a surveillance audit, run a gap check first:

👉 Download the ISO 13485 Gap Assessment Checklist — Free checklist for medical device manufacturers assessing their QMS against ISO 13485:2016 requirements.

In This Guide

What ISO/TR 14969 was and what it covered
Why it was withdrawn
What replaced it — the ISO 13485:2016 Practical Guide, including its structure and chapter mapping
Why 2026 is the year this gap becomes a compliance liability (FDA QMSR)
How to update your QMS documentation to reflect current guidance
Where to purchase the current standard and guidance documents
FAQ

👉 Start Here — Top Resources

ISO 13485:2016 — ANSI Webstore — Purchase the current edition of the standard. Use code CC2026 for 5% off at checkout.
ISO 13485 Training — BSI Group — Implementation, internal auditor, and lead auditor courses aligned to ISO 13485:2016.
ISO 13485 Gap Assessment Checklist — Free download. Identify where your current QMS falls short before your next audit.

What Was ISO/TR 14969?

ISO/TR 14969:2004 was a Technical Report published by ISO’s Technical Committee 210 (ISO/TC 210), the group responsible for quality management and general aspects for medical devices.

TR stands for Technical Report. Unlike a full ISO standard, a Technical Report carries no requirements. It cannot be used as the basis for certification or regulatory inspection. Its purpose was interpretive: help organizations understand what ISO 13485 required and how to meet those requirements in practice.

ISO/TR 14969 provided clause-by-clause guidance on ISO 13485:2003. It explained intent, offered implementation examples, and clarified language that auditors and manufacturers found ambiguous. The document mirrored the clause structure of ISO 13485:2003 and covered:

Scope and application — how requirements applied across different organization types (manufacturers, service providers, distributors)
Quality management system (Clause 4) — documentation requirements, records, and what was required vs. recommended
Management responsibility (Clause 5) — how top management commitment was assessed and evidenced
Resource management (Clause 6) — personnel competency requirements, infrastructure, and work environment controls
Product realization (Clause 7) — planning, design controls, purchasing, production, and process validation
Measurement, analysis, and improvement (Clause 8) — feedback, internal audits, nonconformance control, CAPA, and data analysis

Most common finding: Organizations that built their QMS procedures using ISO/TR 14969 as a reference may have clause citations, interpretive notes, or CAPA language that is now misaligned with ISO 13485:2016. Those gaps become findings during document reviews and surveillance audits.

Why Was ISO/TR 14969 Withdrawn?

Comparison chart showing differences between withdrawn ISO/TR 14969 guidance and ISO 13485:2016 Practical Guide. — Compare legacy ISO/TR 14969 guidance with the current ISO 13485 implementation approach.

ISO/TR 14969:2004 was withdrawn because ISO 13485 itself was substantially revised in 2016. When the 2016 edition introduced new and modified requirements, the 2004 guidance document became misaligned — and in some areas, a liability.

Change Area	ISO 13485:2003 / TR 14969	ISO 13485:2016
Risk-based process control	Limited risk language	Risk-based approach embedded throughout QMS structure
Regulatory requirements	Aligned primarily to EU directives	Expanded global alignment (FDA, TGA, Health Canada, EU MDR)
Post-market surveillance	General requirements	Explicit feedback loop and monitoring requirements
Software validation	Basic guidance	Expanded requirements for QMS software validation
Outsourced processes	Covered in Clause 4.1	Risk-proportionate controls based on risk and external party capability
Supplier controls	Standard purchasing controls	Risk-proportionate controls with clearer documentation requirements

A technical report tied to the 2003 standard could not guide organizations through requirements that didn’t exist until 2016. ISO withdrew the document and directed users to the replacement handbook.

What Replaced ISO/TR 14969? Structure and Clause Mapping

Timeline showing ISO/TR 14969 withdrawal and transition to ISO 13485:2016 Practical Guide and FDA QMSR requirements. — See how ISO/TR 14969 evolved into today’s ISO 13485 guidance framework.

The current guidance document is the ISO 13485:2016 — Medical Devices — A Practical Guide, published by ISO in 2017 and authored by technical experts from ISO/TC 210. In the United States it was adopted by AAMI as AAMI/ISO 13485:2016 — A Practical Guide, available through the ANSI Webstore. AAMI explicitly identifies it as the replacement for ISO/TR 14969.

The handbook runs approximately 214 pages and is organized to mirror the clause structure of ISO 13485:2016, making it a direct lookup reference when you’re working through specific requirements. Here’s how it maps:

Handbook Section	ISO 13485:2016 Clause	Key Guidance Provided
Introduction & Scope	Clause 1	Applicability across organization types; what “regulatory purposes” means in practice
Quality Management System	Clause 4	Risk-based QMS design; documentation hierarchy; outsourced process controls
Management Responsibility	Clause 5	Top management commitment evidence; quality planning; management review inputs/outputs
Resource Management	Clause 6	Competency records; infrastructure qualification; work environment controls
Product Realization	Clause 7	Design controls; purchasing controls; production process validation; sterilization; servicing
Measurement, Analysis & Improvement	Clause 8	Feedback systems; complaint handling; internal audit; CAPA; statistical methods

Beyond clause-level guidance, the Practical Guide also includes:

Regulatory notes specific to different markets — particularly useful for EU MDR and FDA QMSR alignment
Worked examples of how to apply risk-based thinking to QMS process selection and documentation intensity
Transition guidance for organizations moving from ISO 13485:2003-based systems to the 2016 edition

One practical limitation worth knowing: the Practical Guide is a 214-page document that, despite its name, is not always light reading. Industry reviewers have noted that some sections contain circular references and that the guidance on risk-based approach — one of the biggest paradigm shifts in the 2016 standard — spans only a few pages for a topic that has generated ongoing debate between manufacturers and notified bodies. Having the Practical Guide alongside a current training course is more effective than relying on the handbook alone.

👉 If you’re preparing for Stage 1 audit and haven’t run a full clause-by-clause gap check, do that before you open the Practical Guide. Download the ISO 13485 Gap Assessment Checklist to identify gaps first — then use the handbook to close them.

Why This Matters More in 2026: FDA QMSR and Dual Compliance

This isn’t just a document housekeeping issue. In 2026, it’s a compliance liability with a hard regulatory edge.

The FDA QMSR took effect February 2, 2026. It formally replaced 21 CFR Part 820 — the U.S. Quality System Regulation that governed device manufacturing for nearly 30 years — with ISO 13485:2016 as the legal baseline for U.S. medical device quality systems. Manufacturers who previously maintained a 21 CFR Part 820-based QMS now need to be running against ISO 13485:2016 requirements, including the interpretive framework the 2016 standard uses.

That has a direct impact on ISO/TR 14969 references. Here’s why:

ISO/TR 14969 pre-dates both ISO 13485:2016 and FDA QMSR. Any QMS procedure, work instruction, or training record that traces its authority back to 14969 guidance — rather than the 2016 standard and current Practical Guide — is not aligned to the regulatory expectations your FDA inspector will be applying.

Specific areas where this creates dual exposure:

CAPA requirements — 14969 guidance on CAPA pre-dates the 2016 standard’s risk-proportionate framing. FDA inspectors applying QMSR expectations will scrutinize whether your CAPA process scales corrective action depth to risk level. Procedures built on 14969 interpretation often don’t.
Post-market surveillance — The 2016 standard significantly strengthened feedback loop requirements. 14969 guidance reflects the lighter 2003 language. Under QMSR, FDA expects active post-market data feeding back into the QMS — not just complaint logs.
Software validation for QMS applications — If your document control system, CAPA software, or ERP was validated against 14969 guidance language, that validation basis needs review under the 2016 standard’s expanded software validation requirements.

I worked with a team at a supplier to a large device OEM during QMSR transition prep. Their internal audit procedure had been solid for years — well-written, consistently followed. When we mapped it against QMSR expectations, the issue wasn’t procedure quality. It was that the criteria used to determine audit frequency and depth hadn’t been updated since the 2003-era documentation. Risk-based audit scheduling — required under the 2016 standard — wasn’t in the procedure. The OEM’s supplier quality team flagged it in a pre-audit review before the FDA did. That’s the window you want to catch this in.

For a detailed breakdown of the QMSR transition and what changes for manufacturers, see FDA QSR vs ISO 13485.

How to Update Your QMS for Current Guidance

Five-step workflow for updating QMS documentation from ISO/TR 14969 to ISO 13485:2016 guidance. — Use this workflow to systematically remove obsolete guidance from your QMS.

If your QMS procedures, work instructions, or training materials reference ISO/TR 14969, here’s how to address it systematically.

Step 1 — Document search Run a controlled search of your document management system for “ISO/TR 14969,” “TR 14969,” and “14969:2004.” Flag every document where the reference appears. Include training materials and supplier quality agreements.

Step 2 — Classify each reference Not every reference creates a compliance gap. Categorize:

✅ Citation-only reference — the procedure logic is sound; only the document reference needs updating
⚠️ Interpretive reference — procedure was built around 14969 guidance that may not align with current Practical Guide interpretation (CAPA framing, risk-based audit criteria, outsourced process controls)
⚠️ Training material reference — auditors check training records; outdated citations get flagged

Step 3 — Batch the citation updates For straightforward citation updates, consolidate them into a single planned revision cycle. Update the reference from “ISO/TR 14969” to “ISO 13485:2016” or the Practical Guide as appropriate. Document the rationale in your change control record.

Step 4 — Cross-reference interpretive references against the Practical Guide For procedures built on 14969 interpretation, map them against the equivalent clause in the ISO 13485:2016 Practical Guide. Pay specific attention to: CAPA (Clause 8.5), outsourced process controls (Clause 4.1), internal audit (Clause 8.2), and post-market surveillance feedback (Clause 8.2.1). These are the areas where the 2016 guidance diverges most from 2003-era interpretation.

Step 5 — Update internal auditor training records If your ISO 13485 internal auditor training references 14969, update the training materials and re-document competency verification. This is consistently one of the overlooked items in QMS transitions — and it surfaces in audits.

Do the gap assessment before you start revising. Chasing individual references without knowing your overall QMS posture is working in the wrong order. The ISO 13485 Gap Assessment Checklist gives you the full picture first.

✅ Quick Checklist: ISO/TR 14969 Reference Review

[ ] Searched QMS document system for all 14969 references
[ ] Searched training materials and supplier quality agreements
[ ] Classified references as citation-only or interpretive
[ ] Verified CAPA procedure aligns with 2016 risk-proportionate framing — not 14969
[ ] Verified internal audit frequency and depth criteria include risk-based logic
[ ] Verified post-market surveillance feedback procedure reflects 2016 requirements
[ ] Updated training materials to remove obsolete guidance document references
[ ] Confirmed training records reflect ISO 13485:2016 Practical Guide as current source
[ ] Completed a full ISO 13485:2016 gap assessment against all 8 clauses

Where to Buy ISO 13485 and the Current Guidance Handbook

Document	Description	Source
ISO 13485:2016	The current active standard — required for certification	ANSI Webstore
ISO 13485:2016 Practical Guide	214-page official guidance handbook replacing ISO/TR 14969	ANSI Webstore — available individually or in bundles
ISO 13485 / ISO 14971 Bundle	Standard + risk management standard package	ANSI Webstore bundle
ISO/TR 14969:2004	Withdrawn — historical reference only	Available as historical document only

Use coupon code CC2026 for 5% off at the ANSI Webstore — valid through December 31, 2026. ANSI serves international buyers and offers standards in multiple languages where available.

For more on building your ISO 13485 QMS documentation, see ISO 13485 Documentation Requirements and the ISO 13485 Implementation Roadmap.

FAQ

Is ISO/TR 14969 still valid?

No. ISO/TR 14969:2004 was officially withdrawn by ISO when ISO 13485 was revised to its 2016 edition. It is no longer current and should not be used as implementation guidance for an ISO 13485:2016-aligned QMS. It remains available as a historical document only. The replacement is the ISO 13485:2016 — Medical Devices — A Practical Guide.

What replaced ISO/TR 14969?

ISO/TR 14969 was replaced by the ISO 13485:2016 — Medical Devices — A Practical Guide, a 214-page companion handbook published by ISO in 2017 and authored by ISO/TC 210 technical experts. In the United States, it was adopted by AAMI as AAMI/ISO 13485:2016 and is available through the ANSI Webstore. AAMI explicitly identifies it as the replacement for ISO/TR 14969.

Can I still reference ISO/TR 14969 in my QMS procedures?

It is not prohibited, but it creates audit risk — especially now that FDA QMSR is in effect. A reference to a withdrawn guidance document signals that your documentation system may not be current. Best practice is to replace ISO/TR 14969 citations with ISO 13485:2016 clause references or the Practical Guide, and to verify that any procedure logic built on 14969 interpretation still holds against the 2016 standard.

Does ISO/TR 14969 apply to FDA QMSR compliance?

No. ISO/TR 14969 was guidance for ISO 13485:2003. The FDA QMSR — effective February 2, 2026 — harmonizes U.S. requirements with ISO 13485:2016. QMSR compliance requires alignment with the 2016 standard and its current guidance documents. Organizations still referencing 14969 in CAPA, audit, or post-market surveillance procedures should treat QMSR implementation as the trigger to complete that cleanup.

What is the difference between a Technical Report and an ISO standard?

An ISO Technical Report carries no requirements and cannot serve as the basis for certification or regulatory inspection. ISO/TR 14969 was a TR — it existed to help organizations interpret and implement ISO 13485, not to define binding requirements. The ISO 13485:2016 Practical Guide serves the same interpretive purpose.

How is ISO/TR 14969 different from ISO 13485?

ISO 13485 is the requirements standard — it defines what a QMS must do to be certifiable. ISO/TR 14969 was guidance only — it explained how to interpret and meet those requirements. The standard is mandatory for certification; the guidance document was optional but widely used. ISO 13485:2016 is the current active standard.

Do I need to buy the ISO 13485:2016 Practical Guide separately from the standard?

Yes. The standard and the Practical Guide are separate publications. The standard defines the requirements; the Practical Guide explains clause intent and provides implementation examples. Bundle packages combining ISO 13485:2016, the Practical Guide, and ISO 14971 are available at the ANSI Webstore at savings compared to individual purchases. For manufacturers building or overhauling a QMS, having both is strongly recommended.

Where can I get ISO 13485 training that covers the current guidance?

BSI Group offers ISO 13485 training at awareness, requirements, implementation, internal auditor, and lead auditor levels — all aligned to the 2016 edition. BSI is both an accredited training provider and a recognized certification body. Pairing their implementation or internal auditor course with the Practical Guide gives you a working command of the 2016 requirements, not just familiarity with the document.

📥 Free Resources

ISO 13485 Gap Assessment Checklist — Free checklist for medical device manufacturers assessing their QMS against ISO 13485:2016 requirements before certification or a surveillance audit
ISO 9001 Roadmap — Step-by-step implementation guide for manufacturers building or improving a quality management system
Manufacturing Compliance Checklist — Practical compliance reference covering key ISO, OSHA, and quality requirements for production environments
Supplier Quality Checklist — Evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts
AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification

Not Sure What to Do Next?

🔹 Still researching ISO 13485 requirements? Start with What Is ISO 13485? for a full breakdown of the standard’s scope, structure, and who needs it.

🔹 Building or upgrading your ISO 13485 QMS? The ISO 13485 Implementation Roadmap walks you through the sequence from gap assessment to certification-ready documentation. For training on the 2016 requirements, BSI Group’s ISO 13485 courses include implementation-level coverage that goes well beyond the handbook itself.

🔹 Ready to purchase the standard? Get ISO 13485:2016 at the ANSI Webstore in digital or print. Use code CC2026 for 5% off through December 31, 2026.

The Standards Navigator covers the full medical device compliance standards landscape — from ISO 13485 implementation to FDA QMSR alignment. If your QMS has to hold up against both ISO certification and FDA inspection, the guidance document you’re working from matters as much as the standard itself.

Stay Current on ISO 13485 and Medical Device Compliance

QMS procedures built on outdated guidance don’t fail audits immediately. They fail them on the third surveillance cycle, when nobody remembers where the language came from. The FDA QMSR has made that timeline shorter.

The Standards Navigator covers ISO 13485 implementation, QMSR transition, risk management requirements, and the documentation controls that keep QMS systems audit-ready across both regulatory frameworks.

👉 Get updates on the medical device compliance standards cluster 👉 Be first to access new ISO 13485 implementation resources and checklists

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

Medical Device Compliance Standards: What Manufacturers Need to Know in 2026

Medical device manufacturers face a layered compliance framework — ISO 13485, ISO 14971, FDA QMSR, and EU MDR each impose specific requirements that must work together as an integrated system. This guide explains the core standards, how they interact, and what manufacturers need to prioritize at each stage of the compliance process.

The regulatory framework every medical device manufacturer must understand before the first audit

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

The Compliance Gap That Gets Medical Device Manufacturers in Trouble

Most medical device manufacturers don’t fail audits because they ignored the requirements. They fail because they didn’t understand how the requirements connect — and which standards they were actually obligated to meet.

The medical device compliance standards landscape is layered. ISO 13485 sets the QMS framework. ISO 14971 governs risk management. FDA regulations run parallel to international standards and don’t always align. Supplier controls, sterilization validation, design controls, and labeling each carry their own standard reference. A manufacturer who treats these as independent checkboxes instead of an integrated system is building toward an audit finding — or worse, a product recall.

The stakes are not abstract. The FDA issued 483 observations totaling thousands of findings in the medical device sector last year. Most cited documentation gaps, inadequate CAPA processes, or failure to meet design control requirements — all areas governed by the standards covered in this guide.

I’ve worked in quality systems that span heavy industrial, energy, and manufacturing environments — and the pattern I’ve seen across every sector is the same: organizations that struggle with audits are usually managing compliance requirements in silos. In the medical device world, that problem is amplified because the regulatory framework is both more complex and less forgiving than most industrial standards. Getting the structure right before your first audit is not optional — it’s the difference between certification and a warning letter.

Before you map your compliance requirements, download the ISO 13485 Gap Assessment Checklist — it walks you through every clause so you can identify exactly where your QMS falls short before an auditor does → ISO 13485 Gap Assessment Checklist

In This Guide:

The core standards every medical device manufacturer must know
How ISO 13485, ISO 14971, and FDA regulations interact
US vs. EU regulatory requirements compared
Supplier control and special process standards
Decision-stage guidance: what to prioritize based on where you are in the compliance process

👉 Start Here — Top Resources

Buy ISO 13485:2016 — ANSI Webstore — the official QMS standard for medical device manufacturers (use code CC2026 for 5% off)
ISO 13485 Training — BSI Group — training courses and certification services for ISO 13485
Buy ISO 14971:2019 — ANSI Webstore — risk management standard required alongside ISO 13485

The Core Standard: ISO 13485:2016

ISO 13485:2016 infographic showing clause structure and comparison of ISO 13485 versus ISO 9001 requirements for medical device quality management systems. — A visual breakdown of ISO 13485:2016 requirements and how they differ from ISO 9001 for medical device manufacturers.

ISO 13485:2016 is the international standard for quality management systems specific to medical device manufacturers and their supply chains. It is the foundation of medical device compliance worldwide.

ISO 13485 is not simply ISO 9001 with medical device language added. The two standards share structural similarities through the harmonized high-level clause structure, but ISO 13485 imposes stricter requirements in several critical areas ISO 9001 leaves to organizational discretion:

Requirement Area	ISO 9001:2015	ISO 13485:2016
Risk management	Risk-based thinking (general)	Formal risk management required (links to ISO 14971)
Design controls	Required	More prescriptive — validation, verification, design transfer
CAPA	Required	More detailed — specific investigation and effectiveness checks
Regulatory requirements	Not addressed	Explicitly required — must identify and meet applicable regs
Sterile product controls	Not addressed	Specific controls for sterile devices
Supplier controls	Required	More stringent — supplier qualification and monitoring
Document and record retention	Not specified	Specific retention periods tied to device lifetime

If you are ISO 9001 certified and entering the medical device market, you are not starting from scratch — but you are adding significant requirements. The gap is larger than most manufacturers expect.

If you need the standard itself, ISO 13485:2016 is available through the ANSI Webstore — use code CC2026 for 5% off through December 31, 2026.

Most common finding: Inadequate document control — specifically, failure to control the review and approval of documents and maintain records of changes. ISO 13485 Clause 4.2 is one of the most frequently cited areas in FDA 483 observations.

Risk Management: ISO 14971:2019

ISO 14971 is the international standard for risk management applied to medical devices. It is not optional if you are manufacturing medical devices — ISO 13485 explicitly requires you to apply risk management throughout the product lifecycle, and ISO 14971 is the recognized method for doing it.

ISO 14971:2019 defines the process for:

Identifying hazards associated with a medical device
Estimating and evaluating associated risks
Controlling those risks
Monitoring the effectiveness of controls

The relationship between ISO 13485 and ISO 14971 is not optional. ISO 13485 Clause 7.1 requires organizations to establish risk management requirements for product realization. ISO 14971 is the standard that defines what “proper” risk management looks like. Auditors will look for evidence that your risk management file connects directly to your design controls, production processes, and post-market surveillance activities.

ISO 14971 vs. ISO 13485 — understanding how they interact is one of the most common questions from manufacturers building a QMS for the first time.

If your risk management files exist independently of your design control documentation — that is an audit finding waiting to happen. Most teams miss the linkage between hazard identification in the risk management file and the verification/validation activities in the design history file.

Run your gap assessment before you go further — most QMS gaps in medical device companies trace back to missing connections between ISO 14971 risk files and ISO 13485 design controls: ISO 13485 Gap Assessment Checklist

US Regulatory Requirements: FDA QMSR and 21 CFR Part 820

US medical device manufacturers operate under FDA jurisdiction. The Quality Management System Regulation (QMSR), which took effect February 2, 2026, replaced the legacy Quality System Regulation (QSR) under 21 CFR Part 820.

The QMSR represents a significant shift: it incorporates ISO 13485:2016 by reference as the baseline for device QMS requirements. This means FDA-regulated manufacturers who are ISO 13485 certified are closer to QMSR compliance than they were under the old QSR — but important differences remain.

Area	ISO 13485:2016	FDA QMSR (2026)
Scope	International	US market devices only
Complaints	Required	Required + specific MDR reporting timelines
Corrections and removals	Addressed in CAPA	Specific FDA reporting requirements (21 CFR Part 806)
UDI	Not addressed	Required for most device classes
Electronic records	Not specified	21 CFR Part 11 compliance required
Third-party audits	Required for ISO 13485 certification	FDA inspections — not third-party certification

Understanding the relationship between FDA QSR and ISO 13485 is essential for US manufacturers — the two frameworks are now more aligned than before, but they are not identical.

If you are selling devices in the US market, FDA QMSR compliance is a legal requirement, not a voluntary certification. ISO 13485 certification does not satisfy FDA obligations — it demonstrates QMS capability but does not substitute for an FDA inspection.

Comparison infographic showing US FDA QMSR and EU MDR regulatory pathways for medical device manufacturers and ISO 13485 quality system requirements. — A side-by-side comparison of US FDA QMSR and EU MDR pathways showing how medical device compliance differs across global markets.

EU Requirements: MDR and CE Marking

Selling medical devices in the European Union requires CE marking under the EU Medical Device Regulation (MDR 2017/745), which replaced the Medical Device Directive (MDD) and came into full effect in 2021. The transition deadline for legacy MDD-certified devices has been extended but enforcement has tightened significantly.

Key MDR requirements relevant to QMS:

MDR Requirement	Connection to ISO 13485
Technical documentation	Design history file / DHF requirements
Clinical evaluation	Post-market clinical follow-up (PMCF)
Unique Device Identification (UDI)	Traceability requirements
Post-market surveillance (PMS)	Customer feedback and complaint monitoring
Notified Body audit	ISO 13485 certification is typically required
Person Responsible for Regulatory Compliance (PRRC)	Management responsibility — ISO 13485 Clause 5

The MDR is more prescriptive than ISO 13485 in clinical evidence requirements. If you are exporting to the EU, your clinical evaluation report and post-market surveillance plan must meet MDR requirements that go beyond what ISO 13485 explicitly requires.

If you are selling in both the US and EU markets, you are managing two regulatory frameworks simultaneously. This is where a well-structured ISO 13485 QMS becomes particularly valuable — it provides the common foundation that both frameworks build on.

Supplier Controls and Special Process Standards

ISO 13485 Clause 7.4 imposes stricter supplier control requirements than most manufacturers new to the medical device space expect. You are not simply verifying that a supplier has a quality system — you are responsible for ensuring that purchased products and services meet specified requirements and that critical suppliers are evaluated, approved, and monitored.

For medical device manufacturers, supplier controls must address:

Supplier qualification — documented criteria for evaluation and approval
Incoming inspection — defined acceptance criteria for purchased product
Critical supplier monitoring — ongoing performance data, not just initial qualification
Supplier audits — for high-risk or critical component suppliers
Flow-down requirements — pushing your quality requirements into the supply chain

Special processes — sterilization, biocompatibility testing, coating, welding on implantable components — require additional validation documentation. The relevant standards include:

Process	Standard Reference
Sterilization (EO, radiation, steam)	ISO 11135, ISO 11137, ISO 17665
Biocompatibility	ISO 10993 series
Packaging validation	ASTM F2132, ISO 11607
Software validation	IEC 62304
Electrical safety	IEC 60601 series

These are not optional for manufacturers of the relevant device types. If your device is sterilized, you need sterilization validation documentation. If it contacts patient tissue, you need biocompatibility data. Gaps in special process validation are among the most serious findings an FDA inspector or Notified Body auditor can cite.

Design Controls and Validation Standards

ISO 13485 design controls infographic showing the Design History File process from inputs through outputs, verification, validation, and design transfer. — A visual guide to the ISO 13485 design controls process and how design inputs become validated, production-ready medical devices.

Design controls are where ISO 13485 certification and FDA compliance intersect most directly. ISO 13485 Clause 7.3 requires a structured design and development process covering:

Design and development planning
Design inputs (requirements)
Design outputs (specifications)
Design review at defined stages
Design verification (does it meet inputs?)
Design validation (does it meet user needs?)
Design transfer (can it be manufactured consistently?)
Design changes (controlled and documented)

The design history file (DHF) is the physical record of this entire process. It is the first thing an FDA inspector or Notified Body auditor will request. Manufacturers who build their DHF as a collection of unconnected documents — rather than as a traceable record linking inputs to outputs to verification to validation — create significant risk for themselves.

If you are new to building a medical device QMS and need a structured path through these requirements, the ISO 13485 Implementation Roadmap on The Standards Navigator covers the full sequence from gap assessment through certification.

BSI Group offers ISO 13485 training covering both requirements understanding and implementation — useful for teams building their first medical device QMS or transitioning from a general ISO 9001 system.

Labeling and Traceability Standards

Labeling compliance is a specific, frequently cited area in FDA 483 observations. Under both FDA QMSR and MDR requirements, device labeling must meet defined content and format requirements — and the label must be controlled as a quality record.

Key labeling standards and requirements:

ISO 15223-1 — symbols used in medical device labeling (required for EU MDR compliance)
21 CFR Part 801 — FDA labeling requirements for US devices
UDI requirements — FDA requires Unique Device Identification on most device labels, with submission to the GUDID database

Traceability connects directly to your CAPA and complaint handling processes. If a complaint involves a specific lot or device unit, your traceability records must be sufficient to identify affected products, investigate the root cause, and determine corrective action scope. ISO 13485 Clause 7.5.9 addresses traceability explicitly — and auditors will test it.

How the Standards Work Together

Layered medical device compliance standards infographic showing ISO 13485 as the foundation with ISO 14971, FDA QMSR, EU MDR, supplier controls, CAPA, and traceability requirements. — A visual framework showing how ISO 13485, FDA QMSR, EU MDR, and supporting standards connect into an integrated medical device compliance system.

The most important thing to understand about medical device compliance is that these standards are not independent — they form an integrated system. Here is how they connect:

Standard	Role in the System
ISO 13485:2016	QMS framework — the backbone that everything else connects to
ISO 14971:2019	Risk management process — required by ISO 13485, referenced throughout
FDA QMSR	US regulatory layer — builds on ISO 13485, adds FDA-specific requirements
EU MDR	EU regulatory layer — requires ISO 13485 certification via Notified Body
IEC 62304	Software lifecycle — required if your device includes software
ISO 10993	Biocompatibility — required for patient-contacting devices
ISO 15223	Labeling symbols — required for EU MDR labeling compliance

A manufacturer who has ISO 13485 certification, a complete ISO 14971 risk management file, and solid FDA QMSR documentation has built the framework that all additional standards layer onto. The common mistake is treating each standard as a separate compliance project rather than building the integrated system first.

If you are deciding between prioritizing FDA QMSR or ISO 13485 certification first: in most cases, building to ISO 13485 gives you the QMS foundation that both US and EU regulatory compliance require. The ISO 13485 Documentation Requirements article covers what your QMS documentation set must include.

Quick Compliance Checklist

Use this as a starting reference — not a substitute for a clause-by-clause gap assessment.

✅ ISO 13485:2016 obtained and QMS scope defined
✅ Risk management procedure in place referencing ISO 14971
✅ Design controls documented — inputs, outputs, verification, validation, transfer
✅ CAPA process established with effectiveness verification
✅ Supplier qualification and monitoring program documented
✅ Document and record control procedures in place with defined retention periods
✅ Internal audit program scheduled and resourced
✅ Management review process defined and conducted
✅ Complaint handling and MDR/vigilance reporting process established
✅ UDI requirements evaluated and implemented where applicable
✅ Applicable special process validations identified and documented
✅ Labeling reviewed against ISO 15223 (EU) and 21 CFR Part 801 (US)

⚠️ If you cannot check most of these — complete a formal gap assessment before committing to a certification timeline.

FAQ

Is ISO 13485 certification required to sell medical devices?

ISO 13485 certification is not legally required by US law — the FDA requires QMSR compliance, not ISO 13485 certification specifically. However, ISO 13485 certification is required to sell devices in the EU under MDR, and it is increasingly required by OEM customers and contract manufacturers as a condition of doing business. Most manufacturers targeting both markets pursue certification.

How is ISO 13485 different from ISO 9001?

ISO 13485 is a sector-specific standard derived from ISO 9001 but with significantly stricter requirements in risk management, design controls, CAPA, supplier controls, and regulatory compliance. It does not include the continual improvement emphasis that ISO 9001 requires — instead it focuses on consistent compliance with regulatory requirements. A detailed comparison is covered here.

Do I need ISO 14971 if I am ISO 13485 certified?

Yes. ISO 13485 explicitly requires risk management throughout the product lifecycle and references ISO 14971 as the applicable method. You are not ISO 13485 compliant if your risk management process does not meet ISO 14971 requirements. The two standards work together — you cannot separate them.

What is the FDA QMSR and how is it different from the old QSR?

The Quality Management System Regulation (QMSR) took effect February 2, 2026 and replaced 21 CFR Part 820 (the Quality System Regulation). The QMSR incorporates ISO 13485:2016 by reference, making it more aligned with the international standard. Key differences remain around FDA-specific reporting requirements, UDI obligations, and 21 CFR Part 11 electronic records requirements. A full breakdown of FDA QSR vs ISO 13485 is here.

How long does it take to get ISO 13485 certified?

For a manufacturer building a QMS from scratch, 12–18 months is a realistic timeline. Organizations with an existing ISO 9001 QMS can often close the gap in 6–12 months, depending on how many medical device-specific requirements need to be added. The ISO 13485 Implementation Roadmap covers the full timeline in detail.

What is a Notified Body and do I need one?

A Notified Body is an organization designated by EU member states to assess conformity of medical devices under the MDR. If you are seeking CE marking for Class IIa, IIb, or Class III devices, you must engage a Notified Body — they conduct the audits that verify ISO 13485 compliance and technical documentation. BSI Group is one of the major Notified Bodies offering both training and certification services.

What are the most common ISO 13485 audit findings?

The most frequently cited areas include: inadequate document and record control (Clause 4.2), incomplete CAPA processes with missing effectiveness verification (Clause 8.5.2), insufficient supplier qualification documentation (Clause 7.4), and gaps in design control records — particularly missing design verification and validation evidence (Clause 7.3). Common mistakes in ISO 13485 QMS implementation covers these in detail.

Do my suppliers need to be ISO 13485 certified?

Not necessarily — but you are responsible for ensuring purchased product meets specifications regardless. Whether a supplier needs ISO 13485 certification depends on their criticality and what they supply. Critical component suppliers and contract manufacturers of finished devices are typically expected to be certified. Commodity suppliers may only require documented incoming inspection.

📥 Free Resources

ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements — medical device articles only

ISO 9001 Roadmap — step-by-step implementation guide for manufacturers building or improving a quality management system

Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments

Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts

AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification

Not Sure What to Do Next?

🔹 Still researching your compliance requirements? Start with a gap assessment against ISO 13485 before you invest in implementation. Download the free ISO 13485 Gap Assessment Checklist — it maps every clause so you know exactly where you stand.

🔹 Ready to build your QMS? ISO 13485 training through BSI Group covers requirements, implementation, and internal auditor training — the right sequence for a team building their first medical device QMS.

🔹 Need the standard itself? Buy ISO 13485:2016 through the ANSI Webstore — use code CC2026 for 5% off through December 31, 2026. International buyers can purchase in multiple languages.

Medical device compliance is not a single standard — it is a framework of interconnected requirements that must be built and maintained as a system. Understanding how ISO 13485, ISO 14971, FDA QMSR, and EU MDR relate to each other is the first step toward building a QMS that holds up under audit. The Standards Navigator covers each of these standards in depth — start with the resources above and build from there.

Stay Current on Medical Device Compliance

Regulatory changes in the medical device space don’t slow down. FDA QMSR took effect in 2026. EU MDR enforcement is intensifying. ISO 14971 continues to be misapplied by manufacturers who treat risk management as a documentation exercise rather than an integrated process.

Organizations that keep pace with these changes have one thing in common — they’re not waiting for an audit finding to tell them something changed. The ones that struggle are managing compliance reactively, updating their QMS only when a customer or inspector forces the issue.

The Standards Navigator covers ISO 13485, ISO 14971, FDA regulatory requirements, and the full medical device compliance framework — from standard purchase through certification and ongoing surveillance.

👉 Get updates when new medical device compliance articles publish
👉 Be first to access the ISO 13485 Documentation Kit when it launches

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

ISO 13485 Implementation Roadmap: How to Build a Compliant Medical Device QMS in 2026

ISO 13485:2016 is now US federal law under the FDA QMSR, making a compliant medical device QMS mandatory rather than optional. This roadmap walks manufacturers through a seven-phase implementation — from gap assessment and scope through risk management, documentation, CAPA, and certification — covering both the international certification path and FDA inspection readiness for US manufacturers building from the ground up.

A step-by-step guide to implementing ISO 13485:2016 — from gap assessment to certification and FDA QMSR readiness

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

Building a Medical Device QMS Is No Longer Optional in the United States

For years, ISO 13485 sat in a strange position for US manufacturers. It was the global benchmark for medical device quality management — required to sell in the EU, Canada, and most of the world — but inside the United States it was voluntary. You complied with FDA’s Quality System Regulation, and ISO 13485 was a nice-to-have for export.

That changed on February 2, 2026. FDA’s Quality Management System Regulation (QMSR) took effect, replacing the old Quality System Regulation and incorporating ISO 13485:2016 by reference directly into 21 CFR Part 820. The practical effect is blunt: ISO 13485:2016 is now part of US federal law. FDA inspections are conducted against it. The standard you could once ignore at home is now the framework your inspector arrives with.

So whether you are a US manufacturer preparing for your first QMSR-aligned FDA inspection, or an international supplier chasing your first ISO 13485 certificate to unlock the EU market, you face the same task: build a quality management system that survives outside scrutiny. This roadmap walks you through it — clause by clause, phase by phase — from the day you decide to start to the day a registrar or an FDA investigator walks through the door.

This ISO 13485 implementation roadmap is a long article because building a medical device QMS is a long project. Use the table of contents to jump to where you are.

Before you build anything, find out where you actually stand. Most teams overestimate how compliant their existing processes are — and discover the gaps during the certification audit or FDA inspection, when fixing them is expensive and the clock is running. Run a clause-by-clause check against ISO 13485:2016 first.

👉 Download the free ISO 13485 Gap Assessment Checklist and benchmark your QMS in an afternoon, before you commit budget to implementation.

In This Guide

Why ISO 13485 implementation looks different in 2026 (QMSR, EU reforms)
The realistic timeline and cost of a full implementation
A seven-phase roadmap from gap assessment to certificate
How risk management (ISO 14971) and design controls fit into the QMS
The documentation you actually need — and where teams over-build
Internal audit, management review, and Stage 1 / Stage 2 audit preparation
FDA QMSR inspection readiness for US manufacturers
The mistakes that fail audits — and how to avoid them

👉 Start Here (Top Resources)

If you are implementing ISO 13485 from scratch, these are the three resources that move the project fastest:

Build your documentation without a consultant. A complete, pre-written ISO 13485 documentation kit gives you the quality manual, procedures, and records templates structured to the standard — so you spend your time tailoring, not drafting from a blank page. 👉 See the ISO 13485 documentation kits at 9001Simplified
Get the official standard. You cannot implement a clause you have not read. Buy ISO 13485:2016 from the ANSI Webstore — use code CC2026 for 5% off through December 31, 2026. ANSI serves international buyers and offers standards in multiple languages.
Train your internal team. Your management representative and internal auditors need formal training. BSI Group offers ISO 13485 training courses spanning awareness through lead auditor.

What Makes 2026 Different

ISO 13485:2016 is still the current edition — and it will be for a while. ISO postponed the next revision deliberately to let the 2016 edition “bed in,” with a new version not expected before roughly 2028–2029. So the standard you implement today is the standard you will operate under for years. That stability is good news: it means your implementation work has a long shelf life.

What has shifted is the regulatory context around the standard.

In the United States, the QMSR is the headline. FDA now incorporates ISO 13485:2016 into 21 CFR Part 820, layered with a handful of FDA-specific additions — labeling, UDI, and certain record and definition provisions — that go beyond the ISO text. A critical nuance: the QMSR is “version locked” to the 2016 edition. Future ISO 13485 revisions will not automatically apply in the US unless FDA initiates new rulemaking. Certification to ISO 13485 is still not legally required in the US — FDA inspects you directly — but building your QMS to the standard is now the most direct path to QMSR compliance.

In the European Union, the pressure point is notified body capacity, not the standard itself. EU Implementing Regulation 2026/977, published in May 2026 and applying from February 25, 2027, finally imposes hard maximum timelines on notified bodies — 30 days to review an application and sign a contract, 120 days for the QMS audit, 90 days for product verification, and 20 days to issue the certificate, with capped clock-stops and transparent quotations. For manufacturers, the message is that the certification path is becoming more predictable, but you still need a clean, audit-ready QMS to take advantage of it.

One more 2026 wrinkle worth flagging if your devices touch biocompatibility: FDA’s recognition of the sixth edition of ISO 10993-1 is partial. Notably, FDA does not recognize Clause 6.9 on biological risk estimation, holding that it conflicts with the recognized risk management standard ISO 14971:2019. If your risk files cite ISO 10993-1 wholesale, that is now a deficiency-letter risk in US submissions. Keep biological risk inside the ISO 14971 framework. We cover biocompatibility in depth separately — for this roadmap, just know that your risk management process is the anchor, not the 10993 series.

If you sell only in the US → build to ISO 13485:2016 for QMSR compliance and skip certification unless a customer demands it. If you sell internationally → you need an actual ISO 13485 certificate from an accredited registrar, so plan for a Stage 1 / Stage 2 audit. If you sell in both markets → build one QMS to ISO 13485:2016 and bolt on the FDA-specific QMSR additions; do not run two parallel systems.

QMSR vs ISO 13485 at a Glance

The two frameworks now share a core, but they are not identical. This is where US and international readers diverge — and where a single well-built QMS can serve both.

Dimension	ISO 13485:2016	FDA QMSR (21 CFR Part 820)
Legal status	Voluntary international standard	Mandatory US federal regulation
Core requirements	The full ISO 13485 QMS	Incorporates ISO 13485:2016 by reference
Proof of compliance	Certificate from accredited registrar	FDA inspection — no certificate issued
Added requirements	None beyond the standard	Labeling, UDI, certain records & definitions
Risk management	References ISO 14971	Requires ISO 14971 framework; rejects ISO 10993-1 Clause 6.9
Version handling	ISO may revise (~2028–2029)	“Version locked” to the 2016 edition
Who needs it	Anyone selling internationally	Any device manufacturer marketing in the US

For the full treatment, see our dedicated FDA QSR vs ISO 13485 comparison.

Timeline and Cost: What to Expect

A realistic ISO 13485 implementation runs 6 to 12 months for a small-to-mid-size manufacturer building from a limited starting point. Companies already operating a mature ISO 9001 system or a legacy QSR-based system can move faster; companies starting from informal processes should plan for the full year.

ISO 13485 implementation timeline infographic showing a phased 6 to 12 month roadmap for medical device manufacturers progressing from gap assessment through certification. — A visual roadmap showing a realistic ISO 13485 implementation timeline from assessment through certification readiness.

Phase	Typical duration	What drives it
Gap assessment & scope	2–4 weeks	Size of the gap between current practice and the standard
Process & documentation build	8–16 weeks	Whether you draft from scratch or start from templates
Implementation & operation	8–12 weeks	You need real records, not just documents — audits want evidence
Internal audit & management review	3–4 weeks	Must be complete before a registrar will proceed to Stage 2
Certification (Stage 1 + Stage 2)	6–10 weeks	Registrar scheduling and any nonconformity closure

On cost, the single biggest variable is whether you hire a consultant to draft your system or build it yourself from a structured template. Consultant-led implementations commonly run $15,000–$50,000+ depending on device class and company size. A template-driven build can cut the documentation labor dramatically. For a full breakdown, see our guide on how much ISO 13485 certification costs.

Phase 1 — Foundation: Scope, Standard, and Leadership Commitment

Everything downstream depends on getting three things right at the start.

Define your QMS scope. ISO 13485 lets you exclude certain requirements — for example, design and development (Clause 7.3) if you are a contract manufacturer building to a customer’s design. But exclusions must be justified and documented, and you cannot exclude something just because it is inconvenient. Map which clauses apply to your role: manufacturer, specification developer, contract manufacturer, sterilization provider, or importer. Your scope statement is the first thing a registrar reads and the boundary an FDA investigator works within.

Acquire and read the standard. This sounds obvious and gets skipped constantly. You cannot delegate compliance with a document nobody on the team has read end to end. Buy the official ISO 13485:2016 text from the ANSI Webstore — apply coupon CC2026 for 5% off through the end of 2026 — and have your management representative work through it clause by clause. If you also need the risk management standard, ISO 14971:2019 is available there too. ANSI’s catalog covers international buyers and multiple languages, which matters if your QMS spans sites.

Secure genuine leadership commitment. Clause 5 puts top management on the hook — quality policy, quality objectives, resource allocation, and management review are not delegable to a quality manager working in isolation. The fastest implementations have an executive sponsor who clears roadblocks. The ones that stall have a quality team trying to impose a system the leadership treats as paperwork.

If you are a contract manufacturer → document your design and development exclusion now, with justification, before you build the rest of the system around it.

⚠️ Common pitfall: Claiming a Clause 7.3 exclusion you can’t defend. If your team does any design input — even tweaking a customer’s spec for manufacturability — a registrar may reject the exclusion and you’ll be retrofitting design controls mid-project. Decide your true scope honestly before you build.

Most ISO 13485 projects don’t fail on the standard — they fail on documentation that nobody can find, follow, or defend in an audit. Before you write a single procedure, make sure you know which records the standard actually requires.

👉 Run the gap assessment and map your existing documents against the clauses — it turns “we think we’re covered” into a defensible list.

Phase 2 — Plan: Processes, Roles, and Competence

ISO 13485 is a process-based standard. Before documentation, map your actual processes and how they connect — the “sequence and interaction” the standard requires.

Identify your core processes. At minimum: management processes (planning, review, resourcing), product realization (design, purchasing, production, servicing), and support processes (document control, records, CAPA, internal audit). For each, define inputs, outputs, owners, and the records that prove it ran.

Appoint a management representative. Clause 5.5.2 requires a member of management responsible for the QMS. This person owns the system, reports its performance to leadership, and is typically the registrar’s main point of contact.

Plan competence and training. Clause 6.2 requires that personnel performing work affecting product quality are competent — with records to prove it. This includes your internal auditors, who must be trained and independent of the areas they audit. Formal training shortens the learning curve here; BSI Group’s ISO 13485 course catalog runs from awareness through lead auditor, and the lead-auditor tier is what equips your internal audit program to find problems before the registrar does. For audit methodology itself, note that the underlying guidance standard, ISO 19011, was updated to a 2026 edition in May 2026 — worth referencing when you write your internal audit procedure.

⚠️ Common pitfall: Treating internal auditor “independence” as a formality. Having someone audit their own department is one of the most common nonconformities — and it quietly undermines every finding that audit produces. Cross-train auditors so no one reviews work they own.

Phase 3 — Risk Management and Design Controls

This is where ISO 13485 separates itself from ISO 9001, and where the most consequential implementation decisions live.

Risk management is the spine. ISO 13485 threads risk-based thinking through the entire product lifecycle, and it leans on ISO 14971:2019 as the method. You need a risk management process, a risk management file for each device or device family, and evidence that risk controls are verified and monitored in production and post-market. As noted earlier, keep biological risk inside this ISO 14971 framework rather than importing a separate scoring approach — that alignment is exactly what FDA expects under the QMSR.

Design controls (Clause 7.3) apply if you develop devices. This is the discipline FDA investigators scrutinize hardest, because design failures are where patients get hurt. You need:

Design control element	What it requires
Design and development planning	A documented plan with stages, reviews, and responsibilities
Design inputs	Requirements derived from intended use, user needs, and regulation
Design outputs	Specifications that can be verified against inputs
Design review	Formal reviews at planned stages with independent reviewers
Design verification	Evidence outputs meet inputs
Design validation	Evidence the device meets user needs in actual or simulated use
Design transfer	Controlled handoff to production
Design changes	Controlled, reviewed, and documented changes
Design history file (DHF)	The complete record of the above

If you are a US manufacturer, the QMSR keeps design controls firmly in play — they map directly onto the ISO 13485 Clause 7.3 requirements, which is one reason a single ISO-aligned system now serves both purposes.

If you are preparing your first device submission → build the risk management file and design history file in parallel with the QMS, not after. Auditors and investigators expect to see them populated, not planned.

⚠️ Common pitfall: Building the risk file as a one-time document for the submission, then never touching it again. Risk management is a living, lifecycle requirement — production and post-market data have to feed back into it. A risk file frozen at launch is a finding waiting to happen.

Phase 4 — Build the Documentation

Now you write the system. ISO 13485 expects a defined documentation hierarchy: a quality manual, documented procedures, work instructions, forms, and the records they generate.

ISO 13485 documentation architecture infographic showing the five-layer quality management documentation hierarchy from quality manual through records. — A visual breakdown of the five documentation layers used to build and maintain an ISO 13485 quality management system.

The required documents. ISO 13485:2016 explicitly requires certain documented procedures — document control, record control, management review, internal audit, control of nonconforming product, CAPA, and several product-realization procedures among them. A medical device file (technical documentation) is required for each device type. Our breakdown of ISO 13485 documentation requirements lists exactly what the standard mandates versus what is optional.

Where teams over-build. The most common documentation mistake is writing procedures more detailed and rigid than the operation can actually follow. Every sentence in a procedure is a commitment an auditor can hold you to. If your procedure says calibration happens every 90 days and a record shows 95, that is a nonconformity you created with your own words. Write to what you do; improve what you do separately.

Start from a structured template, not a blank page. Drafting an entire ISO 13485 documentation set from scratch is where 6-month projects become 12-month projects. A complete documentation kit gives you the quality manual, every required procedure, and the records templates already structured to the clauses — so your team spends its hours tailoring language to your operation instead of reinventing the architecture of a QMS.

👉 See what’s included in the 9001Simplified ISO 13485 documentation kit — it is the no-consultant route most small manufacturers should evaluate first.

Set up document and record control before you generate volume. Clauses 4.2.4 and 4.2.5 require controlled documents and controlled records. Get the control mechanism — versioning, approval, retention, retrieval — working before you have hundreds of documents to retrofit.

⚠️ Common pitfall: Over-documenting. Teams write procedures so detailed and rigid that the floor can’t actually follow them — then every deviation from their own paperwork becomes a nonconformity. Document what you genuinely do, keep procedures lean, and push the specifics down into work instructions where they’re easier to change.

Phase 5 — Implement and Operate

A documented QMS proves nothing. Auditors and investigators want records that show the system ran.

This is the phase teams underestimate. You can write a CAPA procedure in a day; demonstrating that CAPA actually works requires real CAPAs opened, investigated, and closed over weeks. Plan for an operating period — typically 8 to 12 weeks minimum — where the system runs and generates genuine evidence: training records, calibration records, completed reviews, supplier evaluations, nonconformance reports, and CAPA records.

A registrar will not progress to a certification audit, and an FDA investigator will not be satisfied, by documents alone. Both want to trace a process from requirement to record to outcome. Build that evidence trail before you invite anyone to inspect it.

If you are under customer pressure to certify quickly → start operating the system in parallel with finishing documentation, so your evidence trail is already accumulating when the documents are signed off.

⚠️ Common pitfall: Booking the certification audit before the system has actually run. A registrar can tell the difference between a QMS that has operated for three months and one that generated all its records last week. Backdated or thin evidence is the fastest way to turn a Stage 2 audit into a list of nonconformities.

Phase 6 — CAPA, Supplier Controls, and Production Controls

Three areas generate the most audit findings and FDA 483 observations. Get them right and you de-risk the entire certification.

CAPA (Corrective and Preventive Action). This is the single most-cited area in medical device QMS audits. A weak CAPA system — actions opened and never closed, root causes not actually identified, effectiveness never verified — signals to an auditor that the whole system is decorative. Your CAPA process must show genuine root cause analysis, defined actions, and verified effectiveness. Our deep dive on CAPA requirements in ISO 13485 covers the failure modes in detail.

Supplier and purchasing controls (Clause 7.4). You are accountable for what your suppliers provide. You need defined supplier evaluation criteria, approved-supplier records, and controls proportionate to the risk the purchased product carries. Flow your quality requirements down in writing — handshake arrangements do not survive audits.

Production and process controls (Clauses 7.5). This includes process validation for any process whose output cannot be fully verified by later inspection — sterilization and certain welding or molding processes are classic examples — plus identification, traceability, and handling of product. Cleanliness, contamination control, and installation/servicing requirements apply where relevant to your device.

A documentation kit accelerates this layer too. The CAPA log, supplier evaluation forms, nonconformance records, and validation templates are exactly the high-stakes documents you do not want to invent under deadline.

👉 A structured kit gives you defensible templates for all three areas so your effort goes into running the processes, not formatting the paperwork.

Avoid the recurring traps documented in our guide to common mistakes in ISO 13485 QMS implementation — most failures are predictable.

⚠️ Common pitfall: Closing CAPAs without verifying effectiveness. “We retrained the operator” is not a closed CAPA — it’s an action with no proof it worked. Auditors reopen these constantly. Every CAPA needs a defined effectiveness check and evidence it passed before you close it.

Phase 7 — Internal Audit, Management Review, and Certification

Before any external party inspects you, inspect yourself.

Internal audit (Clause 8.2.4). Conduct a full internal audit of your QMS against ISO 13485 using trained, independent auditors. This is your dress rehearsal — the audit that finds problems while you still control the timeline and the narrative. Document findings, open CAPAs, and close them.

Management review (Clause 5.6). Top management formally reviews QMS performance against defined inputs — audit results, customer feedback, process performance, CAPA status, and more — and produces documented outputs and decisions. Registrars treat a missing or hollow management review as a serious gap.

The certification audit (international path). An accredited registrar conducts a two-stage audit:

Stage	Focus	Outcome
Stage 1	Documentation review and readiness	Confirms the system is ready for Stage 2; identifies gaps
Stage 2	On-site implementation audit	Verifies the system operates as documented; raises any nonconformities

Close any nonconformities, and the registrar issues your certificate — typically valid for three years with annual surveillance audits. Choosing an accredited registrar matters; verify accreditation through bodies like ANAB or the relevant IAF member. Our guide to the best ISO certification bodies walks through selection.

⚠️ Common pitfall: Running a hollow management review to check the box. A review that doesn’t actually examine audit results, CAPA status, and process performance — and produce real decisions — is treated by registrars as a serious gap, because it signals leadership isn’t engaged. Make it substantive, and keep the minutes.

FDA QMSR Inspection Readiness

If you are a US manufacturer, your “certification audit” may instead be an FDA inspection — and the bar is the QMSR, which now runs on ISO 13485:2016 plus FDA’s additions.

Practical readiness steps:

Map ISO 13485 to the QMSR additions. Most of your ISO-aligned system satisfies Part 820 directly. Layer in the FDA-specific requirements — labeling and packaging controls, UDI, and certain record and complaint-handling provisions — that exceed the ISO text.
Keep your records inspection-ready, not audit-ready-once. FDA inspections are unannounced or short-notice. The evidence trail from Phase 5 has to be standing, not assembled on demand.
Treat CAPA and complaint handling as the focal points. These are where 483 observations concentrate. A clean, closed-loop CAPA system is your strongest signal of control.
Understand the relationship between the two frameworks. Our comparison of FDA QSR vs ISO 13485 explains exactly what the QMSR changed and where the frameworks now align.

For US manufacturers selling internationally, the efficient move is one ISO 13485 QMS with the QMSR additions built in — not two systems. The frameworks now overlap by design.

Quick Implementation Checklist

Use this as a high-level progress tracker. Each item maps to a phase above.

✅ QMS scope defined and exclusions justified in writing
✅ Official ISO 13485:2016 (and ISO 14971:2019) acquired and read
✅ Top management commitment secured; quality policy and objectives set
✅ Management representative appointed
✅ Core processes mapped with owners, inputs, outputs, and records
✅ Personnel competence and internal auditor training in place
✅ Risk management process and risk management file established (ISO 14971)
✅ Design controls and design history file in place (if you develop devices)
✅ Quality manual, required procedures, and record templates written
✅ Document control and record control operating before volume builds
✅ System operated long enough to generate genuine records (8–12 weeks)
✅ CAPA system demonstrably closing the loop with verified effectiveness
✅ Supplier evaluation and purchasing controls documented and flowed down
✅ Process validation completed where output can’t be fully verified
✅ Full internal audit completed; findings closed
✅ Management review conducted with documented outputs
✅ Registrar selected (international) or QMSR inspection readiness confirmed (US)
✅ Stage 1 and Stage 2 audit passed; nonconformities closed

FAQ

How long does ISO 13485 implementation take?

For a small-to-mid-size manufacturer building from a limited starting point, plan for 6 to 12 months. Companies with a mature ISO 9001 system or a legacy QSR-based system can move faster, while organizations starting from informal processes should plan for the full year. The longest single phase is usually documentation, followed by the operating period needed to generate real records.

Is ISO 13485 certification required in the United States?

No. FDA inspects US manufacturers directly against the QMSR, which incorporates ISO 13485:2016 — certification by a third-party registrar is not legally required. However, building your QMS to ISO 13485 is now the most direct path to QMSR compliance, and certification is required to sell in the EU, Canada, and most international markets. Many US manufacturers certify anyway to serve global customers and demonstrate a recognized standard of control.

What is the difference between ISO 13485 and the FDA QMSR?

The QMSR, effective February 2, 2026, replaced FDA’s old Quality System Regulation and incorporates ISO 13485:2016 by reference into 21 CFR Part 820, plus FDA-specific additions covering labeling, UDI, and certain records. The two are now largely aligned by design. The QMSR is “version locked” to the 2016 edition, so future ISO 13485 revisions will not automatically apply in the US. See our full FDA QSR vs ISO 13485 comparison for detail.

Do I need ISO 14971 to implement ISO 13485?

Effectively, yes. ISO 13485 threads risk-based thinking through the product lifecycle and relies on the methodology in ISO 14971:2019 for risk management. You need a documented risk management process and a risk management file for each device. We explain the relationship in ISO 14971 vs ISO 13485.

Can a contract manufacturer exclude design controls?

Yes, if you build strictly to a customer’s design and do not perform design and development activities. ISO 13485 permits excluding Clause 7.3, but the exclusion must be justified and documented in your QMS scope. You cannot exclude a requirement simply because it is burdensome — only because it genuinely does not apply to your role.

What causes most ISO 13485 audit findings?

CAPA weaknesses lead the list — actions that never close, root causes not genuinely identified, and effectiveness never verified. Document and record control, supplier controls, and process validation are also frequent finding areas. Our guide to common ISO 13485 QMS mistakes covers the recurring patterns.

Should I hire a consultant or use a documentation kit?

It depends on device class, internal capacity, and budget. Consultant-led implementations offer hands-on guidance but commonly run $15,000–$50,000 or more. A structured documentation kit gives you the full QMS architecture — manual, procedures, and record templates — at a fraction of that cost, so your team tailors rather than drafts from scratch. Many small manufacturers start with a kit and bring in targeted consulting only for device-specific risk and design questions.

What is ISO 13485 and who needs it?

ISO 13485 is the international quality management system standard for organizations involved in the medical device lifecycle — design, production, storage, distribution, installation, and servicing. It applies to manufacturers, specification developers, contract manufacturers, sterilization providers, and importers. Our primer, What Is ISO 13485?, covers the fundamentals.

📥 Free Resources

Practical tools to support your implementation — download what fits your project:

ISO 13485 Gap Assessment Checklist — free checklist for medical device manufacturers assessing their QMS against ISO 13485 requirements, clause by clause, before committing to implementation.
ISO 9001 Roadmap — step-by-step implementation guide for organizations building or improving a quality management system, useful if you operate an ISO 9001 base alongside 13485.
Manufacturing Compliance Checklist — practical compliance reference covering key ISO, OSHA, and quality requirements for production environments.
Supplier Quality Checklist — evaluation tool for assessing supplier quality controls and flow-down compliance before audits or new contracts.
AS9100 Rev D Gap Assessment Checklist — 74-item clause-by-clause checklist for aerospace suppliers assessing their QMS before certification, for teams operating across aerospace and medical device lines.

Not Sure What to Do Next?

Your next step depends on where you are in the project:

🔹 If you haven’t assessed your gap yet → start with the free ISO 13485 Gap Assessment Checklist. Don’t commit budget to implementation until you know the size of the gap.
🔹 If you’re ready to build documentation → evaluate a complete ISO 13485 documentation kit before paying consultant rates to draft from scratch. It is the fastest route to an audit-ready document set for most small manufacturers.
🔹 If you’re comparing the US and international paths → read FDA QSR vs ISO 13485 and how much ISO 13485 costs to scope budget and timeline before you choose.

Building an ISO 13485 QMS is a real project, but it is a known one. The clauses are fixed, the phases are sequential, and the failure modes are predictable. Move through it in order, build real evidence as you go, and inspect yourself before anyone else does — and a certification audit or FDA inspection becomes a confirmation, not a gamble. The Standards Navigator exists to make exactly this kind of industrial compliance work clear and survivable for the people who have to actually do it.

Most teams don’t fail ISO 13485 because they misunderstand the standard — they fail because they assumed they were compliant and found out during the audit. The organizations that struggle treat the QMS as paperwork to satisfy a registrar. The organizations that succeed treat it as the operating system that proves their devices are safe — and they build evidence from day one.

The Standards Navigator covers medical device compliance from QMSR readiness to risk management, CAPA, and certification — written from operational and quality management experience, not generic theory.

👉 Get updates on medical device QMS, ISO 13485, and FDA QMSR compliance
👉 Be first to access new gap assessment tools, documentation guides, and implementation resources

Subscribe below to stay ahead.

The Standards Navigator — Industrial Compliance. Clearly Explained.

ISO 13485 Documentation Requirements (2026)

Every document and record ISO 13485 requires — with clause references, document control requirements under Section 4.2, record retention rules, how QMSR changed the documentation landscape, and the seven gaps auditors find most consistently. Built as a reference document quality managers can use before their next audit.

Every document your QMS must have, what auditors check first, and why the gaps between your procedures and your records are where most findings live.

Last Updated: May 2026

Affiliate Disclosure: Some links in this article are affiliate links. If you purchase through them, The Standards Navigator may earn a commission at no additional cost to you.

📋 Free Download: ISO 13485 Gap Assessment Checklist — 64 items covering ISO 13485 clauses + all four FDA QMSR bridge requirements ISO 13485 certification alone does not cover.

The Binder on the Shelf Is Not a QMS

Years ago, working in a nuclear component facility, I watched a certification audit go sideways in the first thirty minutes. The quality manager had spent six months building what looked like a complete quality management system — binders, procedures, forms, the works. The auditor asked to see the document register. The quality manager pointed to the binder. The auditor asked how documents were controlled at the point of use. The quality manager pointed to the binder again.

The binder was the system. It sat on a shelf in the quality office. The machinists on the floor had printed copies of procedures from three years prior. Nobody had a current revision of anything. The audit did not go well.

ISO 13485 documentation is not about having paperwork. It is about having the right documents, in the right format, accessible to the right people, at the right time — and being able to prove all of that during an audit. The standard is specific about what must be documented, what must be retained as records, and what that documentation must demonstrate.

Under QMSR, which took effect February 2, 2026, FDA now evaluates ISO 13485 documentation requirements against the framework directly. Organizations that treat documentation as a filing exercise rather than a quality system function are finding that gap at inspection.

This article covers every documentation requirement ISO 13485 imposes, where auditors look first, and what a compliant documentation system actually looks like in practice.

In This Guide

The difference between documents and records under ISO 13485 — and why it matters for audits
Every mandatory document the standard requires
Every mandatory record the standard requires
Document control requirements under Section 4.2
Record retention rules under Section 4.2.5
The most common documentation gaps auditors find
How QMSR changed the documentation landscape for U.S. medical device manufacturers
Decision-stage guidance for organizations at different points in their documentation journey

Start Here (Top Resources)

🔖 Get ISO 13485:2016 → ANSI Webstore — ANSI is the official U.S. distributor of ISO standards, ensuring you receive the controlled, compliant version required for certification audits. Use coupon CC2026 for 5% off.

🔖 Build compliant QMS documentation → 9001Simplified — 9001Simplified provides ready-to-use documentation kits that dramatically reduce the internal labor required to build a compliant QMS from scratch.

🔖 Train your team on ISO 13485 documentation requirements → BSI Group — BSI Group is a founding member of ISO and one of the world’s largest providers of ISO training courses, recognized by certification bodies globally.

🔖 Pursue or maintain ISO 13485 certification → ISOQAR — ISOQAR is a UKAS-accredited certification body — one of the most recognized in the industry for ISO management system certification.

Browse the What Is ISO 13485? pillar article for full clause context, or use the ISO 13485 Gap Assessment Checklist to identify your specific documentation gaps before your next audit.

Documents vs. Records: The Distinction That Drives Compliance

ISO 13485 treats documents and records as separate categories with different requirements. Confusing them is one of the most consistent sources of documentation findings in surveillance audits.

Documents are instructions, procedures, specifications, and plans — the things that tell people what to do. They are living documents: they can be revised, updated, and superseded. Section 4.2.4 governs their control.

Records are evidence that something was done — completed forms, test results, inspection reports, calibration data, training sign-offs. They are fixed in time: once a record is created, it cannot be altered without creating a documented amendment. Section 4.2.5 governs their control.

The practical distinction matters for two reasons. First, the control requirements differ. Documents need revision control, approval, distribution, and obsolescence management. Records need legibility, identification, storage protection, retrieval, and defined retention periods. A documentation system that applies the same controls to both will have gaps in one or the other.

Second, auditors evaluate them separately. When an auditor asks for a procedure, they are asking for a document. When they ask for evidence, they are asking for a record. Handing an auditor a completed form when they asked for a procedure — or a procedure when they asked for evidence — signals a documentation system that does not understand its own structure.

At this point, most quality managers building or auditing a documentation system should: → Map your document inventory against your record inventory separately. If your document register includes completed forms alongside controlled procedures, your system architecture has a structural problem. 9001Simplified’s documentation kits include pre-structured document and record registers built for ISO 13485 compliance. 9001Simplified provides ready-to-use documentation kits that dramatically reduce the internal labor required to build a compliant QMS from scratch.

Mandatory Documents Under ISO 13485

ISO 13485 requires specific documented procedures and plans across multiple clauses. These are not optional — certification bodies audit for their existence and their content.

ISO 13485 documentation infographic illustrating mandatory quality management system documents with interconnected process icons for quality manuals, risk management, design planning, procedures, records retention, purchasing controls, and document control requirements. — Certification bodies expect documented procedures, controlled records, and defined plans that demonstrate the quality system operates consistently and remains audit ready — see the full list in the table below.

Document	Clause	What It Must Cover
Quality Manual	4.2.2	Scope of the QMS, exclusions with justification, documented procedures or references, description of QMS process interactions
Document Control Procedure	4.2.4	Approval, review, revision control, distribution, obsolescence management, external documents
Records Control Procedure	4.2.5	Identification, storage, protection, retrieval, retention periods, disposition
Management Review Procedure	5.6	Inputs, outputs, frequency, documentation requirements
Competence, Training & Awareness Procedure	6.2	How competence is determined, how training is delivered, how competence is evaluated and recorded
Infrastructure Procedure	6.3	Maintenance of buildings, equipment, and supporting services affecting product quality
Work Environment Procedure	6.4	Control of work environment conditions where required for product conformity
Risk Management Procedure	7.1	Risk management process across the product lifecycle, per ISO 14971
Customer-Related Processes Procedure	7.2	Requirements determination, review, and customer communication
Design & Development Procedure	7.3	Planning, inputs, outputs, review, verification, validation, transfer, changes (if design is not excluded)
Purchasing Procedure	7.4	Supplier evaluation, selection, monitoring, and purchasing information
Production & Service Controls Procedure	7.5	Control of production and service provision, cleanliness, installation, and servicing
Identification & Traceability Procedure	7.5.3	Product identification throughout realization and traceability requirements
Customer Property Procedure	7.5.4	Control and safeguarding of customer-supplied product or data
Preservation Procedure	7.5.5	Preservation of product during processing and delivery
Monitoring & Measurement Equipment Procedure	7.6	Calibration, verification, and control of measuring equipment
Feedback Procedure	8.2.1	Post-market surveillance and feedback collection
Complaint Handling Procedure	8.2.2	Complaint receipt, investigation, and regulatory reporting decisions
Internal Audit Procedure	8.2.4	Audit planning, conduct, reporting, and follow-up
Nonconforming Product Procedure	8.3	Identification, segregation, evaluation, and disposition
CAPA Procedure	8.5.2 / 8.5.3	Corrective and preventive action process, including root cause analysis and effectiveness verification

⚠️ If your organization excludes design and development under Clause 7.3, that exclusion must be justified in the Quality Manual and documented. Exclusions without documented justification are a consistent finding in initial certification audits.

📋 Free Download: ISO 13485 Gap Assessment Checklist — 64 items covering ISO 13485 clauses + all four FDA QMSR bridge requirements ISO 13485 certification alone does not cover.

Mandatory Records Under ISO 13485

Records are the evidence your QMS operated as documented. The standard specifies which records must be maintained — these are the minimum. Your procedures may require additional records.

Record	Clause	What It Must Demonstrate
Management Review Minutes	5.6.3	Inputs reviewed, decisions made, actions assigned with owners and timelines
Education, Training, Skills & Experience	6.2	Competence evaluated, training completed, results recorded
Infrastructure Maintenance	6.3	Maintenance activities and results for quality-critical equipment
Risk Management Records	7.1	Risk analysis, risk evaluation, risk control, residual risk assessment, post-production monitoring
Customer Requirements Review	7.2.2	Requirements determined and confirmed before commitment
Design & Development Records	7.3	Inputs, outputs, reviews, verifications, validations, transfer, and changes (if not excluded)
Design & Development Changes	7.3.9	Change description, evaluation, verification, validation, approval
Supplier Evaluation Records	7.4.1	Evaluation criteria, results, and re-evaluation decisions
Production Process Validation	7.5.2	Validation protocols, results, equipment qualifications
Traceability Records	7.5.3.2	Unique device identification and traceability through production
Customer Property Records	7.5.4	Receipt, condition assessment, and disposition of customer property
Calibration Records	7.6	Equipment identification, calibration standard, results, next due date
Internal Audit Records	8.2.4	Audit plans, findings, nonconformances, corrective actions, follow-up
Product Monitoring & Measurement	8.2.6	Evidence of conformity and identification of release authority
Nonconforming Product Records	8.3	Nature of nonconformity, disposition decision, concession records if applicable
CAPA Records	8.5.2 / 8.5.3	Root cause analysis, action taken, effectiveness verification with criteria and evidence

➡️ 9001Simplified Documentation Kits — Pre-built ISO 13485 procedures, forms, and record templates covering every mandatory document and record listed above. 9001Simplified provides ready-to-use documentation kits that dramatically reduce the internal labor required to build a compliant QMS from scratch.

Document Control: What Section 4.2.4 Actually Requires

Section 4.2.4 sets out seven specific requirements for document control. Each one has a practical implementation implication — and each one is evaluated individually during audits.

1. Documents must be approved before use. Approval must be by authorized personnel. Your document control procedure must define who has approval authority for each document type. A document approved by someone outside that authority — or with no documented approval at all — is a nonconformance.

2. Documents must be reviewed, updated as necessary, and re-approved. Review frequency should be defined in your procedure. Documents that have never been reviewed since initial creation are a finding in surveillance audits — particularly if the regulatory environment or production process has changed.

3. Changes and current revision status must be identified. Every controlled document needs a revision identifier — a number, letter, or date — and your document register needs to reflect current revision status. Auditors check this against what is in use.

4. Relevant versions must be available at points of use. This is the binder-on-the-shelf failure. Current controlled versions must be accessible where work is performed. If people work from printed copies, you need a controlled printing process. If work is performed on a production floor, current procedures must be accessible there — not only in the quality office.

5. Documents must be legible and identifiable. This sounds obvious. It is consistently violated by organizations that allow handwritten annotations, informal updates, or degraded printed copies to remain in service.

6. External documents must be identified and controlled. This includes customer drawings, regulatory guidance documents, referenced standards, and supplier specifications. External documents that affect product quality must be listed in your document control system and their current version verified.

7. Obsolete documents must be prevented from unintended use. Obsolete documents must either be removed from all points of use or clearly marked as obsolete. Finding an active workstation with a superseded procedure is a major nonconformance — regardless of whether anyone was actually using it.

If you are under active FDA inspection pressure → BSI Group ISO 13485 Training covers document control implementation and audit preparation in depth. BSI Group is a founding member of ISO and one of the world’s largest providers of ISO training courses, recognized by certification bodies globally.

Record Retention: What Section 4.2.5 Actually Requires

Section 4.2.5 requires that records be retained for a period at least equal to the lifetime of the medical device, but not less than two years from the date of product release by the organization.

That two-year floor is the minimum. In practice, most medical device records should be retained significantly longer:

Implantable devices — the device lifetime may span decades. Records need to match.
Devices with long service lives — the same logic applies.
FDA QMSR requirements — align with ISO 13485 on the two-year minimum but your complaint handling procedure may require longer retention for MDR-related records.
Customer contractual requirements — OEM customers increasingly specify record retention periods in their supplier quality agreements. These requirements take precedence where they are more stringent than the standard’s minimum.

Your records control procedure must define retention periods for each record type. A blanket “two years” policy applied to all records — including design history files and risk management records for long-life devices — is not compliant.

Provider	What You Get	Best For
ANSI Webstore	ISO 13485:2016 official standard	Any organization needing the controlled, compliant version of the standard
9001Simplif i ed	QMS documentation kits with record templates	Organizations building documentation from scratch or rebuilding after a major finding
BSI Group	ISO 13485 training courses	Teams implementing documentation systems or preparing for initial certification
ISOQAR	ISO 13485 certification	Organizations ready to pursue or maintain certification

Most organizations building documentation systems from scratch need all three:

The standard from ANSI Webstore (use CC2026 for 5% off)
Lead implementer training from BSI Group
A documentation kit from 9001Simplified

This combination covers the standard, the knowledge, and the implementation infrastructure.

The Most Common Documentation Gaps

ISO 13485 documentation gaps infographic illustrating seven common audit findings, including outdated document registers, incomplete supplier records, weak CAPA evidence, missing procedures, and disconnected risk management records within medical device quality systems. — Documentation failures rarely appear as isolated findings. They create chains of audit problems across CAPA, supplier controls, training, management review, and risk management. The gap is usually discovered long after it was created.

These are the findings that appear most consistently in ISO 13485 surveillance audits and QMSR inspections. Each one points to a specific procedure or record requirement.

The Quality Manual references procedures that don’t exist. A common initial certification shortcut is writing a Quality Manual that references a full set of documented procedures — then discovering during the surveillance audit that several of those procedures were never finalized. The Quality Manual and the document register must be synchronized.

The document register is not current. Document registers that haven’t been updated in months, that show revision numbers inconsistent with what is in use, or that are missing entire document categories are a consistent finding. The register is the first thing many auditors check.

Risk management records stop at design transfer. ISO 14971 requires risk management across the product lifecycle. Design-phase risk files with no post-production updates — no connection to complaint data, service reports, or CAPA findings — are incomplete regardless of how thorough the original analysis was. See ISO 14971 vs ISO 13485 for the full lifecycle requirement.

CAPA records close without effectiveness verification evidence. A CAPA record that reads “action implemented — problem resolved” with no supporting data is not a closed CAPA — it is an open finding waiting to be issued. For the complete breakdown of what effectiveness verification requires, see CAPA Requirements in ISO 13485.

Supplier qualification records are incomplete or outdated. An approved supplier list without corresponding qualification evidence, or qualification records for suppliers whose scope has changed without requalification, are consistently cited findings under Clause 7.4.

Training records prove attendance, not competence. Sign-off sheets showing who attended a training session are not competence records. The record must show what competence was evaluated, by what method, and what the result was. See Common Mistakes in ISO 13485 QMS for the full breakdown of this finding.

Management review minutes record presentations, not decisions. Minutes that describe what was presented in management review without documenting what was decided are a major finding under Section 5.6.3. Every input reviewed must produce a documented output — a decision, an action, or a rationale for no action.

How QMSR Changed the Documentation Landscape

FDA’s Quality Management System Regulation, effective February 2, 2026, aligns U.S. medical device QMS requirements with ISO 13485:2016. For documentation, the practical changes are significant.

The Device Master Record (DMR) structure is now explicitly required. Under QMSR, the DMR — which must include device specifications, production process specifications, quality assurance procedures, packaging and labeling specifications, and installation and maintenance procedures — is a specific documentation requirement that ISO 13485 certification alone does not fully address.

Complaint files under 21 CFR 820.198 remain a separate requirement. ISO 13485 requires a complaint handling procedure. QMSR additionally requires that complaint files contain specific elements — including the decision on whether the complaint required investigation and, if so, the results of that investigation — that go beyond what most ISO 13485 complaint procedures specify.

MDR procedures must be documented separately. Medical Device Reporting obligations are a regulatory requirement that sits outside ISO 13485 but must be addressed in your QMS documentation under QMSR.

⚠️ FDA QMSR compliance date was February 2, 2026. If your documentation system has not been reviewed against the four QMSR-specific bridge requirements since that date, that review is overdue. The ISO 13485 Gap Assessment Checklist covers all four QMSR bridge requirements explicitly alongside the standard ISO 13485 clause requirements.

For the full regulatory alignment picture, see FDA QSR vs ISO 13485.

Infographic explaining the major operational and regulatory changes introduced under the FDA QMSR, including terminology alignment, expanded risk management, inspection changes, and ISO 13485 document control requirements. — The FDA’s QMSR transition introduced major changes beyond terminology — expanding risk management expectations, changing inspection structure, and aligning medical device quality systems directly with ISO 13485.

Why Organizations Delay Getting Documentation Right

“We’ll clean it up before the surveillance audit.”

This is the most common delay rationalization — and it consistently produces the worst outcomes. Documentation gaps that accumulate over 11 months cannot be credibly remediated in the 30 days before a surveillance visit. Auditors can identify recently created records. A CAPA file dated three weeks before the audit for a problem that complaint data shows has existed for eight months is not evidence of a functioning QMS — it is evidence of audit preparation, which auditors treat as a different category of finding.

“Our documentation was good enough for initial certification.”

Initial certification evaluates documentation at a point in time against a system that was built to be audited. Surveillance audits evaluate whether that system has been maintained — which means they look at records created since the last audit, not at procedures written before it. Organizations that passed initial certification and then stopped maintaining their documentation systems often face multiple major nonconformances at the first surveillance visit.

“We don’t have the internal resources to build this properly.”

This objection is real — but the cost of building documentation properly before certification is substantially lower than the cost of remediation after a major nonconformance. A documentation kit from 9001Simplified covers every mandatory document and record template in a ready-to-use format. 9001Simplified provides ready-to-use documentation kits that dramatically reduce the internal labor required to build a compliant QMS from scratch. The internal labor required to customize a pre-built kit is a fraction of what is required to build from scratch — and a fraction of what remediation costs after a finding.

Frequently Asked Questions

What documents are required by ISO 13485?

ISO 13485 requires documented procedures covering quality manual, document control, records control, management review, training and competence, risk management, customer requirements, purchasing, production controls, identification and traceability, calibration, feedback, complaint handling, internal audit, nonconforming product, and CAPA. The full list with clause references is in the Mandatory Documents table above.

What records are required by ISO 13485?

ISO 13485 requires records covering management reviews, training and competence evaluations, risk management activities, design and development (if not excluded), supplier evaluations, calibration, internal audits, product monitoring, nonconforming product dispositions, and CAPA activities. The full list with clause references is in the Mandatory Records table above.

How long must ISO 13485 records be retained?

The standard requires retention for at least the lifetime of the device, with a minimum of two years from product release. For implantable devices and devices with long service lives, the retention period is typically longer and should be defined in your records control procedure. FDA QMSR aligns with this minimum but specific record types — particularly MDR-related records — may require longer retention.

Does ISO 13485 require a Quality Manual?

Yes. Section 4.2.2 requires a Quality Manual that defines the scope of the QMS, documents or references procedures, and describes the interactions between QMS processes. The Quality Manual is one of the first documents an auditor requests.

Can we use electronic records to meet ISO 13485 requirements?

Yes — electronic records are acceptable provided your document control system ensures they are controlled, legible, retrievable, and protected from unauthorized modification. Electronic systems used to manage controlled documents must themselves be validated if they affect product quality.

What is the difference between a controlled document and a record under ISO 13485?

A controlled document is an instruction, procedure, or specification that tells people what to do — it can be revised and must be version-controlled. A record is evidence that something was done — it is fixed in time and must be retained according to your records control procedure. Section 4.2.4 governs controlled documents; Section 4.2.5 governs records. The distinction is fundamental to building a compliant documentation system.

Does design and development documentation apply to all medical device manufacturers?

Only if the manufacturer performs design and development activities. If your organization manufactures to customer specifications and does not perform design activities, you may be eligible to exclude Clause 7.3 — but that exclusion must be documented and justified in your Quality Manual. Contract manufacturers who claim a 7.3 exclusion without justification are consistently cited at initial certification.

How do FDA QMSR documentation requirements differ from ISO 13485?

QMSR aligns with ISO 13485 but adds four specific requirements: the Device Master Record structure, complaint files under 21 CFR 820.198, Medical Device Reporting procedures, and corrections and removals procedures. ISO 13485 certification alone does not cover these four requirements. The ISO 13485 Gap Assessment Checklist addresses all four explicitly.

What is the first thing an auditor looks at for ISO 13485 documentation?

Most auditors start with the document register — to verify that controlled documents are listed, revision levels are current, and the register reflects what is actually in use. From there they move to the Quality Manual to verify scope and procedure references. Gaps in either of those two items typically expand the audit’s scope significantly.

Free Resources

📋 Free Download: Manufacturing Compliance Checklist — ISO 9001, 14001, 45001 & OSHA — 50 items with gap scoring across all systems.

📋 Free Download: Supplier Quality Checklist — ISO 9001 Clause 8.4 — all supplier controls auditors evaluate, 45 items with scoring.

📋 Free Download: ISO 9001 Implementation Roadmap — The exact 5-phase process from gap assessment to Stage 2 audit clearance.

📋 Free Download: ISO 13485 Gap Assessment Checklist — 64 items — ISO 13485 clauses + all four FDA QMSR bridge requirements ISO 13485 certification alone does not cover.

Not Sure What to Do Next?

→ You need the official ISO 13485:2016 standard → ANSI Webstore — Use CC2026 for 5% off. ANSI is the official U.S. distributor of ISO standards.

→ You need to build ISO 13485 documentation from scratch → 9001Simplified Documentation Kits — ready-to-use procedures, forms, and record templates for every mandatory document.

→ You need to train your team on documentation requirements → BSI Group ISO 13485 Training — BSI Group is a founding member of ISO and one of the world’s largest providers of ISO training courses.

→ You are ready to pursue ISO 13485 certification → ISOQAR — UKAS-accredited, one of the most recognized certification bodies in the industry.

→ You need to assess your documentation gaps before your next audit → ISO 13485 Gap Assessment Checklist — free, 64 items.

→ You need to understand how QMSR changed your documentation obligations → FDA QSR vs ISO 13485

→ You need to understand CAPA record requirements in depth → CAPA Requirements in ISO 13485

→ You need to understand the most common documentation audit findings → Common Mistakes in ISO 13485 QMS

→ You need to understand how risk management documentation connects to your QMS → ISO 14971 vs ISO 13485

→ You need to understand the full ISO 13485 clause structure → What Is ISO 13485?

→ You want to buy ISO 13485 → Buy ISO 13485

→ You want to browse all medical device standards → explore standards by compliance area

Still figuring out where to start?

If you are not ready to commit to a documentation build yet — that is normal. Most organizations spend several weeks between identifying gaps and starting remediation.

The best next step: → Download the free ISO 13485 Gap Assessment Checklist — it takes 20 minutes and tells you exactly which documents and records you are missing before you spend anything.

Feature image promoting an ISO 13485 Gap Assessment Checklist for medical device manufacturers, contract manufacturers, and component suppliers preparing for certification and FDA QMSR compliance. — ISO 13485 Gap Assessment Checklist designed to help medical device manufacturers identify compliance gaps, prioritize actions, and prepare for certification and FDA QMSR requirements.

📋 Free Download: ISO 13485 Gap Assessment Checklist — 64 items — ISO 13485 clauses + all four FDA QMSR bridge requirements ISO 13485 certification alone does not cover.

The Binder Is Not the System

Documentation is not ISO 13485’s most technically demanding requirement. But it is the foundation every other requirement rests on. Without controlled documents, procedures cannot be consistently followed. Without records, there is no evidence that procedures were followed at all. Without a document control system that connects what is written to what people actually use, the gap between those two things grows quietly — until an auditor measures it.

The organizations that handle documentation audits well are not the ones with the most sophisticated quality management software or the thickest procedure binders. They are the ones whose documentation reflects how work actually gets done — current, accessible, and connected to the records that prove it.

That alignment takes discipline to build and discipline to maintain. It does not take complexity.

At The Standards Navigator, complex standards are translated into practical, real-world guidance you can act on.

Subscribe below to stay ahead.

The Internal Audit That Used to Be Private Isn’t Anymore

In This Guide

Table of Contents

👉 Start Here (Top Resources)

What Clause 8.2.4 Actually Requires

Internal Audits vs. Supplier Audits vs. Certification Audits

Auditor Competence: What Clause 6.2 Actually Requires

Building a Risk-Based Audit Program

The Internal Audit Process, Step by Step

A Real Finding, Start to Finish

The Five Most Common Findings

MDSAP: What Changes for Multi-Market Audits

What Changed: QMSR and ISO 19011:2026

Quick Audit-Readiness Checklist

FAQ

How often does ISO 13485 require internal audits?

Can the same person who performs a process also audit it?

Do internal auditors need a formal certification?

Does the FDA QMSR require a separate internal audit program from ISO 13485?

Are internal audit reports confidential from FDA inspectors?

What’s the difference between an internal audit and a supplier audit under ISO 13485?

Does MDSAP replace our ISO 13485 internal audit requirement?

What’s the most common reason internal audit programs fail a certification audit?

Should we hire a consultant to run our internal audits, or can we do it ourselves?

📥 Free Resources

Not Sure What to Do Next?

Subscribe for Medical Device Compliance Updates

Subscribe

The Question That Stalls Every EU Market Entry Meeting

In This Guide

Table of Contents

👉 Start Here

What Is EU MDR 2017/745?

What Is ISO 13485?

MDR vs. ISO 13485: Core Differences

Why Manufacturers Conflate the Two

Where MDR and ISO 13485 Overlap

MDR Transition Timelines: Where Things Stand in 2026

Do You Need Both? A Decision Framework

Common Mistakes That Surface in Notified Body Review

Quick Reference Checklist

FAQ

Does ISO 13485 certification satisfy MDR requirements?

Is ISO 13485 mandatory for the EU market?

Do U.S.-only manufacturers need to worry about MDR?

What’s the current MDR transition deadline for legacy devices?

Is the EU actually changing MDR requirements soon?

What’s the biggest documentation gap Notified Bodies flag?

Can one gap assessment cover both ISO 13485 certification readiness and MDR technical file readiness?

Where should a manufacturer start if pursuing both?

📥 Free Resources

Not Sure What to Do Next?

Stop Guessing Where Your MDR Gap Actually Is

Subscribe

Your Sterilization Validation File Is the First Thing an Auditor Opens

In This Guide

Table of Contents

👉 Start Here (Top Resources)

Why Sterilization Standards Sit Inside Your QMS

The Standards Aren’t Interchangeable

ISO 11135: Ethylene Oxide Sterilization

ISO 11137: Radiation Sterilization

ISO 17665: Moist Heat Sterilization

ISO 11607: Sterile Packaging

Sterility Assurance Level: The 10⁻⁶ Standard

Using a Contract Sterilizer Doesn’t Transfer the Risk

Common Findings in Sterilization Validation Files

Common Sterilization Myths

Quick Audit Checklist

FAQ

What’s the difference between ISO 11135 and ISO 11137?

Does ISO 17665 apply to reusable devices?

Is ISO 11607 required if I use a contract packaging supplier?

What is Sterility Assurance Level (SAL) and why is 10⁻⁶ the target?

Do I need to revalidate if I switch contract sterilizers?

How does ISO 14971 relate to sterilization validation?

Does the FDA QMSR require anything beyond ISO 13485 for sterilization?

What’s the most common reason sterilization validation fails an audit?

Not Sure What to Do Next?

📥 Free Resources