Building a Digital Device History Record (eDHR)

A work order closes on Friday afternoon. Fifty devices, built across three cells, over four shifts, by seven operators. Production is done. Now Quality begins the real work.

Were the correct instructions followed? Were all in-process inspections completed? Did every step get signed off? Which revision of the drawing was actually used on Cell B on Wednesday night? Were the torque wrenches in calibration? Are the measurement records legible? Did anyone document the fifteen minutes the line was down for a bearing replacement?

If answering those questions requires walking to the shop floor, opening a three-ring binder, sorting through inspection sheets, checking two spreadsheets, and forwarding an email with a photo attachment, the manufacturing record is fragmented. It is not a Device History Record — it is a reconstruction project.

A modern electronic Device History Record isn't created after manufacturing. It is assembled naturally as manufacturing happens. Every signature, measurement, inspection, and photo drops into place at the moment the work is performed. By the time the last operator closes the last step, the record is complete, searchable, and ready to release.

What is a Device History Record?

Set aside the regulatory language for a moment. In practical terms, a Device History Record is the evidence that a specific product was manufactured according to the approved process. Not a summary. Not a certificate. The actual evidence.

If a device is returned two years from now, or an investigator asks about a particular lot, the DHR is the file you open to answer the question. A good one lets you answer immediately. A poor one starts a week of forensic work.

A complete DHR demonstrates, without ambiguity:

• Who built it. Which trained operators performed which operations, on which shift, on which date.
• What was built. The exact product, configuration, and quantity — tied to serial numbers, lot numbers, and UDIs.
• Which revision. The released revision of every work instruction, drawing, and specification in play at the time of manufacture.
• When work occurred. Timestamps at the step, not after-the-fact date fields.
• What inspections passed. In-process and final inspection results with acceptance criteria and pass/fail evidence.
• Which materials were used. Component lot numbers tied to each serialized device.
• Which equipment performed the work. Fixture, tool, and instrument identification with calibration status at time of use.
• What approvals were obtained. Electronic signatures at every point the process requires a signoff.

If your current record cannot answer any of those questions in a few minutes for any device you shipped last quarter, the record is doing less work than the people who built it deserve.

What belongs inside a Device History Record?

The exact contents of a DHR depend on the product, but the anatomy is consistent. Think of it as a set of layered evidence that answers different questions.

Each element earns its place. Signatures prove accountability. Revisions prove the correct instructions were used. Measurements prove specifications were met. Equipment records prove the tools were fit for purpose. Together, they add up to a defensible answer to the fundamental question: was this device built the way we said it would be built?

How paper DHRs become difficult to manage

Every quality team that has managed paper DHRs at scale recognizes the pattern. It is not that any single problem is catastrophic. It is that dozens of small problems compound, and after a year of production the cumulative weight is substantial.

• Missing travelers. A packet is set down on a bench, moved during cleanup, and no one can locate it Monday morning. Production stops while someone reconstructs the sequence.
• Handwritten corrections. A value is crossed out, initialed, and rewritten. Was the correction authorized? Was the change reviewed? The page shows the change but not the reason.
• Separate inspection forms. Inspection results live on a different sheet than the operation record, filed in a different folder, reconciled only if someone remembers.
• Manual filing. Completed travelers pile up, get bundled, get filed weeks after the fact. A record you cannot find is not a record.
• Scanning as an afterthought. Paper is scanned into PDFs at the end of the month. Search across a thousand scanned PDFs is not search.
• Lost signatures. The build is complete. The final signoff page went home in someone's notebook. The lot cannot release until it is recovered.
• Uncontrolled revisions at the bench. The engineering team released Rev C on Tuesday. The copy at Cell B is Rev B, printed in March. No one intended to build to the wrong revision. Paper does not update itself.
• Searching archives. A complaint comes in for serial 8471. Someone spends an afternoon in the file room. That afternoon is the response time on that complaint.
• Duplicate data entry. Measurements written on paper are re-typed into a spreadsheet, then re-typed into an ERP. Every keystroke is an opportunity for an error.

None of these are the fault of the operators, inspectors, or quality analysts. They are the predictable output of a system built on fragmented paperwork instead of a single, connected manufacturing record.

How an electronic DHR builds itself

The central shift in an electronic DHR is not that paperwork becomes digital. It is that the record stops being paperwork at all. Every manufacturing action contributes to a live record. When the last operation closes, the DHR is done.

Notice what is missing from that flow: a stage where anyone assembles the record. There is no separate DHR compilation step because there is nothing left to compile. The signatures were captured at the step. The measurements were recorded at the step. The revision was locked at the step. The equipment verification happened at the step. The record already exists.

What auditors actually want to see

Auditors — whether FDA, notified body, customer supplier quality, or your own internal quality team — are not looking for a beautiful binder. They are trying to answer a specific set of questions about your process control. The manufacturers who do best in audits are the ones who can answer those questions quickly, consistently, and without theatre.

Auditors do not expect perfection. They expect organization, consistency, and honesty. A record that shows a nonconformance, a proper investigation, and a documented disposition is far stronger than a record with suspicious gaps. Digital manufacturing records make that kind of transparency the default, not the exception.

The advantages of a digital Device History Record

The differences between paper and electronic DHRs are not marginal. Once a manufacturer has worked with a real eDHR, going back to paper feels roughly like going back to pulling numbers from a printout instead of a spreadsheet.

Common mistakes to avoid

Not every digital DHR project delivers the results it promises. The failures tend to share a small number of root causes, and every one of them is preventable.

• Collecting data after production. If operators finish a step and then fill in the data ten minutes later, the record is a memory exercise rather than a live capture. Digital systems that permit this defeat their own purpose.
• Incomplete signatures. Optional signoffs get skipped. Required signoffs cannot be skipped. Make the signature a gate, not a suggestion.
• Paper attachments stored separately. A digital record with a physical envelope of "supporting paperwork" is a hybrid record — which is to say, a paper record that pretends to be digital.
• Uncontrolled revisions. If the system does not enforce that only the current released revision may be served for new production, it is not controlling revisions.
• Missing inspection records. Inspections that live in a separate quality system, disconnected from the manufacturing record, are invisible to anyone opening the DHR.
• Scanning paperwork without organizing it. A folder of PDFs named by scan date is not a DHR. Structured data is what makes an electronic record actually electronic.
• Treating the DHR as a filing exercise. The DHR is the operational record of how a device was built. The moment it becomes a downstream artifact of "compliance," it stops being useful to the people who build the product.

Building an audit-ready process

Audit readiness does not begin the week before an inspection. It begins on the shop floor, weeks and months earlier, in the ordinary rhythm of executing manufacturing correctly. When the process is strong, the record is strong. When the process is weak, no amount of pre-audit polishing will hide it.

A manufacturer with those nine elements in place does not have to prepare for audits. They have to review the records the process already produced. That is the shift a digital DHR makes — from record assembly to record review.

The strongest records are built one step at a time

A Device History Record should never feel like paperwork assembled after production. It should be the natural result of a well-controlled manufacturing process — the byproduct of doing the work correctly and capturing what happened as it happened.

When manufacturing activities are documented digitally as work occurs, the completed record becomes more accurate, easier to review, easier to retrieve, and easier to defend. Quality teams stop assembling records and start reviewing them. Operations stops chasing missing signatures and starts closing work orders on time. Auditors stop waiting for boxes to be pulled and start reading the record that was already there.

The strongest Device History Records aren't created at the end of production. They're built one manufacturing step at a time.