DHR review checklist under the FDA QMSR
By Savi C., Co-Founder · Published Nov 16, 2026
What changed under the QMSR
The Quality Management System Regulation amended 21 CFR Part 820 to incorporate ISO 13485:2016 by reference. In doing so it dropped three familiar terms. The device master record maps to the medical device file in ISO 13485 clause 4.2.3. The design history file maps to the design and development file in clause 7.3.10. The device history record maps to the record for each device or batch in clause 7.5.1.
The obligations did not go away, and most sites still call the per-device record a DHR. What changed is the yardstick: FDA now inspects against ISO 13485 as incorporated by the QMSR, plus the requirements the QMSR keeps on top of it, such as labeling and packaging controls under 820.45.
The DHR review checklist
Build record
- Every operation on the traveler completed in sequence, signed and dated
- Components and lot numbers match the bill of material at the revision in effect on the build date
- Firmware or software version programmed matches the approved revision
- Calculations carried through correctly, with units and rounding as the procedure specifies
- Quantity started, scrapped, reworked and released reconciled, with no unexplained loss
Acceptance activities
- Every in-process and final inspection and test present, with results inside specification
- Instruments used for acceptance were in calibration on the build date
- Where implantable devices are involved, the identity of the people performing inspection and testing is recorded
Labeling and identification
- Labeling inspected before release and the inspection recorded, as 820.45 requires
- The label matches the approved revision, including the UDI, expiration date, and storage and handling instructions
- Labels issued, used, destroyed and returned reconciled for the lot
Nonconformances and documentation
- Every out-of-specification result has a nonconformance report with a disposition
- Reworked product re-inspected to the original acceptance criteria
- Corrections made under good documentation practice: a single line, initialed, dated, with a reason where your procedure requires one
Release
- Release recorded with the identity of the person authorizing it, as ISO 13485 clause 8.2.6 requires
- Release signed only after every other record in the packet was complete
How Litewave fits
Litewave reads paper or electronic DHR packets and travelers, applies checks like these against your own specifications, and gives QA only the exceptions, each linked to the page it came from. Litewave proposes, qualified people approve, and the release decision stays with your quality system. Our published results come from pharmaceutical manufacturing, and device figures will be published only when a device customer has agreed to them.
Questions we get asked
Does FDA still use the term device history record?
Not in the QMSR. The regulation now relies on ISO 13485, where the equivalent is the record for each device or batch in clause 7.5.1. The record is still required, and most manufacturers still call it a DHR internally.
Does ISO 13485 certification mean we comply with the QMSR?
Not by itself. The QMSR incorporates ISO 13485 but keeps additional FDA requirements, including labeling and packaging controls under 820.45, and FDA inspects against the regulation rather than your certificate.
Who has to approve device release?
Whoever your procedures authorize. ISO 13485 clause 8.2.6 requires the record to identify the person authorizing release, so the review is not complete until that authorization is recorded.
