Periodic Review and Retirement of Validated Systems: The Back End of the Lifecycle

A system is not validated forever. Periodic review confirms it still does what it was validated to do, and retirement makes sure the data it created remain readable for as long as the law requires.

What periodic review is for

EU GMP Annex 11 expects computerised systems to be periodically evaluated to confirm that they remain in a valid state, covering the current range of functionality, deviations, incidents, problems, upgrade history, performance, reliability, security and compliance with the validation status. The July 2025 draft revision of Annex 11 proposed a dedicated periodic review chapter, so the expectation is likely to become more explicit. Check the current status of the revision before relying on its wording.

A practical review checklist

  • Changes made since the last review and whether each was assessed and tested appropriately.
  • Incidents, deviations and support tickets, and any trends in them.
  • User access: leavers removed, roles still appropriate, privileged accounts controlled.
  • Audit trail review practice and findings.
  • Backup and restore tests, disaster recovery and business continuity.
  • Supplier status: version support, security patches and end-of-life notices.
  • Whether the system is still used for its original intended use.

The frequency should reflect risk. A system affecting batch release deserves more attention than a low-risk reporting tool.

Acting on the outcome

The review should end in a documented conclusion and, where gaps appear, actions with owners and dates handled through the quality system. A review that always concludes “no issues” is an inspection risk in itself.

Retirement and data retention

When a system is decommissioned, the question is what happens to the records. Data subject to retention requirements must remain accessible, readable and usable throughout the retention period, either by keeping the system available in a controlled read-only state or by migrating the data with verification. Retirement should follow a plan approved under change control, with an impact assessment, a data disposition decision and a final report.

Do not forget the loose ends

Interfaces to other systems, user accounts, licences, archived backups and procedures that reference the old system all need closing out. The inventory of validated systems should be updated so that the retired system is clearly marked and its records can be located years later.

Related reading

How PQRA helps

PQRA designs risk-based periodic review programmes, conducts the reviews as an independent party, and plans retirement and data migration so that records stay compliant after the system has gone.

Ready to talk it through? Contact the PQRA team.

CATEGORIES:

Uncategorized

Tags:

No responses yet

Αφήστε μια απάντηση

Η ηλ. διεύθυνση σας δεν δημοσιεύεται. Τα υποχρεωτικά πεδία σημειώνονται με *