Glossary Updates16 new terms added to the glossaries · November 12, 2026, 21:23 CET
AI TechDocKnowledge

Glossary · USA: FDA device and drug rules

Design controls (medical devices)

Also known as: Design controls, Design and development controls, Design control

Design controls are the planned, documented controls over the design and development of a medical device: planning, inputs, outputs, review, verification, validation, transfer to production and the control of design changes. In the USA they are required by the FDA's Quality Management System Regulation (21 CFR Part 820) through ISO 13485:2016 clause 7.3; in the EU the same clause applies through the manufacturer's quality management system.

  • USA
  • Standards
  • Technical documentation

In one sentence

Design controls: planned, documented control of device design from inputs to transfer and changes (ISO 13485 7.3, FDA QMSR 21 CFR Part 820).

Example

For a new glucose meter, the design input “measures within ±15 % of the reference method” is traced to the design output (algorithm and strip specification), to the verification study, and to the validation with lay users; a later change of the strip chemistry goes through design change control.

Explained in context

This term is a station of a mini course

  • The medical-device evidence chain: from intended purpose to post-market evidenceStation: GSPR and requirements traceability · Design controls and design historyStart the course

Context cards connect this term with others to answer one question. Also in British English and German.

How it applies

  • From QSR to QMSR: Until February 1, 2026, design controls were set out in 21 CFR 820.30 of the Quality System Regulation. Since February 2, 2026, the QMSR incorporates ISO 13485:2016 by reference, and the design control requirements are those of clause 7.3. The substance continues; the clause numbers and some terms change.
  • The chain they create: Inputs are traced to outputs, outputs are verified against inputs, and the device is validated against user needs and the intended use. That chain is the backbone of requirements traceability in a device file.
  • Changes: Design changes are reviewed, verified and validated as appropriate, and their effect on parts already delivered is assessed (ISO 13485 7.3.9).
  • Technical documentation: IFU and labeling are design outputs. Put them under the same design change control as the hardware and software, and record which design input each instruction or warning serves.

Design verification vs. design validation

Verification shows that design outputs meet design inputs ("did we build it right?"); validation shows that the device meets user needs and its intended use under actual or simulated use conditions ("did we build the right device?"). A test report can't serve both unless it was planned for both.

External references