Device Master Record (DMR) is the compilation of records containing the procedures and specifications for a finished medical device, covering device design specs, production processes, quality assurance criteria, packaging and labeling, and installation and servicing methods. Defined under FDA 21 CFR 820.181, it now maps to the Medical Device File in ISO 13485:2016 clause 4.2.3.
What is Device Master Record (DMR)?
A Device Master Record (DMR) is the manufacturing recipe for one device type. It tells a qualified team what to build, from which components, on which equipment, under which environmental controls, and against which acceptance criteria.
The DMR sits downstream of design. Design controls produce approved design outputs; design transfer converts those outputs into production specifications, which become the DMR. It is a living document set, not an archive. Every approved change updates it.
Note the terminology shift. Under the FDA Quality Management System Regulation (QMSR), effective February 2, 2026, 21 CFR Part 820 incorporates ISO 13485:2016 by reference, and the term Device Master Record no longer appears in the regulation. FDA now enforces the Medical Device File under clause 4.2.3. The content obligation stayed. The label did not.
Why Device Master Record (DMR) matters in medical device development
Manufacturing conformity is a patient safety control. A DMR that lags the current approved design lets a plant build to superseded specs: wrong solder profile, wrong sterilization cycle, wrong labeling revision. Those defects reach patients.
It is also the record inspectors reach for first. An investigator pulls the Medical Device File, then a Device History Record (DHR) for a recent lot, and checks that the lot was built to the specs the file names. A gap between the two is a finding on document control and production controls at the same time.
Commercially, the DMR governs how fast you scale. Contract manufacturers, second sources, and new lines are all on board with it, and a folder of loose drawings with unclear revision status stalls transfer.
Key components of a Device Master Record (DMR)
Per 21 CFR 820.181, the DMR must include or refer to the location of five content groups. ISO 13485 clause 4.2.3 asks for the same substance.
- Device specifications. Drawings, composition, formulation, component specs, and software specs. For embedded software, this ties into IEC 62304 lifecycle records and released version identifiers.
- Production process specifications. Equipment specs, production methods, procedures, and environment specs: cleanroom class per ISO 14644-1, ESD controls, temperature and humidity limits.
- Quality assurance procedures. Acceptance criteria, in-process and final inspection plans, test equipment, sampling plans.
- Packaging and labeling specifications. Packaging validation per ISO 11607 for sterile barrier systems, label artwork revisions, UDI carriers, and IFU versions.
- Installation, maintenance, and servicing procedures. Relevant for capital equipment, imaging systems, and field-serviced devices.
The phrase “include or refer to” means the DMR can be a controlled index pointing at documents held elsewhere in the quality system. Nothing requires a single binder. It must also be prepared, dated, and signed by an authorized individual, which pulls it under document and change control.
Three record types get confused. The Design History File (DHF) shows how the device was designed. The DMR shows how to build it. The DHR shows how a particular lot was actually built.
Common challenges and best practices
The most common failure is drift. A change order is approved, the drawing updates, and the DMR index still points at revision B. Tie the DMR revision to the change control record so no ECO closes until every affected element is re-released.
The second failure is treating the five regulatory categories as a checklist of file names. They are minimum content requirements. A “packaging specification” pointing at a document with no sealed-package validation behind it satisfies nobody.
Practices that hold up under audit:
- Maintain one controlled index per device type or family, with document numbers and revision levels, not titles.
- Keep the DMR in a validated electronic system with audit trails, aligned with 21 CFR Part 11 where electronic signatures apply.
- Reconcile the DMR against the as-built BOM in the MES or ERP on a defined cadence. Divergence between engineering and production data is where recalls start.
- For EU market access, align the file with EU MDR 2017/745 Annex II technical documentation expectations.
- Retain records for the expected life of the device, at minimum two years from commercial release, per 21 CFR 820.180.
How SJML helps with Device Master Record (DMR)
Syrma Johari MedTech (SJML) builds and maintains production documentation as part of design transfer and new product introduction. Our engineering teams take approved design outputs through DfX review, BOM review, PFMEA, and process validation (IQ/OQ/PQ), so the specifications handed to the line are complete and verifiable. Manufacturing runs on SAP-integrated MES for traceability across PCBA, molding, precision metal, and box build, in cleanroom and ESD-controlled environments where the product demands them. Our QARA team supports ISO 13485 and MDSAP quality systems, document control, and regulatory sustenance.
Talk to SJML’s manufacturing team →
Frequently asked questions
The content is still required. The term is not. Effective February 2, 2026, the QMSR amended 21 CFR Part 820 to incorporate ISO 13485:2016 by reference, and the phrase Device Master Record no longer appears in the regulation. FDA now inspects against clause 4.2.3, Medical Device File, which covers the same production specifications and procedures.
The Device Master Record defines how a device type should be built: specifications, processes, acceptance criteria. The Device History Record captures how one lot, batch, or unit actually was built: dates, quantities, equipment used, inspection results, labeling applied. DMR is the standard. DHR is the evidence that a given unit met it.
Yes. The regulation uses the phrase “include or refer to the location of,” which permits a controlled index pointing to specifications held elsewhere in the quality system. The requirement is retrievability under document control, not physical consolidation. Every referenced document needs a document number, a current revision level, and accessibility to an inspector on request.
Design transfer converts approved design outputs into production specifications, and the DMR is the output of that conversion. If design outputs are ambiguous or untestable, the DMR inherits the ambiguity, and the line builds to interpretation rather than specification. A clean transfer yields drawings, tolerances, process parameters, and acceptance criteria a plant can follow without asking questions.
Related terms
- Design History File (DHF)
- Device History Record (DHR)
- Design Transfer
- Change Control
- Process Validation (IQ/OQ/PQ)
