How to Read a Device Master Record

A device master record isn’t the design history file, even though the two get confused constantly. The DHF is the record of how a design decision got made; the DMR is the current, approved recipe a manufacturing line actually builds from. Reading one is a different exercise from reading the other.

In brief

21 CFR § 820.181 requires a device master record for each device type or family, capable of demonstrating that devices are manufactured in accordance with the approved specifications.
The DMR is an index of controlled documents, not a single file — device specifications, production process specifications, quality assurance procedures, packaging and labeling specifications, and installation and servicing procedures, each with its location referenced rather than duplicated.
A DMR only protects a manufacturer if it’s current. A component spec or process instruction that still points to a superseded revision is a mismatch a reviewer or an auditor finds quickly.
The DMR and the design history file inform each other but aren’t interchangeable: the DHF explains why a specification was chosen; the DMR is what the specification currently says. A DHF can be complete while a DMR is wrong, if nobody updated it after the last design change.

What the regulation actually requires

21 CFR § 820.181 doesn’t require the device master record to be one physical document — it requires that the location of each element be documented, so an auditor or reviewer can be pointed to the current, controlled version of each piece: device specifications, including drawings, composition, and component specifications; production process specifications, including the equipment and environment; quality assurance procedures and acceptance criteria; packaging and labeling specifications; and installation, maintenance, and servicing procedures. Reading a DMR for completeness means confirming every one of those categories is represented and points somewhere real, not assuming the index is accurate because it looks organized. That’s a different check than reading a design history file, which is judged on whether the evidentiary chain from input to verified output holds together, not on whether a current specification is correctly indexed.

Why it’s worth reading closely, not just confirming it exists

The failure mode that actually shows up in an inspection isn’t a missing DMR — every manufacturer has one. It’s a DMR that still references a document revision the design history file already superseded, because the change control step that should have updated the DMR reference didn’t happen, or happened in one department’s files and not the other’s. Reading a DMR closely means spot-checking a sample of its referenced documents against what’s actually current in production — the same cross-referencing discipline behind reading a CAPA for whether the fix actually closed the loop, rather than just checking that a form was completed.

Where this goes wrong

Treating the DMR as a single static document

Missing that it’s an index to controlled records living elsewhere, several of which are more likely to drift out of sync than the index itself.

Confusing it with the design history file

Looking for design-rationale evidence in the DMR, or looking for current production specifications in the DHF — the two answer different questions.

Checking that a DMR exists instead of that it’s current

Confirming the index is present without spot-checking whether its referenced revisions match what production is actually using.

A device master record earns its purpose the day someone has to prove what a device was actually supposed to be built to — and that proof is only as good as whether the record was kept current between design changes, not whether it was assembled correctly the first time.

Sources & further reading

21 CFR § 820.181 — Device Master Record ecfr.gov
Regulatory Academy — How to Read a Design History File regulatoryacademy.com
Regulatory Academy — How to Read a CAPA regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.