Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

FDA QMSR (21 CFR Part 820): the ISO 13485 harmonization, explained

Last updated:

The Quality Management System Regulation (QMSR) — FDA's amended 21 CFR Part 820, the device current good manufacturing practice (CGMP) rule every US medical device manufacturer has to operate under — became mandatory on its February 2, 2026 compliance date, two years after the final rule, "Medical Devices; Quality System Regulation Amendments," was published in the Federal Register on February 2, 2024 at 89 FR 7496. The regulation's number didn't change; its substance did, by incorporating the international standard ISO 13485:2016 by reference instead of maintaining a US-only quality system rule written from scratch.

Key takeaways

  • The text shrank and the substance moved into ISO 13485.
  • Two definitions matter to software teams.
  • The record names are gone; the records are not.
  • No. FDA's QMSR FAQ (FAQ 13) says: "The FDA will not require certificates of conformance to ISO 13485 and will not issue certificates of conformance to ISO 13485.

What changed in Part 820, and what stayed?

The text shrank and the substance moved into ISO 13485. The final rule (docket FDA-2021-N-0507) replaced the old subparts with a short regulation that incorporates by reference ISO 13485:2016 (third edition, 1 March 2016) and Clause 3 of ISO 9000:2015. FDA's FAQ says the agency found the ISO 13485 requirements, "when taken in totality, substantially similar" to the old Quality System regulation. The codified part now has six live sections:

Section Content
820.1 Scope Finished devices for human use; FD&C Act controls where ISO 13485 conflicts
820.3 Definitions ISO 13485 and ISO 9000 terms apply, except FD&C Act and FDA definitions that supersede them
820.7 Incorporation by reference ISO 9000:2015 Clause 3; ISO 13485:2016
820.10 Requirements for a QMS Document an ISO 13485 QMS, plus listed FDA requirements
820.35 Control of records Extra content for complaint, servicing and UDI records
820.45 Device labeling and packaging controls Inspection and release of labeling

Scope did not change: the rule applies to finished device manufacturers, including accessory makers, and not to component suppliers, who are "encouraged to consider" it. FDA's FAQ 12 notes that both standards can be read in read-only form through the ANSI IBR portal and the ISO Online Browsing Platform.

What does the QMSR add on top of ISO 13485?

A short list of FDA-specific requirements, most of them links to other parts of 21 CFR:

Provision ISO 13485 clause it supplements FDA requirement
820.10(b)(1) 7.5.8 Identification UDI system under part 830
820.10(b)(2) 7.5.9.1 Traceability Device tracking under part 821, if applicable
820.10(b)(3) 8.2.3 Reporting to regulatory authorities Medical device reports under part 803
820.10(b)(4) 7.2.3, 8.2.3, 8.3.3 Advisory notices under part 806 (corrections and removals)
820.10(c) 7.3 Design and development Required for class II and III devices, and for class I "devices automated with computer software" plus five listed class I types
820.10(d) 7.5.9.2 Implant traceability also for devices that support or sustain life
820.35(a), (b) 8.2.2, 7.5.4 Named fields in complaint and servicing records
820.45 7.5.1 Labeling and packaging examined, released and documented

Two definitions matter to software teams. A component is "any raw material, substance, piece, part, software, firmware, labeling, or assembly" intended for the finished device, so third-party libraries and firmware images are components under the QMSR. And FD&C Act definitions, such as "device" in section 201(h), override ISO 13485's terms. Section 820.10(e) states the consequence of a gap: a device made without compliance is adulterated under section 501(h).

What happened to the DHF, DMR and DHR?

The record names are gone; the records are not. In its response to comment 31 FDA says it is "not retaining separate requirements" for the quality system record, device master record, design history file and device history record, because ISO 13485 already requires their contents. The rough equivalents:

  • Design history file → the design and development file (Clause 7.3.10);
  • Device master record → the medical device file (Clause 4.2.3), which starts from the final design output;
  • Device history record → the medical device or batch record (Clause 7.5.1).

Renaming a folder is not the work. Check that each ISO 13485 file actually contains or references what the clause asks for.

Do you need ISO 13485 certification to comply with QMSR?

No. FDA's QMSR FAQ (FAQ 13) says: "The FDA will not require certificates of conformance to ISO 13485 and will not issue certificates of conformance to ISO 13485. A certificate of conformance to ISO 13485 will not exempt a manufacturer from an FDA inspection." It adds that FDA inspections "are scheduled based on risk factors," while third-party audits "occur annually based on a three-year plan," and that QMSR inspections do not follow the MDSAP audit plan. MDSAP stays available as a voluntary program. An EU-certified manufacturer still gets inspected; an uncertified one can still comply.

How did FDA inspections change on 2 February 2026?

Three things changed on the effective date:

  • New compliance program. FDA stopped using the Quality System Inspection Technique (QSIT) and retired programs 7382.845 and 7383.001. Investigators now follow Compliance Program 7382.850, which groups QMSR requirements into six QMS Areas (Change Control; Design and Development; Management Oversight; Measurement, Analysis, and Improvement; Outsourcing and Purchasing; Production and Service Provision) and four Other Applicable FDA Requirements (Medical Device Reporting; Reports of Corrections and Removals; Medical Device Tracking Requirements; Unique Device Identification). Each inspection covers at least one element in every area, with risk management documentation used to focus it.
  • Records that were off limits. The old § 820.180(c) exception kept management reviews, quality audits and supplier audit reports out of inspection. FAQ 8 says the exceptions "are not maintained in the QMSR," and the preamble's reason is harmonization: other regulators and MDSAP auditors already see those records.
  • Older records count. FAQ 7 says investigators may review records created before 2 February 2026, and suggests a comparative analysis showing that they meet the QMSR.

Design records. CP 7382.850 Part III.I keeps the limit on FDA's design-record access under section 704(e): it applies once the device is marketed, or after a clinical investigation plan goes to an IRB, an IDE, 510(k), PMA, HDE or PDP submission, or a change to a marketed device.

Where does cybersecurity sit inside a QMSR quality system?

Across the design, purchasing and improvement clauses, though the codified rule never uses the word. FDA makes the link in its guidance Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions, issued 3 February 2026. It supersedes the 27 June 2025 "Quality System Considerations" version and restates its references in ISO 13485 terms. Section IV.A is titled "Cybersecurity is Part of Device Safety and the Quality Management System Regulation (QMSR)." The clause references FDA gives:

ISO 13485 / 21 CFR Cybersecurity use in the guidance
7.1 Risk management in product realization A safety risk assessment and "a separate, accompanying security risk assessment"
7.3 Design and development; 820.10(c) Security requirements, architecture views, threat modeling, testing
7.3.7 Validation Software validation, including cybersecurity controls in their environment of use
7.4 Purchasing Supplier controls for third-party software; plans for unsupported components
7.3.10 and 4.2.3 files Where third-party component evidence is documented
7.5.4 and 820.35(b) Servicing Records of updates and service activity
8.2.2 and 820.35(a) Complaint handling Intake of security complaints
8.2.4, 8.4, 8.5 Audit, data analysis and CAPA for vulnerabilities found after release
Part 806 Corrections and removals, cited for the cybersecurity management plan

The guidance treats a Secure Product Development Framework (SPDF) as "one approach to help ensure that the QMSR is met," naming the HSCC JSP2, IEC 81001-5-1 and ANSI/ISA 62443-4-1 as options. It says an SBOM "or an equivalent capability should be maintained as part of the device's configuration management," and that manufacturers should keep custodial control of source code. Security risk management interfaces with ISO 14971 safety risk management as described in AAMI TIR57 and ANSI/AAMI SW96; software lifecycle evidence usually comes from IEC 62304.

How does an inspector treat a cyber device?

As a device first, with an extra check. CP 7382.850 Part III.H says cyber devices under section 524B(c) "should be considered for review for conformity with Section 524B(b)(2)" in domestic and foreign inspections, and gives investigators a CyberMed support contact. Part V.6 says CDRH should consider action when a manufacturer fails a 524B(b)(2) requirement for a cyber device submitted after 29 March 2023 (a prohibited act under section 301(q)), and that a QMSR failure involving cybersecurity can also support action. The premarket side is covered in our FDA premarket cybersecurity guide; the postmarket side in FDA postmarket cybersecurity.

Worked example: how does one new CVE move through a QMSR quality system?

Synthetic example, not a real product. A class II patient monitor runs an embedded Linux image. A new CVE is published for its TLS library.

  1. InputThe vulnerability feed match is logged as quality data (Clause 8.4); a hospital's report of the same issue would also enter complaint handling under 8.2.2 and 820.35(a).
  2. AssessmentThe security risk assessment is updated (Clause 7.1) to decide whether the risk is controlled or uncontrolled.
  3. CAPAA corrective action is opened (Clause 8.5) and linked to the risk record.
  4. Design changeThe library update is a design change (Clause 7.3.9) with verification and software validation (7.3.6, 7.3.7); the SBOM in configuration management is updated.
  5. SupplierIf the library came through a vendor SDK, the purchasing file (7.4) records the supplier's fix.
  6. FieldThe update is released through servicing (7.5.4, 820.35(b)); if it is a correction or removal, part 806 decides whether a report is due.

An investigator following the Change Control and Measurement, Analysis, and Improvement areas would expect to walk this chain from record to record.

How should a device maker start?

  1. Map your procedures to ISO 13485 clauses and 820.10–820.45AAMI TIR102, listed on FDA's QMSR page, maps 21 CFR references to ISO 13485.
  2. Prepare for management review and audit reports to be readWrite them knowing an investigator may ask for them.
  3. Run the comparative analysis FDA suggestsfor records created under the old QS regulation.
  4. Check class I software devices"Devices automated with computer software" need full design controls.
  5. Put cybersecurity into the clauses, not a side fileSecurity risk assessment, SBOM, supplier controls and CAPA belong in the same QMS an inspector walks.
  6. Re-train on CP 7382.850Internal audits structured around QSIT's subsystems should be re-cut into QMS Areas and OAFRs.
  7. Check open submissions with FDAThe sources here do not address submission-specific transition questions; use FDA's QMSR FAQ contacts.

Does AI play any role in a QMSR-era design and development file?

Only in a narrow evidence step. The QMS records themselves (design reviews, CAPA, complaint files) are written and approved by the manufacturer's people. SoftWSP extracts a CycloneDX SBOM from a firmware image, matches the components it identifies against NVD, CISA KEV, FIRST EPSS and CISA CSAF advisories, and uses AI to draft a plain-language finding for each match, citing the component, version and advisory, for an engineer to review. That output can feed the configuration management and risk records above; it does not satisfy ISO 13485 or the FD&C Act on its own. For the SBOM itself, see the firmware SBOM guide.

SoftWSP's device and firmware security work supplies the SBOM and vulnerability evidence that feeds both the QMSR records and an FDA cybersecurity submission: see Device & Firmware Security.

This guide draws on the QMSR final rule (89 FR 7496), FDA's QMSR overview and FAQ pages, Compliance Program 7382.850 and FDA's 3 February 2026 cybersecurity guidance, as read on 12 November 2026. It is not a substitute for the regulation, FDA guidance or regulatory advice.

Put this guide to work

Frequently asked questions

What is the QMSR, and when did it take effect?

The Quality Management System Regulation (QMSR) is FDA's final rule amending the device current good manufacturing practice (CGMP) requirements of 21 CFR Part 820, titled "Medical Devices; Quality System Regulation Amendments." Per the Federal Register record (cited the same way in FDA's QMSR FAQ), the rule was published on February 2, 2024, at 89 FR 7496, and became effective — meaning manufacturers had to be in compliance — on February 2, 2026, after a two-year transition period. The regulation number itself didn't change (it's still Part 820); what changed is most of its substance.

Did FDA just replace Part 820 with ISO 13485? What does it actually require now?

Not quite. FDA's QMSR page states the rule "incorporat[es] by reference" ISO 13485:2016 ("Medical devices — Quality management systems — Requirements for regulatory purposes") along with Clause 3 (definitions) of ISO 9000:2015, rather than reprinting ISO 13485's text inside Part 820 itself. But FDA did not simply defer to the ISO standard wholesale: per FDA's own QMSR page, "to the extent any clause of ISO 13485 conflicts with any provision of the FD&C Act and its implementing regulations, the FD&C Act and/or its implementing regulations will control." This guide lists the codified FDA additions (820.10, 820.35 and 820.45) but not every interpretation in the rule's preamble — a device manufacturer should work from FDA's own QMSR guidance and the rule's preamble, not assume ISO 13485 conformance alone is sufficient, before finalizing a compliance program.

Do I need to get ISO 13485 certified to comply with QMSR?

No. FDA's QMSR FAQ page is direct on this point (FAQ #13): "The FDA will not require certificates of conformance to ISO 13485 and will not issue certificates of conformance to ISO 13485. A certificate of conformance to ISO 13485 will not exempt a manufacturer from an FDA inspection." The same FAQ distinguishes FDA's own inspection model from third-party certification audits: "FDA inspections assess compliance to FDA regulations and are scheduled based on risk factors. Third-party audits assess conformance to a standard and occur annually based on a three-year plan." A manufacturer can hold ISO 13485 certification for other markets (the EU MDR/IVDR effectively require it) without that certificate substituting for an FDA inspection, and can in principle comply with QMSR without ever being ISO-13485-certified.

What changed for FDA's own inspection process?

Per FDA's QMSR page, the agency discontinued the Quality System Inspection Technique (QSIT) and its associated compliance program documents (7382.845 and 7383.001) that FDA investigators had used under the old Part 820, replacing them starting February 2, 2026 with an updated "Inspection of Medical Device Manufacturers Compliance Program: 7382.850." For a manufacturer, this means the audit checklist and inspection framework an investigator uses changed alongside the underlying regulation — a quality system documented and trained against the old QSIT framework should be re-checked against the new compliance program, not assumed to translate automatically.

Sources

  1. FDA: Quality Management System Regulation (QMSR) — official overview page (Federal Register citation, effective date, ISO standards incorporated, QSIT retirement)
  2. FDA: Quality Management System Regulation — Frequently Asked Questions (FAQ #13 on ISO 13485 certification; inspection-vs-audit distinction)
  3. Federal Register: Medical Devices; Quality System Regulation Amendments, final rule, 89 FR 7496 (February 2, 2024; docket FDA-2021-N-0507)
  4. FDA: Compliance Program 7382.850, Inspection of Medical Device Manufacturers (implementation date February 2, 2026)
  5. FDA: Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (guidance, February 3, 2026)
  6. ISO: ISO 13485:2016 — Medical devices — Quality management systems — Requirements for regulatory purposes (catalogue page)
Was this guide helpful?

In this cluster

FDA QMSR (21 CFR Part 820): the ISO 13485 harmonization, explained