Webinar: From Paper to eIFU: Preparing for the Next Global Step in Medical Device Compliance

Register now

Device Master Record (DMR): What It Contains and Why It Matters

A Device Master Record (DMR) is the core compilation of records containing all information required to manufacture a medical device in compliance with regulatory requirements. Under the FDA’s Quality System Regulation (QSR), codified at 21 CFR 820.181, every medical device company must establish and maintain a Device Master Record for each device type. Note: the FDA published a revised Quality Management System Regulation (QMSR), effective February 2, 2026, which aligns 21 CFR Part 820 more closely with ISO 13485:2016; references to QSR section numbers throughout this article reflect the prior regulation. The DMR serves as the single source of truth for manufacturing specifications, quality procedures, and design requirements—making it critical for regulatory compliance, manufacturing consistency, and product traceability.

What Is a Device Master Record?

The Device Master Record is a comprehensive collection of documents that defines exactly how a device is designed, manufactured, tested, and released for distribution. It functions as the blueprint for all production activities and provides the documented evidence that manufacturing processes are controlled and validated. The DMR is not a single document but rather a compilation—often organized in an indexed file or digital repository—that ties design specifications, manufacturing procedures, quality standards, and regulatory requirements into one traceable system.

FDA inspectors routinely examine the DMR during facility audits to verify that the manufacturer has documented all necessary design and manufacturing information. A well-organized, complete DMR demonstrates that the company has systematic control over its processes and can quickly demonstrate compliance during inspections. Conversely, incomplete or disorganized DMRs are among the most frequently cited deficiencies in FDA warning letters and inspection reports.

What Does the Device Master Record Contain?

The contents of a DMR vary depending on the device complexity, manufacturing method, and regulatory requirements, but 21 CFR 820.181 specifies the minimum information that must be included. The DMR must contain or reference sufficient information to ensure that the device can be manufactured consistently and meet all applicable acceptance criteria.

Device and Component Specifications

The DMR must include complete specifications for all materials, components, and finished devices. This includes material properties, supplier qualification records, component acceptance criteria, and any substitution rules or equivalency assessments. The device specification section defines the physical, chemical, electrical, or biological properties that the finished device must meet, with references to technical drawings, schematics, software specifications, and approved revisions.

Production Process Specifications

Manufacturing procedures and process specifications must be clearly documented and referenced in the DMR. This includes step-by-step procedures for assembly, processing, and testing; environmental controls required during manufacturing; equipment specifications and calibration requirements; and critical process parameters with documented rationale for acceptable ranges. The DMR must also reference instructions for installation, maintenance, and servicing if the manufacturer is responsible for these activities.

Quality Assurance Procedures and Acceptance Criteria

All quality procedures referenced in the DMR must define how devices are tested, inspected, and released. This includes incoming inspection criteria for components, in-process inspection points, finished device acceptance criteria, and corrective action procedures. The acceptance criteria must be measurable, objective, and linked to device specifications and risk-based requirements.

Packaging and Labeling Specifications

The DMR must contain or reference all packaging and labeling requirements, including artwork approval, label specifications, packaging materials, sterility or shelf-life requirements, and storage conditions. This section ensures that every device distributed has the correct, approved labeling and is properly protected during distribution.

Installation, Maintenance, and Servicing Procedures

If applicable, the DMR must include procedures and instructions for installation, maintenance, and servicing. This is particularly important for implantable devices, diagnostic systems, and devices that require specialized field service or calibration. These procedures must align with the design specifications and risk controls established during design development.

Device Master Record vs. Design History File: Understanding the Difference

The DMR and the Design History File (DHF) are often confused, but they serve distinct purposes. The Design History File, defined in 21 CFR 820.184, is a compilation of records containing the procedures and activities related to the design and development of a device. The DHF documents the design process, design changes, design validation, and the rationale behind design decisions. It is primarily used to demonstrate that the design was properly controlled and validated, and it is typically maintained by the design and development team.

The DMR, by contrast, is focused on manufacturing and production. It contains the current, approved specifications and procedures that manufacturing must follow to produce the device consistently. While the DHF preserves the historical record of how the design evolved, the DMR is the working document used daily on the manufacturing floor. Think of it this way: the DHF answers the question 'How did we develop this design?' while the DMR answers 'How do we manufacture this device?'

In practice, some documents may be referenced in both the DHF and DMR. For example, design specifications and risk assessments developed during design may be referenced in the DMR to justify manufacturing parameters. The key is that both files must be organized, indexed, and maintained with appropriate version control and change management procedures.

Device Master Record Under ISO 13485: International Considerations

ISO 13485, the international standard for medical device quality management systems, requires similar documentation to that mandated by FDA regulations. ISO 13485:2016 section 7.3 (Design and Development) requires organizations to plan, control, and document all design and development activities; the design and development file requirement is specifically in section 7.3.10. While the regulatory language differs slightly from FDA regulations, the requirement is functionally equivalent: manufacturers must maintain a complete record of device specifications and manufacturing procedures.

Manufacturers seeking to comply with both FDA and ISO 13485 requirements should note that FDA regulations are prescriptive—specifically requiring a Device Master Record—while ISO 13485 describes requirements functionally but does not mandate a specific document structure. This means that a DMR compliant with FDA regulations will typically exceed ISO 13485 requirements, so designing the DMR to meet FDA standards generally ensures international regulatory compliance.

Keeping Your DMR Current: Version Control and Change Management

A critical and often overlooked aspect of DMR maintenance is version control and change management. The DMR must always reflect the current, approved manufacturing process. When a design change, process improvement, or procedure update occurs, the affected DMR documents must be updated, reviewed, and approved before implementation. This requires a formal change control procedure that ties together design changes, regulatory implications, manufacturing updates, and quality system documentation.

Every change to DMR documents should be traceable, with clear revision history showing what changed, why, when, and who approved it. This is critical for regulatory inspections and for investigating device failures or adverse events. Devices manufactured under different DMR versions must be clearly identified and tracked for traceability purposes.

  • Establish a formal change control procedure that includes impact assessment and regulatory review

  • Maintain revision control with dated approvals and clear identification of changes

  • Track which device lots were manufactured under which DMR versions

  • Ensure that obsolete DMR versions are archived but retained for traceability

  • Implement a system to communicate DMR changes to all affected personnel

Common DMR Mistakes and How to Avoid Them

Incomplete or missing information is the most common DMR deficiency. Many manufacturers document their processes informally or rely on tribal knowledge rather than written specifications. This creates risk during inspections and makes it difficult to maintain consistency when personnel change. Every manufacturing procedure, acceptance criterion, and specification must be formally documented and indexed in the DMR.

Another frequent problem is inadequate linkage between the design specification and the manufacturing procedure. If the DMR references a design spec but does not explain how manufacturing ensures that the product meets that spec, there is a gap. The DMR should clearly trace how each design requirement is translated into manufacturing controls and acceptance criteria.

  • Missing or incomplete specifications for critical materials, components, or manufacturing parameters

  • Outdated procedures that do not reflect current manufacturing practices or design changes

  • Poor indexing or organization making it difficult for inspectors or operators to locate required information

  • Lack of clear approval and version control, with unclear which version is current

  • Failure to maintain traceability between design specifications and manufacturing controls

💡  Best practice: Establish a single, centralized repository for your DMR documents with role-based access control, change tracking, and audit trails. This ensures that all stakeholders access the current version and provides clear evidence of controlled management during inspections.

The challenge
How Matrix Req Helps

Request a demo and get started today.

The most trusted Software Platform for Design Control & Cloud Connectivity. Access to all features and no credit card required.

Request A Demo Today
DE
USUnited States
GBUnited Kingdom
FRFrance
AUAustralia
DEGermany
ESSpain
AFAfghanistan
ALAlbania
DZAlgeria
ASAmerican Samoa
ADAndorra
AOAngola
AIAnguilla
AGAntigua and Barbuda
ARArgentina
AMArmenia
AWAruba
ATAustria
AZAzerbaijan
BSBahamas
BHBahrain
BDBangladesh
BBBarbados
BYBelarus
BEBelgium
BZBelize
BJBenin
BMBermuda
BTBhutan
BOBolivia
BABosnia and Herzegovina
BWBotswana
BRBrazil
IOBritish Indian Ocean Territory
VGBritish Virgin Islands
BNBrunei Darussalam
BGBulgaria
BFBurkina Faso
BIBurundi
KHCambodia
CMCameroon
CACanada
CVCape Verde
KYCayman Islands
CFCentral African Republic
TDChad
CLChile
CNChina
CXChristmas Island
CCCocos (Keeling) Islands
COColombia
KMComoros
CGCongo
CDThe Democratic Republic of the Congo
CKCook Islands
CRCosta Rica
CICote d'Ivoire
HRCroatia
CUCuba
CYCyprus
CZCzech Republic
DKDenmark
DJDjibouti
DMDominica
DODominican Republic
ECEcuador
EGEgypt
SVEl Salvador
GQEquatorial Guinea
EREritrea
EEEstonia
ETEthiopia
FKFalkland Islands
FOFaroe Islands
FJFiji
FIFinland
GFFrench Guiana
PFFrench Polynesia
GAGabon
GMGambia
GEGeorgia
GHGhana
GIGibraltar
GRGreece
GLGreenland
GDGrenada
GPGuadeloupe
GUGuam
GTGuatemala
GGGuernsey
GNGuinea
GWGuinea-Bissau
GYGuyana
HTHaiti
HNHonduras
HKHong Kong
HUHungary
ISIceland
INIndia
IDIndonesia
IRIran
IQIraq
IEIreland
IMIsle of Man
ILIsrael
ITItaly
JMJamaica
JPJapan
JEJersey
JOJordan
KZKazakhstan
KEKenya
KIKiribati
KWKuwait
KGKyrgyzstan
LALao People’s Democratic Republic
LVLatvia
LBLebanon
LSLesotho
LRLiberia
LYLibya
LILiechtenstein
LTLithuania
LULuxembourg
MOMacau
MKMacedonia
MGMadagascar
MWMalawi
MYMalaysia
MVMaldives
MLMali
MTMalta
MHMarshall Islands
MQMartinique
MRMauritania
MUMauritius
YTMayotte
MXMexico
FMMicronesia
MDMoldova
MCMonaco
MNMongolia
MEMontenegro
MSMontserrat
MAMorocco
MZMozambique
MMMyanmar
NANamibia
NRNauru
NPNepal
NLNetherlands
NCNew Caledonia
NZNew Zealand
NINicaragua
NENiger
NGNigeria
NUNiue
NFNorfolk Island
KPNorth Korea
MPNorthern Mariana Islands
NONorway
OMOman
PKPakistan
PWPalau
PSPalestine
PAPanama
PGPapua New Guinea
PYParaguay
PEPeru
PHPhilippines
PLPoland
PTPortugal
PRPuerto Rico
QAQatar
REReunion
RORomania
RURussia
RWRwanda
BLSaint Barthelemy
SHSaint Helena
KNSaint Kitts and Nevis
LCSaint Lucia
MFSaint Martin
PMSaint Pierre and Miquelon
VCSaint Vincent and the Grenadines
WSSamoa
SMSan Marino
STSao Tome and Principe
SASaudi Arabia
SNSenegal
RSSerbia
SCSeychelles
SLSierra Leone
SGSingapore
SKSlovakia
SISlovenia
SBSolomon Islands
SOSomalia
ZASouth Africa
KRSouth Korea
LKSri Lanka
SDSudan
SRSuriname
SJSvalbard and Jan Mayen
SZSwaziland
SESweden
CHSwitzerland
SYSyria
TWTaiwan
TJTajikistan
TZTanzania
THThailand
TLTimor-Leste
TGTogo
TKTokelau
TOTonga
TTTrinidad and Tobago
TNTunisia
TRTurkey
TMTurkmenistan
TCTurks and Caicos Islands
TVTuvalu
VIU.S. irgin Islands
UGUganda
UAUkraine
AEUnited Arab Emirates
UYUruguay
UZUzbekistan
VUVanuatu
VAHoly See (Vatican City State)
VEVenezuela
VNVietnam
WFWallis and Futuna
YEYemen
ZMZambia
ZWZimbabwe

Thank you

A member of our team will be in contact within 48 hours.


Stay up to date with our latest success stories.

Take a look at how Limbus AI cuts time to market with their innovative deep-learning solution for CT contour delineation.

Read the customer story