A design history file is not one document produced at the end of a project. It is a compilation of records showing that planning, design inputs, reviews, verification, validation, transfer, and changes proceeded in a controlled way [1][7]. Medical device product lifecycle management software is often marketed as a way to keep those records connected as work moves between engineering, quality, and regulatory groups [2][3]. The regulatory framework allows firms to contain records directly or by reference, but it requires that the demonstrated path from approved inputs through approved outputs remains recoverable [1][7]. PLM can support that recoverability when its data model matches how a manufacturer actually operates.
What the design history file must show
Under 21 CFR 820.30, each manufacturer must establish and maintain a design history file for each type of device. The file must contain or reference records that demonstrate the design was developed according to the approved design plan and the requirements of the quality system regulation [1][7]. This means the DHF is a container for evidence: the plan itself, approved inputs, reviewed and approved outputs, design review records, verification results, validation results, design transfer evidence, and controlled changes [7].
The FDA inspection guide offers a narrower editorial view of what belongs in the file. Not every record generated during a design project is a design output, and only approved outputs need to be retained in the DHF [4]. That distinction matters when a PLM system stores thousands of working artifacts. A query that returns every drawing, simulation, test log, or comment does not automatically produce a compliant DHF. The file must contain the records that prove conformance, not an undifferentiated project archive [1][4].
Where PLM intersects with design control records
Siemens describes its pre-configured PLM for Medical Devices as a means to manage design data, synchronize the design history file and device master record, and connect design documentation to quality processes [3]. The vendor's design control page describes design file management, template-driven regulatory records, and collaboration between research and development and production as compliance levers [2]. Those claims are promotional and should be read as descriptions of product strategy rather than confirmed audit outcomes for any particular manufacturer.
A PLM record structure can make the DHF's relational nature visible. Inputs can be linked to verification test results; a design change can be tied to the review and approval that preceded implementation; a design review can reference the risk analysis that informed it [1][7][8]. FDA's inspection approach evaluates those connections through a selected project, including whether the design was correctly transferred and whether changes were controlled [4]. PLM is therefore most relevant not as a document warehouse but as a system that preserves the links between activities.
Mapping a PLM object model to design and development records
A focused evaluation can work from the records explicitly named in 21 CFR 820.30 and FDA's design controls guidance: design plan, approved inputs, design outputs with acceptance criteria, design review results, verification results, validation results, transfer evidence, and change control records [1][7][4].
For each record type, determine whether the PLM can capture the item, its approval date and signatory where required, and a durable link to the artifacts that preceded or followed it. FDA guidance describes software documentation elements such as the software requirements specification, the system and software architecture design chart, and the software design specification [5][6]. The practical test is whether those artifacts can be versioned and referenced from the DHF without leaving the controlled environment.
Manufacturers should also confirm what cannot be inferred from the tool. A PLM object link does not by itself establish that acceptance criteria were stated before verification, that validation addressed each intended use under actual or simulated conditions, or that a design review included an independent individual [4][7]. Those are procedural facts that reside in the content of the records, not in the relationships between them.
Software records and synchronization risk
Device software functions raise a specific documentation problem. FDA guidance states that DHF documentation should be synchronized with software development, verification, and validation efforts. Documentation created retrospectively or after a prolonged period can raise concerns about whether a developer has adequate control of the design process [5][6]. This is a regulatory expectation about timing, not a technical feature that any PLM vendor can declare satisfied by default.
The guidance also distinguishes documentation levels. Basic documentation requires a summary description of testing at the unit, integration, and system levels, plus a system-level test protocol and report. Enhanced documentation adds unit and integration test detail [6]. A PLM system can store software requirements specifications, architecture diagrams, and test records, but the guidance does not recommend a specific software life cycle model or development methodology [6]. Manufacturers still choose the lifecycle model and must make the DHF track that choice.
QMSR transition and the ISO 13485 frame
FDA materials now point manufacturers toward the Quality Management System Regulation, which incorporates ISO 13485:2016 by reference [5][8]. FDA has noted that the QMSR does not use certain legacy terms such as design controls and design validation; the corresponding elements are described in ISO 13485 clause 7.3 and its subclauses [5]. For someone managing a medical device PLM implementation, this means the data model must accommodate the clause 7.3 design and development records, including planning, inputs, outputs, review, verification, validation, transfer, and changes [8].
The transition does not erase the DHF requirement. FDA guidance still references 21 CFR 820.30(j) and describes a DHF as a compilation of records describing the design history of a finished device [5][6]. The practical shift is vocabulary and reference points. Teams should avoid assuming that a legacy template labeled under 21 CFR 820.30 headings will map cleanly to ISO 13485 clause numbering without review. Any PLM configuration should reflect the standard the manufacturer is actually audited against.
A concrete evaluation example: infusion pump software update
Consider a manufacturer evaluating whether a PLM configuration can support DHF records for a software update to an infusion pump. The approved design plan includes a scheduled design review, software verification using unit and integration tests, and validation under simulated use on production-equivalent units. The PLM should be able to show the plan, the set of approved software inputs, the software design specification that traces to those inputs, and the dated test records with identified performers [1][5][7].
Reviewers can then inspect links rather than search across disconnected file shares: each input requirement points to a test case, each change request points to a documented review and approval, and each output points to the reviewer signature and date [1][7]. This is a suggested demonstration, not a test that proves regulatory compliance. It shows whether the tool can reconstruct the causal sequence FDA describes from design input through design output, verification, validation, transfer, and change control [1][4][7].
Sources & references
- eCFR :: 21 CFR 820.30 -- Design controls. · www.ecfr.gov
- Design Control | Quality Management | MedDev Compliance | Siemens · www.siemens.com
- PLM for Medical Devices | Siemens · www.siemens.com
- Design Controls | FDA · www.fda.gov
- Content of Premarket Submissions for Device Software Functions — Guidance for Industry and FDA Staff (June 14, 2023) · www.fda.gov
- Content of Premarket Submissions for Device Software Functions · www.fda.gov
- 21 CFR 820.30 - Design controls. · www.govinfo.gov
- QMSR Design and Development · www.fda.gov