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