Computer system validation · GAMP 5 · Pharma, biotech, medtech
Risk-based validation for GxP systems
CSV for pharma, biotech and medtech, across the entire system lifecycle.
Typical starting points
-
New system or upgrade
SAP S/4HANA, a LIMS or a software tool: validation should run with the project instead of holding up go-live at the end.
-
Implementation with a partner
You need someone on your side who steers and assesses the integrator's testing and validation.
-
Effort out of line with risk
Lots of paper in some places, too little solid evidence in others.
-
Changes take too long
Every change is treated like a small revalidation.
-
An inspection is coming
You want to know whether your evidence will hold.
-
Building up or short-handed
There's no CSV function or test process yet, or the lead role is vacant.
Services
- Business Process Analysis
- Requirements Engineering
- Risk Management
- Supplier Qualification
- Testing
- Infrastructure Qualification
- Security
- Data Governance
-
Computer system validation
Risk-based validation across the lifecycle, following GAMP 5 principles and focused on patient safety, product quality and data integrity.
-
Testing and validation on the client side
When a partner implements your system, such as an ERP or LIMS, I steer testing and validation from your side and assess the integrator's deliverables.
-
Change control and release management
An impact assessment sets the test scope for each change, instead of retesting every release from scratch.
-
Inspection readiness
I review your evidence before the inspection and show where the gaps are and how to close or justify them.
-
Independent review
A second, critical look at your validation deliverables, with specific findings rather than general remarks.
-
Interim lead and build-up
I lead your validation or test workstream for a defined period, or build a CSV function or test process with your team.
How I work
-
Risk-based
Effort follows the risk to patient, product and data, not a template.
-
Alongside the project
Validation and testing run with the project, not after it.
-
Use what exists
Supplier documentation and existing tests are used where they hold up.
-
Handover to your team
You get the documents, the decisions and the reasoning, enough to carry on yourselves.
Project phase
- Understand the process and requirements
- Assess the risks
- Define the controls
- Verify and release
Operation phase
- Assess and control changes
- Plan and test releases
- Review periodically
Background
- 15+ yearsin regulated environments: pharma, biotech, diagnostics, medical devices
- Co-authorin the ISPE GAMP Good Practice Guide: Testing GxP Systems (3rd Edition)
- From ERP to software toolsa range of GxP systems validated and tested
- ISTQBCertified Tester
Selected projects
- Established a company-wide test management process for SAP S/4HANA, including the first comprehensive Master Test Plan, and co-led the CSV workstream for SAP S/4HANA and SAP Solution Manager.
- Led an inspection readiness project for an SAP S/4HANA landscape.
- Delivered validation for a global LIMS implementation.
- Established risk-based software validation and built a three-person CSV team at a health technology company.
- Piloted agentic AI tooling in validation work.
Contact
Every engagement starts with a conversation.
Listen first, then assess
- You describe your situation in 20 minutes. I listen and ask questions.
- Afterwards I analyse what you've told me.
- You receive a short written assessment: where I would start and how I can support you.
The call and the assessment are free and without obligation.
Book a free introductory callPlease don't send confidential documents for the introductory call.