V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryeDHR
Records · The complete guide

eDHR: Electronic Device History Records under the QMSR

In short

An eDHR (electronic device history record) is an electronic collection of production and acceptance records associated with a medical device or batch of medical devices.

4,087 words · ~19 min read
Cleanroom operator in hood, mask, glasses and gloves recording a device assembly step on a tablet
On this page
  1. 01What an eDHR is—and where its boundaries belong
  2. 02Current QMSR requirements: scope before record design
  3. 03DHR, DMR and DHF: legacy vocabulary, different purposes
  4. 04Paper, hybrid and electronic records: choose an authoritative history
  5. 05What a defensible electronic production record contains
  6. 06UDI and traceability: connect identifiers without confusing them
  7. 07Nonconformance and rework: preserve the path to disposition
  8. 08Integrations and outage recovery: reconcile events, not just files
  9. 09Validating intended use and controlling system changes
  10. 10Common weaknesses and an implementation review checklist
  11. 11Retention, complaints and later reconstruction
On this page · 11 sections
  1. 1What an eDHR is—and where its boundaries belong
  2. 2Current QMSR requirements: scope before record design
  3. 3DHR, DMR and DHF: legacy vocabulary, different purposes
  4. 4Paper, hybrid and electronic records: choose an authoritative history
  5. 5What a defensible electronic production record contains
  6. 6UDI and traceability: connect identifiers without confusing them
  7. 7Nonconformance and rework: preserve the path to disposition
  8. 8Integrations and outage recovery: reconcile events, not just files
  9. 9Validating intended use and controlling system changes
  10. 10Common weaknesses and an implementation review checklist
  11. 11Retention, complaints and later reconstruction
AI · Explain it for MY operation

How does eDHR apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What an eDHR is—and where its boundaries belong

In medical-device manufacturing terminology, an electronic device history record (eDHR) is the organised electronic evidence of production and acceptance for an identified device or batch. It captures what actually happened—operations performed, materials used, results recorded and decisions made—not merely what instructions planned. This is an industry-use definition, not a statutory definition.

The record is not the application that stores it. A manufacturing execution system may hold production entries while laboratory and quality systems hold supporting evidence. A practical eDHR can bring these together or connect them through controlled references, provided reviewers can retrieve the relevant records and reconstruct the batch execution history. A link to a changing dashboard is not a stable historical reference.

Define the boundary by device identity, batch grouping and covered manufacturing operations. Direct entries typically identify completed operations, operators, material lots, acceptance results and disposition. Detailed laboratory data, equipment maintenance histories and quality investigations can remain in their own controlled records; the eDHR references the specific evidence relevant to that production history. This avoids copying entire systems into each record while keeping the basis for decisions accessible.

In accountable record-review practice, authorised people remain responsible for review, approval and release. Software completeness checks are review inputs: populated fields do not establish acceptable results or resolved exceptions. An electronic release record documents the authorised disposition decision rather than substituting for it.

02Current QMSR requirements: scope before record design

Start an eDHR project with an applicability map, not a screen layout. As a practical planning method, identify the product, destination market and operations performed before deciding which evidence belongs in the production record. This keeps a shared electronic workflow from becoming an assumed regulatory template for every product at a site.

Binding US device requirements

For US finished devices intended for human use, 21 CFR 820.1(a) covers design, manufacture, packaging, labeling, storage, installation and servicing. For US finished-device manufacturers performing only some covered operations, that same provision limits obligations under the part to requirements applicable to the operations they perform.

For US finished-device manufacturers subject to the QMSR, 21 CFR 820.10(a) requires a documented quality management system complying with applicable ISO 13485 requirements, incorporated by reference, and other applicable requirements of the part. ISO 13485 therefore belongs in the quality-management framework, rather than being treated as an eDHR field specification. The QMSR and ISO 13485 relationship provides useful context for that distinction.

For US finished devices under the QMSR, 21 CFR 820.1(b) gives requirements specifically applicable to the device priority over more generally applicable requirements when requirements in this part conflict with requirements elsewhere in the same chapter.

Translate applicability into record boundaries

Jurisdiction and productApplicability questionRegulatory referenceRecord-design consequence
US finished devices intended for human useWhich covered operations does the manufacturer perform?21 CFR 820.1(a); 820.10(a)Map production evidence to the applicable quality-management framework.
US finished devices; manufacturer performs selected operationsWhich requirements apply to those operations?21 CFR 820.1(a)Define the local record boundary and interfaces with other organisations.
Other product or market combinationsWhich legal framework applies to this product and destination?Product- and market-specific assessmentAssess separately before reusing the US device configuration.

The table is an industry-practice planning tool, not a prescribed regulatory form. Its record-design consequences are recommendations, distinct from the binding US device provisions above. A useful implementation step is to assign an owner to each applicability decision and connect that decision to the affected workflow. Broader context belongs in the FDA QMSR overview, rather than being embedded as assumptions in individual data fields.

The architecture and implementation suggestions that follow are industry practice unless expressly identified otherwise; they are not additional regulatory duties or agency guidance. Keep software configuration decisions separate from legal applicability decisions, even when the same project team handles both.

03DHR, DMR and DHF: legacy vocabulary, different purposes

These descriptions reflect common legacy or operational usage, not quotations of current legal definitions. For current US device obligations, use the regulatory mapping above rather than deriving requirements from familiar record names.

TermPractical question answeredTypical contentsRelationship to the production record
DHR: device history recordWhat happened to this particular device or batch?Execution entries, material identities, results and disposition evidence.The familiar production-history concept.
eDHR: electronic device history recordWhat happened, as documented electronically?Electronic execution entries and linked supporting records.An electronic implementation of that history.
DMR: device master recordHow is the device intended to be manufactured?Manufacturing specifications, instructions and acceptance criteria.Provides the controlled manufacturing baseline for execution.
DHF: design history fileHow did the design develop?Design decisions, reviews and verification or validation evidence.Provides design context, not individual production history.
Production work orderWhat job is being organised?Product, planned quantity, routing and scheduling information.Organises the job; execution evidence documents its performance.
Quality management systemWhat processes and controls govern the work?Procedures, responsibilities, change controls and quality processes.Provides the broader framework around production records.

The useful connection is between an approved instruction revision and evidence of its execution. In practice, the production record should identify the revision that governed the operation and preserve access to it. Linking only to today's electronic work instruction does not establish what applied earlier. A later instruction change should remain distinguishable from the historical execution evidence; otherwise, a reviewer cannot reliably compare the recorded work with its intended manufacturing baseline.

04Paper, hybrid and electronic records: choose an authoritative history

Choose record arrangements by operational controls, not the presence of a screen. This comparison describes practical governance options, not universal regulatory acceptance.

ArrangementLegibility and attributionRevision linkage, retrieval and reconciliation
Paper with controlled imagesCheck handwriting, contributor identity and image completeness.Link form revisions; index images; reconcile originals against copies.
Hybrid records with externally held resultsPreserve readable results and their originating analyst or instrument.Link method revisions; maintain external references; reconcile transfers.
Structured electronic recordsCheck rendered values and user or system attribution.Retain executed revisions; retrieve linked evidence; reconcile interfaces.

For data integrity, designate the authoritative source for each evidence type before execution. If a paper entry, imported result and later transcription disagree, the designated discrepancy owner compares origins and context, documents the resolution and preserves conflicting entries; newest does not mean authoritative.

Device/batch identification → execution evidence from operators → result assessment by testing personnel → exception resolution by assigned owners → authorised reviewer receives reconciled record → retrieval by record custodian

At shift change, outgoing staff identify pending evidence, unresolved discrepancies and the next owner. Incoming staff acknowledge the handoff so review does not depend on memory.

Electronic Production-Record Lifecycle
  1. 1
    Identify scopeAssociate the device or batch with its work order.
  2. 2
    Select instructionsReference the applicable approved instructions and acceptance criteria.
  3. 3
    Capture executionAssociate materials, actors and observations with manufacturing events.
  4. 4
    Assess resultsCompare observations with the criteria governing that operation.
  5. 5
    Resolve exceptionsConnect failures, rework and retests without erasing history.
  6. 6
    Record dispositionRetain the authorised review decision and supporting evidence.
  7. 7
    Preserve retrievalKeep the record and its linked evidence interpretable.
Illustrative operating sequence; exception paths return to the affected activity.

05What a defensible electronic production record contains

Use the following architecture as a practical device-manufacturing evidence model, not a universal mandatory-field list. Select fields around the operations performed and the questions reviewers need to answer; assess applicable regulatory obligations separately.

Evidence componentExample fieldsReviewer questionRelationship to other records
Device and batch identityDevice model, batch, serial numberWhich devices does this cover?Parent production record
Instructions and specificationsDocument identifiers, applicable revisionsWhat instruction applied?Controlled work instructions and specifications
Material genealogyComponent lots, quantities, assembly linksWhat was used?Receiving records and component histories
Operation executionStep, occurrence time, ingestion timeWhat happened, and when?Execution events linked to production
Operator and equipment referencesOperator identity, equipment identifierWho performed the work, using what?Personnel and equipment records
Observed resultsValue, units, method revision, device/batchWhat evidence supports the result?Raw readings and test records
Acceptance criteriaApplicable limit or decision rule, revisionAgainst what was the result assessed?Specification linked to each assessment
ExceptionsAffected devices, issue, investigation referenceWhat interrupted the expected path?Nonconformance and rework records
Disposition evidenceDecision, reviewer, approval time, rationaleHow was the resulting status decided?Electronic release record

Keep acceptance criteria separate from observed results: a limit describes the assessment rule, not what was measured. Preserve each result’s relationship to its method or procedure revision, units, and affected device or batch. Production context tagging helps make these relationships explicit.

Data-model relationships

Production record → execution events → evidence items Material genealogy → production record and consuming execution events Exceptions → affected events, evidence items and devices Review decisions → assessed evidence items, exceptions and production record

In this model, distinguish event occurrence from later ingestion whenever delayed transfer could obscure sequence. Apply the review boundary established in the opening.

Raw evidence is the original observation or capture. A derived summary calculates or condenses that evidence; retain its calculation basis and links to its inputs. A reference points to evidence held elsewhere, rather than containing it. Give that reference a stable identifier and retrieval path so reviewers can reach the evidence behind the summary.

Practical Production-Evidence Relationships

Production Record

Identifies the production subject.

  • record_id
  • lot_id
  • serial_id
  • udi

Execution Event

Connects activity to its record.

  • event_id
  • record_id
  • instruction_revision
  • source_event_id

Evidence Item

Preserves observations and their context.

  • evidence_id
  • event_id
  • result_value
  • result_unit
  • criterion_revision

Material Genealogy

Links incorporated materials to production.

  • genealogy_id
  • record_id
  • component_lot_id
  • component_serial_id

Exception Record

Connects departures with resolution evidence.

  • exception_id
  • affected_event_id
  • disposition_id
  • retest_evidence_id

Review decision

Attributes disposition to its reviewer.

  • review_id
  • record_id
  • reviewer_id
  • decision
  • decided_at
Suggested entities, not a mandatory regulatory database schema.

06UDI and traceability: connect identifiers without confusing them

For US medical-device manufacturers subject to the QMSR, 21 CFR 820.10(b)(1) requires a documented system for assigning unique device identification in accordance with part 830.

For US medical devices subject to the QMSR, 21 CFR 820.35(c) requires the UDI to be recorded for each medical device or batch of medical devices.

For US medical-device manufacturers subject to the QMSR, 21 CFR 820.10(b)(2) requires documented traceability procedures in accordance with part 821, when applicable.

Practical identifier mapping

In eDHR data design, the recorded UDI and local production keys serve different purposes. A useful mapping distinguishes:

  • Work-order key: locates the production job and its execution records.
  • Batch identifier: groups units within the site's production history.
  • Serial number: distinguishes an individual unit in the local record model.
  • Component genealogy reference: links the finished device or batch to component lots or individual components actually consumed.

These relationships are practical design choices, not additional UDI rules. Related values need explicit mappings rather than an assumption that every identifier denotes the same thing. An identifier alone does not reconstruct material consumption or operation history: that takes linked consumption transactions and execution records. A practical retrieval test starts from the recorded UDI, finds the relevant device or batch, then follows its production context to materials used and operations performed.

07Nonconformance and rework: preserve the path to disposition

A practical eDHR exception model connects the originating event to affected devices or batches, interim status, investigation, proposed disposition, authorised instructions, execution evidence, retest and final review. This is an industry-practice model, not permission to rework or release a particular device.

Worked case assumptions: a serialised finished assembly fails a functional test and subsequently undergoes authorised rework. The traceability unit is the finished-device serial number; the result type is pass or fail, with no measurement units. The authorised instruction addresses a connector-seating issue.

  1. Record the failure. Link the failed test execution, applicable test instruction, operator and timestamp to the assembly serial number. Identify the affected assembly explicitly and record its interim hold or quarantine status.
  2. Connect the investigation and proposal. Reference the investigation assessing the connector issue and the proposed rework disposition. Where used, link the material review board decision rather than treating a production comment as authorisation.
  3. Document authorised execution. Link the applicable rework instruction and revision, its authorisation, the assembly identity, who performed the work, when it occurred and what was actually done. In this case, the execution evidence records reseating the connector.
  4. Retest and review. Create a separate test execution linked to the rework and original failure. Record the pass result, then route the connected evidence to the human QA disposition step.

The reviewer considers whether the performed work addresses the investigated failure, whether the retest evaluates the failed function, and whether rework introduced effects needing further evaluation. A pass alone does not explain why the original failure is resolved.

Keep both observations connected. A new test execution is not a correction to incorrectly entered data; a correction instead preserves the prior entry and explains the change. Evidence supporting disposition of this assembly does not, by itself, establish the status of other assemblies sharing its component lot or operation. That scope question belongs in the investigation.

08Integrations and outage recovery: reconcile events, not just files

A practical eDHR integration model assigns ownership before connecting systems. These are manufacturing-record design patterns, not legally prescribed interface behaviours. Typical exchanges and suggested responsibilities include:

  • Enterprise planning: orders, materials and production identifiers; planning owns order identity and approved order revisions.
  • Laboratory or test systems: methods, results and interpretations; laboratory or test engineering owns method revisions and result interpretation. Define the laboratory handoff.
  • Equipment: execution events and process readings; automation engineering owns source identifiers and event semantics.
  • Labeling systems: template revisions, print jobs and verification results; labeling control owns approved template selection.
  • Quality records: nonconformance references and disposition status; authorised quality personnel own disposition changes through the quality-system interface.

Distinguish source-generated evidence from its received representation. Where useful, retain source-system identity, stable source-event identifier, occurrence time, receipt time and reconciliation status. Assign an integration owner to mapping revisions and an operational owner to resolving rejected records. Preserve production context, including the device and operation association.

Worked outage-recovery case

Assume a test station buffers a result during an outage. The event unit is a test execution associated with a finished-device serial number. Normal synchronisation delivers it; a recovery replay later delivers the same event.

Match the stable source-event identifier within its source-system namespace. Retain a canonical event and log an identical replay without creating another execution. Route conflicting content under that identifier for investigation rather than overwriting it. Matching timestamps or result values alone cannot establish duplication: separate executions can share both.

Use controlled offline capture with attributable entries and visible pending-reconciliation status. Expose failed imports and orphan attachments in an assigned work queue. Successful transfer confirms transport, not correct association with the device and operation; reconciliation checks that association before treating the evidence as complete.

09Validating intended use and controlling system changes

Start with intended use, not a generic test script. Describe the operations, evidence types, user roles, interfaces and review decisions the eDHR supports. Identify where an error could misrepresent device history or mislead a reviewer. This practical risk-based validation approach connects testing effort to record consequences; it is not a statement of regulatory validation requirements.

Build a CSV traceability matrix linking each record risk to an expected behaviour, test and retained result. Include negative and boundary scenarios, not just successful workflows.

Record functionSuggested challenge and expected evidence
Identity assignmentSubmit a mismatched device identifier; demonstrate rejection or controlled resolution.
Revision selectionSelect a superseded instruction; demonstrate the intended restriction or authorised exception.
AttributionSwitch users during execution; confirm actions remain attributed to the correct actor.
Result interpretationSubmit an unexpected unit and values at acceptance boundaries; confirm correct handling.
Record changesAttempt an unauthorised change; confirm prevention and preservation of existing evidence.
Access permissionsChallenge role boundaries; confirm users cannot perform excluded actions.
Review routingSubmit an incomplete record; confirm missing evidence is surfaced before approval.
ExportExport representative histories; confirm identifiers, context and review status remain understandable.
RecoveryInterrupt a transaction; confirm recovery leaves neither missing nor duplicate committed evidence.

Supplier documentation can inform testing, but does not by itself demonstrate that the configured system works for the manufacturer’s intended process. Evaluate configuration, permissions, interfaces and representative data alongside the core application. Record unexpected results, their resolution and the basis for accepting the tested configuration.

For each proposed change, identify affected record functions and dependencies, select proportionate regression tests and retain approval evidence. Check that existing records remain interpretable after deployment, including their historical revisions and review context. Apply the review boundary established in the opening. For a worked assurance assessment, see executed evidence in the implementation guide.

Assess separate electronic-record and electronic-signature legal obligations for the relevant product and jurisdiction; do not assume one universal rule.

10Common weaknesses and an implementation review checklist

Use the earlier record-boundary, traceability and recovery discussions as demonstration prompts. These are practical readiness checks, not a regulatory inspection checklist or compliance certification. Ask reviewers to retrieve evidence rather than accept feature descriptions.

WeaknessReview consequencePractical controlDemonstration evidence
Mutable instruction linksHistorical instructions uncertainBind execution to instruction revisionRetrieve the revision applicable at execution
Unassociated attachmentsEvidence cannot be attributedLink attachments to device and eventFollow an attachment to both records
Missing result contextAcceptance cannot be reconstructedUse production context taggingReconstruct the result with units and applicable criteria
Ambiguous genealogyAffected devices unclearPreserve component-to-device relationshipsTrace a component lot to affected devices
Unreconciled importsMissing or duplicate events unresolvedReconcile source and destination eventsDemonstrate a resolved reconciliation case, including discrepancies
Incomplete exception linksDisposition basis unclearConnect exception, action and approvalFollow the original failure through authorised disposition

Implementation review checklist

  • Scope owner: Who maintains the documented device, operation and site boundaries?
  • Authoritative records: Can reviewers identify the controlling record for each evidence type?
  • Identifier ownership: Who assigns identifiers and resolves collisions?
  • Review responsibilities: Who reviews evidence and authorises disposition?
  • Exception routing: Can an unresolved exception reach its accountable decision-maker?
  • Interface reconciliation: Who resolves discrepancies across MES–historian interfaces, and where is closure recorded?
  • Intended-use tests: Which executed tests demonstrate normal, failure and recovery behaviour?
  • Retrieval responsibilities: Who can retrieve readable histories and linked evidence after system changes or retirement?

11Retention, complaints and later reconstruction

For US medical-device manufacturers subject to the QMSR, 21 CFR 820.35(a) requires records of complaint review, evaluation and investigation for possible failures of a device, labeling or packaging to meet its specifications. For those US manufacturers, the same provision allows a further investigation to be omitted when a similar complaint has already been investigated, and requires records documenting the justification for that decision.

Worked reconstruction: start with the device

Assume a complaint identifies a serialised finished device; the traceability unit is that device serial number. A practical reconstruction follows that identifier to production evidence, uses a backward genealogy trace to identify component lots, and retrieves acceptance results and relevant exceptions. Compare this evidence with the history available when the authorised person made the production disposition recorded in the electronic release record.

Keep subsequent servicing evidence distinguishable: a replaced component or later test result describes a later state, not necessarily the device as released. The complaint record captures the reported issue and its evaluation; production history supports reconstruction of manufacture; servicing history explains later interventions. Link these records rather than merging their purposes.

This reconstruction supports a reasoned scope assessment. Shared component lots or documented process exposure can provide a basis for examining other devices; a shared model designation alone does not establish shared production exposure. Treat a missing serial-to-component link as an open information question, with an owner and follow-up action, rather than assuming either exposure or exclusion.

Plan retention around later retrieval

As record-management practice, set retention arrangements through the applicable product-and-market assessment and controlled policy, not a generic eDHR duration. Assign responsibility for historical records, including after system replacement. Plan continuing readability, attachment retrieval and preservation of relationships between records; periodically test whether an authorised reviewer can reconstruct a device history from the retained material.

Cover of The Medical Device Production Guide
For medical device production

Putting eDHR into practice

It shows how assembly revisions, inspections, rework and labelling come together in a reviewable electronic device record.

The Medical Device Production Guide · 32-page guide

Get the guide See the industry page

Frequently asked questions

Q.Should legacy DHR names be changed in procedures, application screens and historical archives?+

Typically, manage terminology through change control, rather than renaming everything at once. As covered in the current-QMSR scope above, the documented quality-management-system obligation already governs the underlying records. In procedures, define how the legacy DHR label maps to current production records. Update screen labels where they confuse users, while preserving searchable aliases. Keep historical archive titles intact and add an explanatory index rather than rewriting approved records.

Q.How can a device manufacturer retrieve production evidence held by a contract manufacturer?+

A practical approach is to define retrieval arrangements in the manufacturing agreement: record ownership, identifiers, export contents, responsible contacts, and access after the relationship ends. Through contract manufacturer management, test a request for an actual production lot, including subcontracted processing and unresolved exceptions. Check whether the returned package identifies its source and approval status. Agree how missing evidence will be escalated and who will maintain access if the contractor changes systems or ceases operating.

Q.When is a controlled scan sufficient for practical retrieval, and when does structured data add value?+

For practical retrieval, a controlled scan can serve when reviewers need a faithful, readable document and can reliably locate its pages, attachments, identifiers, and approval evidence. In a hybrid record system, reconcile the scan against its source before relying on it. Structured data adds value when users need to trace component relationships, compare results, or search across lots. Treat OCR as a search aid until checked; data integrity depends on preserving meaning, not merely making text searchable.

Q.How should a lot-based production record represent components tracked by individual serial number?+

A practical model keeps the production lot as the parent record and records each serialized component as a distinct consumption relationship. Identify the component type, serial number, installation event, and receiving assembly or unit where relevant. Use production context tagging to distinguish components installed, removed, replaced, scrapped, or returned unused. A serial-number attachment alone can leave the final configuration ambiguous. Reconcile the relationships against actual assembly history so a reviewer can trace both the lot and the affected individual units.

Q.How should a mistake discovered after record approval be corrected without obscuring the earlier decision?+

Typically, create a linked correction rather than silently replacing the approved entry. Preserve the original value, correction author, timing, reason, and supporting evidence in the audit trail. Ask an authorized reviewer to assess whether the change affects the earlier disposition and document that assessment separately. Where an electronic release record references the mistaken information, link the correction to that decision. Keep the original approval visible; any subsequent approval should clearly identify the corrected record state it covers.

Q.What should be demonstrated before retiring an application that holds historical production records?+

A practical retirement test demonstrates that representative historical records remain searchable, readable, and interpretable without the original application. Include difficult cases: attachments, changed templates, linked test results, corrections, and approval histories. As part of record retention and archiving, reconcile migrated content against the source and document unresolved discrepancies. Test retrieval using the intended archive tools and user permissions. Also demonstrate recovery from backup and assign ownership for future format changes, access administration, and retrieval requests before shutting down the old system.

Q.What should a reviewer receive when important test evidence remains in a separate laboratory or equipment system?+

A useful review package includes the production identifier, sample identity, test method revision, result and units, acceptance criteria, review status, and a stable reference to supporting evidence. With MES to LIMS integration, check that identifiers resolve to the intended test, not merely the latest result for that sample. Include relevant retest history and explanations for excluded results. The sample handoff should connect the tested material to production. Give reviewers usable access to underlying records when the summary cannot answer their questions.

Q.How can an external reviewer receive a complete production history without unnecessary access to unrelated records?+

Typically, prepare a scoped export organized around the requested device, lot, or serial number rather than granting broad application access. Include an index of the relevant batch execution history, attachments, exceptions, corrections, and approval evidence. Check that references resolve inside the package or through separately authorized access. Clearly identify redactions and exclusions so they do not look like missing pages. Have someone unfamiliar with the production run reconstruct its sequence from the package before sharing it through a controlled channel.

Primary sources

  • 21 CFR 820.1
  • 21 CFR 820.10
  • 21 CFR 820.35

Further reading

  • eDHR Implementation: Executed Evidence
    A distinct worked implementation exercise with failed and pending assurance evidence.
  • Medical-Device eDHR Software
    Software evaluation, distinct from the eDHR definition.
  • Medical-Device MES
  • Medical Device Kitting

Explore this topic

eDHR sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.

Batch & Device Records
14 related entries

Master and executed records that prove a batch or device was made to spec.

BMReBMRMMRBPRBatch RecordDHRCoACoCPIF21 CFR 21121 CFR 11121 CFR 820Technical FileDesign Controls
Medical Device Regulatory
26 related entries

Device-specific rules, submissions and the standards that bind them.

21 CFR 82021 CFR 803ISO 13485ISO 14971IEC 62366ISO 10993IEC 62304IEC 60601510(k)PMADe NovoEU MDRIVDRMDSAPNotified BodyPredicate DeviceTechnical FileCE MarkingDesign ControlsDesign VerificationHuman FactorsPMSMedWatchCustomer ComplaintUDIDHR
Talk to us about eDHR

Want to see how eDHR could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
Medical Devices
Example reports
V5Ultimate

Sample report

Electronic Device History Record (eDHR)

Plan & make

Electronic Device History Record (eDHR)View on screen or print
→ All example reports
Regulatory anchors
  • 21 CFR 820.35 (QMSR)
  • 21 CFR Part 11 (where applicable)
  • Former 21 CFR 820.184 (QSR, before 2 Feb 2026)
Related terms
  • → DHR
  • → BMR
  • → eBMR
  • → MMR
  • → BPR
  • → Batch Record
  • → CoA
  • → CoC
  • → PIF
  • → 21 CFR 211
  • → 21 CFR 111
  • → 21 CFR 820
  • → Technical File
  • → Design Controls
  • → 21 CFR 803

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC