Sample result
What a validation check looks like.
So that you can judge the quality of the work yourself, this page shows the result of a validation check using a typical example. Structure and depth match our report, shortened to the essentials.
Sample: entirely fictitious example, not a client case.
Based on GAMP 5 Second Edition and EU GMP Annex 11. Professional assessment, not legal advice.
1 Framework
- Company
- Mid-sized testing laboratory that analyses samples for pharmaceutical manufacturers and works under GMP.
- Occasion
- A new laboratory information management system (LIMS) is due to go live on [date per project plan].
- Markets
- EU, so Annex 11 applies. Whether customers also use the results for the USA is open.
- Existing
- A procedure for computer system validation, but no validation master plan.
- Criticality
- High with direct impact on patient safety or product quality, medium with impact on data integrity or indirect impact, otherwise low.
2 Classification of the systems
| System | Criticality | Classification |
|---|---|---|
| LIMS | high | GAMP category 4, configured software. The test results feed into the customers' release decisions. The supplier has been assessed by questionnaire and documents, not audited. |
| Interface from the chromatography data system to the LIMS | medium | Category 5, developed specifically for the laboratory. It transfers results; an error corrupts data. |
| LIMS server and database | medium | Category 1, infrastructure. It is qualified, not validated. |
| Invoicing in the ERP | not GxP | No impact on product quality or test data. |
3 Risk-based validation scope
LIMS
- Validation plan, user requirements and functional risk assessment.
- Configuration specification and traceability from requirements to tests.
- Supplier audit before go-live, because criticality is high.
- Audit trail, access control and backup as requirements of their own.
Interface
- Requirements plus functional and design specification.
- Code review and unit tests at the developer, plus a supplier audit.
Server and database
- Document installation and configuration, that is, qualify.
- Operation under change control.
Invoicing
- No GMP validation. The classification is justified and reviewed if the use changes.
4 Plan for tests, evidence and approval
| Test | For | Depth | |
|---|---|---|---|
| Installation qualification (IQ) | All three GxP systems | In the target environment. | |
| Operational qualification (OQ) | LIMS | All GxP-critical functions with positive and negative tests, independently reviewed. Supplier tests are credited where assessed. | |
| Operational qualification (OQ) | Interface | Critical functions per the risk assessment. | |
| Audit trail | roles and rights | LIMS | Including backup and restore. |
| Performance qualification (PQ) | LIMS with interface | With real workflows and the future users. | |
| Report and approval | All three GxP systems | Close deviations, approval by the quality unit, handover to operations. |
Deliberately not: invoicing is not validated, and qualification is enough for server and database. That keeps the effort where test data is created.
5 Open points
- Confirm [date per project plan] with the supplier and the quality unit.
- Clarify whether customers use the results for the US market. If so, 21 CFR Part 11 also applies to electronic signatures.
- Whether supplier tests can be credited depends on the assessment of the supplier's documents.
6 Next steps
- Draw up the validation plan and have the quality unit approve it.
- Write requirements and risk assessment for LIMS and interface.
- Carry out supplier audits at the LIMS supplier and the interface developer.
- Run the tests according to plan, assess and close deviations.
- After approval, set the periodic review.
Reservation
This sample is a professional assessment and not legal advice. It is based on GAMP 5 Second Edition and EU GMP Annex 11, and for the US market 21 CFR Part 11. Scope and test depth are a proposal that the quality unit sets and approves in the validation plan. Values in square brackets appear in the real report as results of the assessment.
Sample: entirely fictitious example, not a client case.
How much validation does your next system need?
30 minutes, confidential, no obligation