Situation
An electronic device history record (eDHR) integrates with a labeling system and automated vision inspection after a label-template update.
Intended Use
Select the approved label, print it for the identified product and lot, inspect critical text and code, reconcile counts, and retain the execution and approval record.
Decision Summary
| Decision element | Case record |
|---|---|
| GxP assessment | Label identity, content, lot association, inspection decision, reconciliation, and retained approval record affect device identification and release. |
| Potential impact | A mislabeled device can be released or the history record can fail to demonstrate correct labeling and reconciliation. |
| Known issue | The fictional retry creates a duplicate serial record while printing only one label. |
| Validation conclusion | The release is restricted until idempotency and reconciliation are corrected and end-to-end negative and recovery tests pass. |
GxP Assessment
Label identity, content, lot association, inspection decision, reconciliation, and retained approval record affect device identification and release.
Affected GxP Functions
- Approved label selection
- Product and lot data mapping
- Printer and vision-system interface
- Reject handling and reconciliation
- eDHR completion and approval
Failure Scenarios
- Obsolete label is selected
- Serial or lot code maps to the wrong record
- Vision inspection passes an unreadable code
- Rejected labels are not reconciled
- The approved record lacks the actual label image
Potential Impact
A mislabeled device can be released or the history record can fail to demonstrate correct labeling and reconciliation.
Existing Controls
- Controlled label master
- Line clearance
- Vision inspection
- Count reconciliation
- Quality release review
Existing Evidence
- Supplier printer qualification
- Vision-system performance study
- Existing eDHR validation
- Approved label proof
Evidence Gaps
- New template mapping
- Interface retry behavior
- Mixed-lot recovery
- Archived image retrieval
Testing Approach
- Script approved and obsolete template selection
- Challenge field mapping, code boundaries, and unreadable images
- Test failed transfer, retry, duplicate prevention, and reconciliation
- Verify record image, audit trail, signature, and accurate copy
Deviations or Known Issues
The fictional retry creates a duplicate serial record while printing only one label.
Validation Conclusion
The release is restricted until idempotency and reconciliation are corrected and end-to-end negative and recovery tests pass.
Reassessment Criteria
- Template or code change
- Printer or vision algorithm update
- Interface or retry change
- Product master change
- Labeling complaint or deviation
Limitations and unresolved questions
Successful printing alone does not establish correct history records. Release remains limited until duplicate identity and recovery paths are controlled.
Relevant regulations and guidance
These sources apply within their stated scope. The suggested worksheet fields, test designs and fictional decisions are practitioner recommendations, unless a source requirement is expressly identified. Completing a template does not establish compliance.
Computer Software Assurance for Production and Quality Management System Software ↗
Regulatory guidance / GMP guideline · United States · February 2026
Scope: Medical-device manufacturers assuring software used in production or their quality management system.
Relevance: For medical-device production or QMS software, supports selecting assurance activities from intended use, risk and available evidence. It is nonbinding guidance and does not determine other sectors’ obligations.
Status: Final / published · Checked 2026-09-21
Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.
Read source details and applicability →EudraLex Volume 4, Annex 11 — Computerised Systems ↗
Regulatory guidance / GMP guideline · European Union · January 2011 revision
Scope: Computerised systems supporting activities in the applicable EU pharmaceutical GMP context.
Relevance: For computerised systems used in EU GMP activities, informs lifecycle, supplier and record controls. Confirm applicability to the actual activity; the example does not establish it.
Status: Final / published · Checked 2026-09-21
The Commission index confirms the January 2011 operative revision. The linked PDF could not be retrieved in this check; retained detailed section mappings need review against an authorized copy.
Read source details and applicability →21 CFR Part 11 — Electronic Records; Electronic Signatures ↗
Regulation · United States · Current eCFR text
Scope: Electronic records and signatures within FDA Part 11 scope, tied to the underlying required records.
Relevance: Assess applicability to electronic records required by FDA predicate rules and electronic signatures used in their place. The presence of an electronic record alone is not an applicability conclusion.
Status: Final / published · Checked 2026-09-21
Publication identity, scope and status checked against the linked official source. This is not an independent audit of every retained guide statement.
Read source details and applicability →Was this useful? Leave feedback
Was this resource useful?
Tell us what helped and what could be clearer. Usefulness feedback does not establish technical validity or regulatory compliance.
Loading contribution options…
Questions and moderated discussion
Questions and discussion
What additional information would you need before making this decision?
Loading contribution options…
Suggest a correction
Sent privately to the editorial moderation queue. Your account email and correction are not published as a comment. Do not include confidential or personal information.
Resource: Electronic Device History Record and Labeling
Loading sign-in status…