ISO 13485
Assess an operating medical-device QMS against ISO 13485:2016 and current FDA QMSR requirements without confusing readiness, certification or FDA approval.

On this page · 12 sections
- 1Readiness means an operating quality system
- 2Define organizational and product scope first
- 3Distinguish incorporated requirements and FDA additions
- 4Build a crosswalk without assuming equivalence
- 5Integrate risk into routine process decisions
- 6Control suppliers and outsourced production evidence
- 7Establish production and acceptance controls
- 8Review complaints, servicing and corrective action
- 9Make document and record control operational
- 10Assign ownership and management oversight
- 11Audit implementation and state readiness honestly
- 12Close gaps with evidence rather than declarations
How does ISO 13485 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Readiness means an operating quality system
ISO 13485 readiness is the ability of a medical-device organization to demonstrate that its quality management system is defined, implemented and effective for its activities and applicable regulatory obligations. It is not a synonym for buying software, preparing an audit binder or obtaining a certificate. The relevant evidence connects product requirements, risk, controlled processes, competent personnel and actual records across the device lifecycle.
For US finished-device manufacturers, FDA's Quality Management System Regulation, or QMSR, became effective on 2 February 2026. The final rule was published on 2 February 2024 at 89 FR 7496. Current 21 CFR Part 820 incorporates ISO 13485:2016 by reference and includes FDA-specific provisions. A readiness assessment after the effective date must address that current framework rather than describing QMSR as a future transition.
ISO 13485 certification, where pursued, is a conformity-assessment activity by a certification body. It does not constitute FDA approval, substitute for FDA inspection, or establish compliance with all market-specific device laws. Likewise, operating under FDA's QMSR does not mean an organization has obtained an ISO certificate. Keep the standard, the regulatory requirement and the certification status separate in procedures and public statements.
02Define organizational and product scope first
Start with the organization's actual role: design, manufacturing, contract manufacture, distribution, servicing or other activities. Define the products and sites covered, outsourced processes and applicable markets. The FDA final rule addresses the scope of Part 820 for finished-device manufacturers; do not assume that every business registered with FDA, every component supplier or every third-party service organization falls under identical obligations.
A scope statement should explain which activities the firm performs and which it controls through external providers. Outsourcing an operation does not automatically eliminate the need to control its effect on device quality. Conversely, a contract requirement imposed on a supplier should not be described as proof that FDA directly regulates that supplier under the same Part 820 scope. Resolve the applicable duties for the actual arrangement.
Use a product-and-market obligations register to separate quality-system requirements from device-specific submission, labeling, reporting and other obligations. This is a suggested implementation tool, not a mandated document title. EU MDR, IVDR and other market requirements need their own analysis. An ISO 13485-focused article does not establish complete conformity with those separate regimes or authorize commercial supply.
03Distinguish incorporated requirements and FDA additions
Section 820.7 identifies the incorporated standard. Use the edition actually incorporated: ISO 13485:2016, not an assumed future revision. FDA's rulemaking explains that a later standard revision does not automatically become US law. The full standard is copyrighted; this article summarizes publicly available FDA explanations and does not reproduce paywalled clause text or replace access to the applicable standard.
The QMSR includes FDA-specific provisions, including control of records in section 820.35 and device labeling and packaging controls in section 820.45. Section 820.35 specifies information for certain complaint and servicing records and addresses device identification. Read those provisions alongside the incorporated standard rather than marking an ISO audit checklist complete and assuming the FDA-specific obligations have therefore been assessed.
| Assessment layer | Evidence to examine |
|---|---|
| Incorporated ISO 13485:2016 requirements | Authorized standard, applicable procedures and implementation records |
| Current FDA Part 820 additions | Record and labeling controls mapped to the specific FDA provisions |
| Other applicable FDA duties | Separate analysis of reporting, identification and other relevant requirements |
| Certification, if sought | Defined certification scope and actual certification-body assessment |
FDA-specific requirements should be visible in the process that performs them. A separate compliance spreadsheet is insufficient if the complaint form, servicing record or packaging instruction omits the information it is meant to capture. Assess the executed record as well as the written procedure. Do not infer compliance solely from a familiar legacy document name.
04Build a crosswalk without assuming equivalence
Many established manufacturers still use legacy terms such as device master record and device history record. Keeping useful terminology is not inherently a problem, but a procedure cited only to an obsolete Part 820 section can conceal an incomplete assessment. Build a crosswalk that identifies the current requirement, the responsible process, the controlled document and the implementation evidence.
Do not assume a one-to-one correspondence between every former section and an ISO clause. The final rule changed the regulatory structure and includes definitions and additional provisions. A crosswalk should explain how the firm's existing record set satisfies the current obligation rather than merely replacing section numbers in headers. Identify genuine gaps, redundant controls and documents whose references need updating.
The sample eDHR is a readable example of production-history evidence. It does not reproduce all incorporated requirements or prove that a manufacturer's device history is complete. Use it to ask which actual records support identity, acceptance, process execution and disposition for a specific device lot, and which records are maintained elsewhere under controlled references.
05Integrate risk into routine process decisions
FDA's final-rule discussion describes risk management as threaded throughout the incorporated quality-system framework, not confined to a single design-control activity. A practical readiness review examines how risk informs purchasing, production, process changes, measurement and problem evaluation. This is not permission to omit applicable requirements merely because a team assigns a low numerical score.
Define the risk question before selecting the control: what failure could affect device safety, performance or conformity, what evidence supports the assessment, and what process prevents or detects it? Relate the control to the actual product and operation. A generic risk register with no connection to supplier acceptance, manufacturing parameters or complaint evaluation may not explain why the system is adequate.
ISO 14971 is a separate risk-management standard; FDA did not incorporate it through this QMSR rule. A firm may use it where appropriate, but should not state that the QMSR automatically incorporates every related ISO standard. Maintain a clear distinction between the binding incorporated requirements, other applicable obligations and the technical methods the firm chooses to support its programme.
06Control suppliers and outsourced production evidence
Readiness includes confidence in externally supplied products and outsourced processes. Establish the supplier evaluation basis, purchasing requirements, acceptance activities, change communication and records needed for the actual relationship. The applicable control depth depends on the product and process risk, not on a universal questionnaire size or a supplier's commercial prominence.
For outsourced operations, define the records the manufacturer needs and when it needs them. A contract manufacturer may retain primary production records while providing an authorized evidence package; the arrangement must still support the manufacturer's applicable responsibilities. Check access to deviations, relevant changes, acceptance data and traceability. A supplier certificate is useful evidence but not an automatic substitute for every required control.
Test a real incoming item or contracted operation from purchasing requirements into acceptance and downstream use. Identify who approves the supplier, who evaluates a change and who decides the status of affected material. Where an issue is found, determine whether its impact was assessed across related lots and products. These are implementation questions, not claims about any customer's actual supply chain.
07Establish production and acceptance controls
The Medical Device Production Guide provides readable operational context for manufacturing records and quality decisions. For an actual readiness assessment, identify the approved instructions, equipment, personnel competence, material identification, in-process controls and acceptance evidence for the device. Link the records to the product and revision actually manufactured.
Consider whether a process result can be adequately verified afterward and what process-validation obligations apply under the incorporated standard and applicable rules. Validation is not synonymous with final inspection or a software demonstration. Define intended use, acceptance criteria, qualification evidence and continuing controls for the actual process. This article supplies no universal validation protocol or claim that a particular system validates itself.
Nonsterile and sterile devices have different process contexts. Do not import aseptic-drug assumptions into every device operation or imply that a packaging inspection proves sterilization suitability. Assess the device's actual characteristics and applicable controls. The customer or manufacturer owns its validation decisions, approvals and evidence; an example record does not transfer that responsibility to a website or vendor.
08Review complaints, servicing and corrective action
Current section 820.35 requires additional information in certain complaint records, including device identity, receipt date, relevant identifiers, complainant details, complaint nature, correction or corrective action, and reply where applicable. It also addresses documentation when a similar complaint has already been investigated and another investigation is not performed. A readiness review should examine the actual rationale, not merely a checkbox labeled 'duplicate.'
The section specifies information for servicing activities and includes UDI-related record requirements. Determine which activities apply and verify the records used in practice. Keep complaint evaluation and applicable FDA reporting obligations connected but distinct: closing an internal complaint is not by itself a reporting assessment under Part 803. The final rule does not remove FDA's separate statutory or inspection authority.
Corrective and preventive actions remain distinct concepts in the incorporated framework described by FDA. A firm can structure its procedures coherently without assuming one universal organizational design, but it should demonstrate how causes are evaluated, actions justified, effectiveness assessed and records maintained. Trend data should lead to an assessed decision, not a numerical dashboard with no responsible owner.
09Make document and record control operational
Document control concerns the instructions and requirements personnel use; record control concerns evidence of activities and decisions. A controlled procedure can be correct while the executed records are incomplete. Conversely, a well-filled production form cannot compensate for an unapproved instruction. Assess both sides and their relationship to the applicable product revision.
Define approval, change, availability, correction, access, retention and retrieval according to the applicable requirements. For electronic records, examine intended use, attribution, relevant history and availability. Do not assume that exporting a PDF preserves all dynamic record functionality or that a timestamp alone establishes a person's authorization. The document control page supplies commercial context, not a certification claim.
Migration deserves its own evidence. Confirm that historical references, approvals and relationships survive the transfer and can be reconstructed for a sampled lot. Test the archived result as a reviewer would use it. A current screen showing the latest product version does not necessarily explain which instruction applied to an earlier batch or who approved a historical change.
10Assign ownership and management oversight
Top management should provide the resources and oversight needed for the quality system to operate. Process owners maintain effective procedures and evidence; quality personnel evaluate conformity and escalations; technical specialists supply product-and-process expertise. These practical role descriptions do not reproduce the standard's copyrighted wording or replace an organization's responsibility mapping.
A readiness plan should identify a gap, its risk or regulatory significance, accountable owner, action, evidence required and review date. Distinguish corrective work from administrative citation updates. Replacing a legacy section number may be necessary, but it does not prove that a missing complaint field, ineffective supplier control or unassessed process has been resolved.
Management review should consider actual system performance and unresolved issues within the applicable framework. Training records should support competence for assigned work, not merely attendance at a general QMSR presentation. Where a process depends on one person's undocumented knowledge, capture the necessary instruction and decision authority so the process remains defensible when that person is unavailable.
11Audit implementation and state readiness honestly
Select a device lot and follow its requirements through purchasing, manufacture, acceptance and disposition. Then follow a complaint or nonconformity back into its related product and process records. Review an outsourced operation and a changed instruction. These evidence paths test whether the quality system works across functions rather than only within an audit checklist.
Ask whether the incorporated edition and FDA additions have been assessed, whether the certification scope matches the actual organization, and whether critical gaps remain open. Potential weaknesses include obsolete regulatory cross-references, treating a certificate as FDA approval, incomplete complaint or servicing fields, outsourced records unavailable for review, and validation conclusions without an intended-use basis.
Describe the outcome precisely: assessed, gaps identified, actions underway, internally verified, or independently certified where an actual certificate supports that statement. Do not promise inspection success or infer certification from readiness work. The medical device sector page and linked guide support further reading; they do not alter the manufacturer's regulatory obligations or provide a substitute for qualified review.
12Close gaps with evidence rather than declarations
For each significant gap, define the record that will show the action worked. A revised complaint form needs a checked example demonstrating that the necessary information is captured. A supplier-control revision needs evidence that the relevant purchasing and acceptance decisions now follow it. A document-reference correction needs a verified crosswalk, not just a new footer citation.
Review effectiveness after implementation at a proportionate interval and with suitable evidence. Do not mark a technical issue complete because its training presentation was delivered. Keep open issues, interim controls and final conclusions distinguishable. This approach supports an honest readiness statement while preserving the difference between internal improvement, independent certification and a regulator's actual assessment.
Frequently asked questions
Q.Does ISO certification replace FDA QMSR compliance?+
No. Certification and compliance are different assessments. Current Part 820 incorporates ISO 13485:2016 and contains FDA-specific provisions; certification does not replace FDA inspection or other applicable duties.
Q.When did the QMSR take effect?+
The final rule published at 89 FR 7496 became effective on 2 February 2026. A current readiness assessment must not describe that transition as still pending.
Primary sources
Further reading
Explore this topic
ISO 13485 sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
GS1 identifiers, barcodes, ASNs and the rules that require lot-level traceability.
Device-specific rules, submissions and the standards that bind them.
Want to see how ISO 13485 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
