What Is a Device Master Record (DMR)? Definition and FDA Requirements

Every medical device cleared for the U.S. market depends on one collection of documents that tells a manufacturer exactly how to produce it. When that collection is complete and traceable back to the validated design, production runs smoothly and inspections go quickly. When it isn’t, Food and Drug Administration (FDA) investigators notice.

Failure to maintain Device Master Records (DMRs) is one of the most common findings in FDA warning letters. This guide covers the DMR definition, how it relates to other FDA record types, what the FDA and ISO 13485 require, and where teams most commonly fall short.

What Is a Device Master Record (DMR)?

A Device Master Record (DMR) is a collection of documents that describe the procedures and specifications for a finished device. Manufacturers must maintain a DMR for each type of device they produce, per 21 CFR 820.181. The DMR must be reviewed and approved before production begins.

The DMR sets the bar for what counts as an acceptable unit. It is sometimes compared to a recipe and needs to be detailed enough that a qualified team at any facility, given the same materials and equipment, could reproduce the device to spec. That level of detail is what makes the DMR a foundation of requirements management for medical device teams.

How the DMR Relates to the DHF and DHR

The DMR is one of three FDA record types that work together. The Design History File (DHF) captures how the device was designed, what inputs shaped it, and the evidence that the design met its requirements. The DMR documents how to manufacture it. A drawing from the DHF becomes a DMR element only when it’s paired with specifications and production methods.

The Device History Record (DHR) is the production log for each batch, lot, or unit. It proves that a specific run was actually built according to the DMR. The DMR says “build it this way,” and the DHR proves “we built it that way.”

What the FDA Requires in a Device Master Record

The regulation (21 CFR 820.181) breaks the DMR into five categories. The phrase “include or refer to” gives you flexibility in how you organize the DMR physically, but every element must be present and retrievable under document control.

Device Specifications

The first category covers drawings, composition, formulation, component specs, and software specs. For devices with embedded software, the software documentation tends to get the most scrutiny during an FDA inspection.

Production Process Specifications

The second category covers equipment specs, production methods, production procedures, and environment specs. These documents need to be detailed enough for a qualified person to reproduce the device at any facility with the right resources.

Environment specs matter most for devices where cleanroom class, temperature, or humidity affects product quality. Inspectors check that actual production conditions match what the DMR says they should be.

Quality Assurance Procedures and Specifications

The third category requires acceptance criteria and the quality assurance equipment used to verify them. Acceptance criteria must be specific and testable. The FDA has cited manufacturers whose DMRs lacked complete acceptance criteria, treating that gap as a failure to define the quality standard production results are measured against.

Packaging and Labeling Specifications

The fourth category covers packaging and labeling specs, including the methods, materials, and in-process controls. Your labeling specs must account for every label type applied to the device. In-process controls for labeling, like label reconciliation and inspection steps, also need to be documented.

Installation, Maintenance, and Servicing Procedures

The fifth category requires procedures for installation, maintenance, and servicing. These tie directly to servicing record requirements (21 CFR 820.200). If a serviced device malfunctions and the service record can’t be traced back to the current DMR procedures, investigators treat the disconnect as a gap in both the DMR and the quality system.

How ISO 13485 Handles DMR Documentation

ISO 13485 doesn’t use the term “Device Master Record.” Instead, it requires a Medical Device File for each device type or family. This file contains or references documents that show the device meets the standard and any applicable regulatory requirements.

How the Medical Device File Differs From the FDA’s DMR

The Medical Device File is broader than the DMR. The FDA historically split device documentation into three separate record types. The DHF, DMR, and DHR each covered a different phase of the product lifecycle. ISO 13485 rolls all of that into a single concept organized by device type or family.

Aligning Your DMR for Both U.S. and International Markets

The FDA’s Quality Management System Regulation (QMSR) took effect on February 2, 2026, and brought FDA terminology in line with ISO 13485:2016. That includes adopting the Medical Device File concept. The QMSR retired the DMR, DHF, and DHR as named regulatory terms, but the documentation obligations behind them still apply under the incorporated ISO 13485 clauses.

If you sell into both U.S. and international markets, organizing your documentation around the Medical Device File makes dual compliance simpler. Internal cross-references to legacy DMR, DHF, and DHR categories help teams keep backward compatibility with existing records.

How to Build and Maintain a Compliant DMR

Three practices separate teams that pass FDA inspections from those that receive 483 observations for DMR deficiencies.

Set Up Document Control Before You Start Drafting

You need a document control system in place before you can have a compliant DMR. Any documents created before that system is approved are noncompliant from the moment they’re written.

Before you draft any DMR content, your quality system needs an approved Document Control Standard Operating Procedure (SOP) that covers:

• Document identification: Unique numbering conventions for all controlled documents.
• Approval authority: Defined approvers for each document type before release.
• Distribution controls: Controlled copies available at all designated use locations.
• Obsolescence procedures: Quick removal of outdated versions so no one uses them by mistake.
• Retention periods: Records kept for the expected life of the device, with a minimum of two years from commercial distribution.

The document control SOP also sets up the approval workflow that gives DMR documents their regulatory standing. That’s why FDA investigators typically ask to see your SOP before they look at the DMR itself.

Connect Each DMR Element Back to the Validated Design

Design transfer is where design requirements become production specs, and where you verify that the production version still matches the original design inputs (per 21 CFR 820.30(h)). Each DHF design output should have a corresponding DMR element:

• Device specifications: DHF design outputs become approved engineering drawings with manufacturing work instructions.
• Acceptance criteria: Design verification criteria become inspection and test procedures.
• Packaging specifications: Design packaging specs become controlled labeling and packaging documents.

A traceability matrix that maps DHF design outputs to DMR sections gives you a way to verify nothing was lost in translation. Auditors use it to confirm that the device being manufactured matches the validated design.

Keep the DMR Updated Through Change Control

A Device Master Record isn’t static once a device reaches production. Design changes fall under 21 CFR 820.30(i), and manufacturing process changes fall under 820.70. If you determine that a modification doesn’t require a new 510(k), that decision and its rationale should be documented alongside the change record.

Common DMR Compliance Failures

FDA warning letters and 483 observations show three recurring DMR deficiency patterns.

Missing or Incomplete Software Specifications

The FDA can cite missing software specs on a 483 observation. If your device contains software, the DMR must include or reference the software specifications. Teams that treat software documentation as secondary to hardware specs risk a standalone finding during inspection.

Records That Can’t Be Found During Inspection

A DMR that exists but can’t be found during inspection is treated the same as having no DMR at all. In one case, a quality manager couldn’t produce the DMR during an FDA visit. The agency had flagged the same problem at that firm five years earlier.

In another case, a manufacturer handed over a DMR for a model that was never manufactured or shipped to the U.S. market. The FDA treated it the same as having no DMR.

DMR Documents Not Updated After Design Changes

When DMR specs no longer match what’s actually being manufactured, you’ll get cited. One firm’s DMR contained specifications that didn’t match what the contract manufacturer was using. The FDA also cited the firm for lacking design change procedures (820.30(i)), directly tying the outdated DMR content to missing change control.

How Requirements Management Supports DMR Compliance

DMR compliance depends on the same traceability setup that supports design controls. Without it, changes that affect requirements and DMR content pass through manual handoffs, and those handoffs create the kind of gaps auditors are trained to find.

Trace Requirements to DMR Content

Complete DMR documentation comes from a clear chain. User needs flow into design inputs, which flow into design outputs. ISO 14971 adds a risk layer, linking hazards to risk controls, their implementation, and proof that they work. Auditors follow this chain from either end, so every link needs to hold up.

Keep Records Audit-Ready as the Product Evolves

When a requirement changes after design transfer, the update needs to reach every connected DMR element. A change to device specifications can affect your quality assurance procedures and your production process specs. A traceability matrix shows those connections between requirements, risk items, verification and validation activities, and DMR content.

How Jama Connect Supports DMR Compliance

Jama Connect® is a requirements management platform with a pre-built framework for medical device teams, aligned to ISO 13485 and FDA design control requirements. Design controls, risk items, verification records, and DMR documentation all connect in one system. When a requirement changes, every linked DMR element gets flagged for review. Teams can trace any specification back to the validated design it came from and see the full chain from user need through production spec in one view.

That traceability is especially useful during design transfer, when DHF outputs need to map cleanly to DMR elements. Instead of reconciling versions across disconnected spreadsheets and file shares, teams can verify the connection between each design output and its corresponding manufacturing spec in the same place. When an FDA inspector asks to walk that chain, the evidence is already assembled and current.

Keeping Your DMR Current Through Every Design Change

DMR compliance failures usually start when it’s too hard to keep documentation current as designs evolve and production methods change. The QMSR’s alignment with ISO 13485 simplifies dual compliance, but it doesn’t solve the core challenge of maintaining a traceable chain from validated design all the way through manufacturing specs. When requirements, risk items, and DMR content live in one connected system, you can see the downstream impact of a change before it creates a compliance gap. Start a free trial of Jama Connect to see how your team can produce audit-ready documentation from live project data.

Frequently Asked Questions About Device Master Records (DMR)

What is the difference between a device master record and a design history file?

During an FDA inspection, auditors treat the DMR and DHF as two ends of the same chain. They’ll pull a requirement from the DHF and ask to see the matching manufacturing spec in the DMR. The DHF proves the design was developed correctly based on verified inputs. The DMR proves the manufacturing process reproduces that validated design in every production run. Keeping those links current is where tools like Jama Connect help, since both record types trace back to the same design inputs.

What records must be included in a device master record?

The regulation (21 CFR 820.181) lists five categories, but the “include or refer to” language means your DMR can work as a controlled index that points to documents stored elsewhere in the quality system. The common mistake is treating the five categories as a checklist of document titles instead of minimum content requirements that must be filled in with current, approved specs.

How long must a device master record be retained?

You must keep DMR records for the expected life of the device, with a minimum of two years from the date of commercial distribution. If you sell in the EU, you may face longer retention requirements under applicable regulations.

Does ISO 13485 require a device master record?

ISO 13485 doesn’t use the term “device master record,” but it requires a Medical Device File for each device type or family. Since the QMSR took effect on February 2, 2026, the FDA has aligned with ISO 13485:2016, and the legacy DMR is now treated as the equivalent of the Medical Device File. The terminology changed, but the documentation obligations are the same.