The Nonconformity That Was Really a Symptom
During an audit of a medical device manufacturer, you find 14 of 60 sampled device history records (DHRs) missing the final release signature. The quality manager says the signature is 'a formality' because the product passed all tests. Investigating further, you learn: the release step was recently moved into the ERP system; the ERP workflow only prompts for signature if a checkbox is ticked; the checkbox defaults to unticked; and no one was trained on the new workflow. Three of the 14 devices have already shipped. The QMS procedure still describes the old paper-based release. The CAPA log shows two prior CAPAs for 'missing signatures' in the past 18 months, both closed as 'retraining completed.'
1. Classify and characterize the finding(s). Is this one nonconformity or several, and at what severity?
Read the worked answer
This is not one clerical nonconformity - it is a system failure with a recurring corrective-action failure. Decompose it:
- Product release without required signature (major). 14/60 = 23% of sampled DHRs, with 3 units already shipped. Release without documented authorization means product was placed on the market without evidence the release criteria were met. That is a major, potentially reportable event depending on jurisdiction.
- Procedure does not reflect actual practice (major). The QMS procedure describes paper release; the process is now ERP-based. Documented process ≠ actual process is a control breakdown, not a typo.
- Ineffective CAPA (major / systemic). Two prior CAPAs for the same issue, both closed on retraining alone. Retraining cannot fix a software default that suppresses the prompt. The root cause was never addressed, so recurrence was predictable.
I would raise the release failure and the ineffective CAPA as the primary majors, and the stale procedure as a supporting finding. The 23% rate and shipped product push this well past minor.
2. The quality manager proposes 'retrain all operators and re-sign the 14 records.' Evaluate this corrective action.
Read the worked answer
It repeats the exact intervention that failed twice. Retraining addresses operator knowledge; the evidence says the cause is a system design default (unticked checkbox suppresses the prompt) plus an uncontrolled process change. Operators did nothing wrong that training would fix - the software let release proceed without a signature.
A defensible corrective action would: (a) contain - identify and assess the 3 shipped devices, quarantine/recall decision per procedure, and correct the 11 unshipped records only after verifying release criteria were actually met (not just signing retroactively); (b) correct the cause - change the ERP default so signature is mandatory and cannot be bypassed, or add a hard stop; (c) verify effectiveness - re-sample DHRs after the fix and confirm 100% signature capture over a defined period; (d) address the CAPA system itself - why were two CAPAs closed without effectiveness verification? That is the deeper root cause.
Retroactively signing records that were released without authorization is falsification risk unless each is independently re-verified against test data. I would reject the proposal and require a root-cause-based CAPA with effectiveness checks.