The medical-device quality system (21 CFR 820 / QMSR) and the 510(k)

FDA’s QMSR explanation states that the Quality Management System Regulation became effective on February 2, 2026. The rule amends the device CGMP requirements of Part 820 and incorporates ISO 13485:2016 by reference. FDA describes this as alignment of its device quality-management framework with internationally recognised requirements.

The current 21 CFR Part 820 is therefore the QMSR. Older references to the Quality System Regulation may be encountered in technical material, but they should not be used as though their former section structure were the current rule. A practical document review checks which requirements an internal procedure actually addresses, rather than changing only its heading or abbreviation.

Part 820 describes controls for design, manufacture, packaging, labeling, storage, installation and servicing of finished devices intended for human use. It requires a manufacturer to establish and maintain a quality management system appropriate to its devices and applicable operations. This scope follows the activities performed; it is broader than the inspection of a finished item.

A practical system map can connect each activity to its responsible function, approved instruction and evidence. For example, a labeling change may begin in engineering or regulatory work but affect production instructions and packaging checks. A storage requirement may need to remain clear through manufacturing and distribution. Following these connections exposes gaps between departments that separate document lists may miss. The map helps staff understand the system without deciding a particular device’s regulatory status.

The QMSR requires documentation of a quality management system that complies with applicable ISO 13485 requirements and the other applicable requirements of Part 820. FDA also explains that the law and its implementing regulations control if an ISO clause conflicts with them. ISO alignment does not remove the need to examine FDA-specific obligations.

For quality staff, a useful cross-reference identifies where each applicable requirement is addressed and what evidence supports it. The cross-reference should point to actual practices, not merely to a procedure with a similar title. FDA describes the incorporated framework as promoting consistency across design, production and lifecycle controls and specifically requiring risk management. A company’s assessment needs to show how its controls fit the operation and remain connected as it changes.

Current Part 820 identifies design and development requirements for Class II, Class III and specified Class I devices through the incorporated ISO framework. The exact applicability depends on the regulation. This is a general explanation of that structure, not a determination for a particular device.

In practical terms, development evidence and manufacturing instructions need to describe a consistent design. A drawing change can affect component specifications, acceptance checks and production methods. Staff reviewing the change commonly examine those dependencies before implementation. Evidence should make clear what was changed, why the change was made and how the resulting requirements reached the point of use. A change that exists only in a design file can leave production working to a conflicting instruction.

Part 820 includes supplemental provisions for records and for device labeling and packaging. Its records provisions address complaint review, evaluation and investigation, servicing information and device identification. Its labeling provisions address documented procedures, examination for accuracy and prevention of mix-ups. These subjects need evidence from the actual activity, not only a policy statement.

A general labeling check might connect the approved labeling content, the material used on the line and the documented release decision. A complaint review might connect the reported issue with the investigation and the action taken. In either case, ambiguity about the device or batch weakens the evidence trail. The aim is a record that explains the event and its handling. The quality-system page develops this connection between activity, responsibility and review.

FDA’s premarket-notification explanation describes a 510(k) as a submission demonstrating substantial equivalence to a legally marketed device. It involves comparison with a predicate and support for the equivalence claim. The agency’s account makes clear that substantial equivalence does not require the devices to be identical.

The submission question and the continuing quality-system question are distinct. FDA notes that it does not typically perform a facility inspection before 510(k) clearance and that a manufacturer should be prepared for a quality-system inspection afterward. Clearance should therefore not be interpreted as evidence that every manufacturing control has been inspected. The company still needs to maintain the applicable quality system and the evidence supporting its operations.

FDA’s premarket explanation says that some changes to a device or its intended use can require a new submission. It also describes the role of change-control records in documenting the assessment. The decision depends on the actual change and applicable requirements; this page cannot determine it for a particular device.

A practical change process brings quality, engineering and regulatory perspectives together early. Review what the proposed change affects, which evidence must be updated and which manufacturing controls need adjustment. Confirm that the implemented configuration remains consistent across specifications, instructions, labeling and the supporting regulatory record. The classification page explains how device classes shape regulatory controls. Classification, premarket review and the quality system are connected decisions, while each retains its own purpose.