Medical Device Design Controls: FDA QMSR §820.30 and ISO 13485 §7.3 Requirements

What Design Controls Are and Why They Matter

Design controls are the set of quality system requirements that govern how medical devices are designed and developed. They exist for one reason: to ensure that the device that reaches patients actually works as intended and does not cause harm.

FDA introduced design controls under 21 CFR Part 820 in 1996, recognizing that the vast majority of device recalls and adverse events trace back to design failures rather than manufacturing failures. A device manufactured perfectly to a flawed specification is still a dangerous device. Design controls close that gap by requiring manufacturers to define what the device must do, verify that the design achieves those requirements, validate that the design actually meets user needs, and document the entire process in a Design History File.

The QMSR, which becomes fully effective February 2, 2027, retains design control requirements and aligns them with ISO 13485:2016 §7.3. The terminology has shifted slightly, but the underlying obligations are as rigorous as ever. Design controls remain one of the top sources of FDA 483 observations year after year — which means getting this right is not optional.

Design Inputs vs. Design Outputs: Getting the Distinction Right

The most fundamental concept in design controls is the distinction between design inputs and design outputs. Confusing the two is a common error that creates traceability gaps auditors will find.

Design inputs are the physical and performance requirements of the device. They describe what the device must do. Inputs come from user needs, intended use, applicable standards, regulatory requirements, and risk management outputs. A design input might be a specific biocompatibility requirement, a performance specification for measurement accuracy, a dimensional requirement driven by the intended anatomical site, or a reliability requirement based on expected device lifetime.

Design inputs must be documented, reviewed, and approved before design work begins. They form the specification baseline against which the design will be verified. Incomplete or ambiguous design inputs are one of the most common 483 observation findings.

Design outputs are the results of the design process: drawings, specifications, software code, manufacturing procedures, material specifications, and labeling. Design outputs must address each design input. The link between inputs and outputs must be traceable — for every input, you must be able to identify the output that satisfies it.

ISO 13485 §7.3.4 and QMSR requirements both require that design outputs be documented in a form that enables verification against design inputs. That documentation is the foundation of your DHF.

Verification and Validation: Two Different Activities

Design verification and design validation are consistently conflated, and that confusion leads to both 483 observations and, more dangerously, devices that do not actually work for users.

Design verification answers the question: Did we build the design right? It tests whether design outputs meet design inputs. Verification is done against the specification. It can be done on prototypes, benchtop models, or final designs using analysis, inspection, or testing. A verification test might confirm that a device achieves its stated measurement accuracy specification under defined test conditions.

Design validation answers the question: Did we build the right design? It tests whether the final device meets user needs and intended use. Validation must be done using final or representative production-equivalent devices under actual or simulated use conditions. A validation might confirm that actual users can operate the device correctly, that the device performs as expected in the clinical environment, or that the device meets the needs of the intended patient population.

The critical distinction: verification tests against the spec; validation tests against the user need. A device can pass all verification testing and still fail validation if the specifications were wrong. Both are required. Both must be planned, executed, and documented before design transfer.

DHF Structure: What Goes in the Design History File

The Design History File is the collection of records that demonstrates your design was developed in accordance with your design control procedures. It is not a single document — it is a file, typically organized by project or device, that contains the records generated throughout the design process.

A complete DHF typically includes the design and development plan, user needs documentation, design inputs (specifications), design review records for each design stage, design outputs (drawings, specifications, software documentation), design verification protocols and reports, design validation protocols and reports, risk management records (per ISO 14971), design change records, and design transfer documentation.

FDA investigators reviewing a DHF want to trace a clear thread from user need to design input to design output to verification to validation. If that thread breaks anywhere, you will receive a 483 observation. Auditors also look for evidence that design reviews were conducted with appropriate cross-functional participation and that action items from design reviews were resolved before proceeding to the next stage.

The DHF must be complete enough that someone who was not involved in the design process could review it and understand what decisions were made, why, and on what evidence.

Design Transfer: Moving from Design to Production

Design transfer is the process of ensuring that the device design is correctly translated into production specifications and that production processes can consistently produce a device that meets the design. It is the bridge between design and manufacturing, and gaps here are a predictable source of 483 observations.

A design transfer plan should identify what must be transferred (drawings, manufacturing procedures, inspection specifications, software builds, test methods), who is responsible for each transfer activity, what verification is required to confirm the transfer is complete, and what records will document the transfer.

Design transfer verification typically includes confirming that production equipment can manufacture devices to specification, that manufacturing personnel understand and can follow the production procedures, that incoming inspection and in-process inspection specifications are complete and implemented, and that the first production devices meet all design requirements.

The design transfer is not complete until the production process has been validated — either through process validation or through confirmation that production devices meet all design inputs. Transfers that occur informally, without documentation, create DHF gaps that are very difficult to remediate after the fact.

Common FDA 483 Observations for Design Controls

Design controls consistently generate among the highest volume of 483 observations of any quality system area. Here are the findings that appear most frequently:

Incomplete design inputs. Design inputs that are vague, untestable, or do not address applicable regulatory requirements. Inputs must be specific enough to be verified. "The device shall be reliable" is not a design input. "The device shall have a mean time to failure of no less than 5,000 hours under normal use conditions" is a design input.

Missing traceability between inputs and outputs. Manufacturers often have inputs and outputs but cannot demonstrate the link. A traceability matrix showing input-to-output and input-to-verification/validation mapping is the standard way to demonstrate this connection.

Validation conducted before design freeze. Design validation must use final devices or devices that are production-equivalent. Validation conducted on prototypes that differed from the final design must be repeated, or the differences must be justified as not affecting the validation conclusions.

Design reviews without documented action item resolution. Design reviews that identify action items but do not track resolution create open questions in the DHF. Every action item from a design review must be documented as closed before design transfer.

Design changes without formal change control. Changes made during development that were not processed through your design change procedure result in a DHF that does not reflect the actual design. Every change that affects design inputs, outputs, verification, or validation must go through change control.

Inadequate design transfer records. Design transfer that is not fully documented leaves gaps between the DHF and the Device Master Record (DMR). The transfer must be documented with evidence that production processes can consistently produce conforming devices.

The Design Controls Toolkit at design-controls-toolkit.vercel.app provides six practitioner-grade templates that address each of these gaps: a Design Control Plan, Design Input Requirements template, V&V Protocol, DHF Checklist, Design Review Template, and Design Transfer SOP. Each template is built to satisfy both QMSR §820.30 and ISO 13485 §7.3 requirements.

If your current design control documentation would not survive an FDA inspection, get the toolkit at design-controls-toolkit.vercel.app.