
The picture
ISO 13485:2016, third edition, published March 2016 by ISO Technical Committee 210, is the quality-management standard the FDA's 2026 Quality Management System Regulation incorporates by reference for US medical devices. ISO's own listing describes it as the standard for organizations involved in the design, production, installation and servicing of medical devices, built around demonstrating a device consistently meets customer and regulatory requirements. It is a living document, current as retrieved 16 September 2026, at edition 3.
What the documents show
ISO's page gives the standard's scope and 2016-03 publication date but, as a catalogue listing, not its clause numbering. The FDA's own QMSR page fills that gap: it names ISO 13485's Design and Development requirements, Clause 7 and its subclauses, as governing design records, and confirms devices under an investigational device exemption remain subject to 21 CFR 820.10(c) and that same Clause 7. Neither document uses the phrase "design history file." That is deliberate: the Federal Register's QMSR final rule records FDA's decision to eliminate the design-history-file, device-master-record and device-history-record terminology because none appear in ISO 13485, folding equivalent content into the standard's own medical device file instead.
What it is allowed to decide
The sources establish a documentation requirement, not a ruling on any company's compliance or any artifact's fidelity. Editorially: a digital prototype used for a Clause 7 design review can be expected to sit inside a traceable record if the manufacturer's own quality system designates it as such — a Provenance and Auditability claim, since the standard requires the record's origin and version history to be controlled. The standard does not, on its own text as retrieved, establish Physical authority; it says nothing about whether a simulation behaves like the physical device. Whether any prototype counts as a controlled record depends on the manufacturer's internal QMS, which these sources do not describe company by company.
The disclosure label
A prototype held under this clause could carry a label reading: this model was produced under a design-and-development process governed by ISO 13485:2016 Clause 7, current as retrieved 16 September 2026; it holds Auditability, being version-controlled within the manufacturer's medical device file; it does not hold Physical authority, since no cited document states the model was validated against real material or mechanical behavior. A quality-assurance lead would plausibly assert this label.
- Does the manufacturer's own quality manual designate this specific prototype as a Clause 7 record, or is it an informal working file?
- Is the retired "design history file" language still used internally in a way that could misstate what the current regulation actually requires?
- What separate evidence, if any, establishes that the model behaves physically like the finished device, since Clause 7 alone does not supply it?
The standard sets an expectation for traceable records, not a fidelity guarantee. Treating it as the latter would overstate what a quality-management clause can tell a reader about any single picture.
Sources & reading trail
ISO's own catalogue page gives the standard's title, scope description, edition (3) and March 2016 publication date.
Source published: 1 March 2016 · Retrieved: 16 September 2026
FDA's page names ISO 13485's Design and Development Clause 7 and 21 CFR 820.10(c) as the governing design-record requirements under the QMSR.
Source published: Not established · Retrieved: 16 September 2026
The final rule's comment-response record states FDA eliminated the design-history-file, device-master-record and device-history-record terminology because it does not appear in ISO 13485.
Source published: 2 February 2024 · Retrieved: 16 September 2026
Documentation, handbooks, rulings and records establish the entry; the authority reading and the disclosure label are Previs Office editorial analysis. This retrospective draft does not imply the site published on the event date.