What is Project Validation Plan (PVP) in Computer System Validation?


In Earlier post we understood what is Design Specification, Its Type & Elements in Computer System Validation.

Now in this article we are going to understand what is project validation plan(PVP) & What Content should include in PVP?.


What is Project Validation Plan(PVP):

CSV processes should be guided by a good plan that is created before the project starts. Project Validation Plan should be developed during this planning phase of the SLC

Validation plan will define the objectives of the validation, the approach for maintaining validation status over the full SDLC & satisfy all regulatory policies & industry best practices (e.g., GAMP 5).

It also defines roles and responsibilities along with the most important part, the Acceptance Criteria.

A project validation Plan shall be created to identify and define the Validation strategy and deliverables generated as an outcome of the execution of the strategy.

The PVP should be project specific and describes the approach for the validation of the system, required activities and deliverables

The validation plan will be created by people who have a good knowledge of the technology involved (i.e., informatics systems, instruments, devices, etc.) and serve to minimize the impact of the project on day-to-day lab processes.

A Validation Plan should include:

•    Deliverables (documents) to be generated during the validation process

•    Resources, departments & personnel to participate in the validation project

  •   Testing Approach – Defines the types of data that will be used for testing, along with the kind of scenarios that will be tested.

•    Time-lines for completing the validation project

•    Acceptance criteria to confirm that the system meets defined requirements

   •   Testing Team and Responsibilities – Lists the members of the validation team, along with their roles and responsibilities in the validation process.

•    Compliance requirements for the system, including how the system will meet these requirements


The plan should be written with an amount of detail that reflects system complexity.

The plans should be approved, at a minimum, by the System Owner and Quality Assurance. Once approved, the plan should be retained according to your site document control procedures.


Following deliverables must be generated as a result of execution of these planning phase/stages-

•       Project Plan (schedule)

•       Change control Approval

•       Updated Inventory List

•       GxP Assessment & system Categorization checklist

•       System level risk assessment

•       Electronic Record & Electronic signature Assessment

•       Vendor survey form (if applicable)

•       Vendor Audit report (if applicable)

•       SOW/NDA ( if applicable)

•       User Requirement Specification (update if required)

•       Project Validation Plan/Validation Master Plan

•       Updated Inventory List


“Trust but Verify “ Ronald Reagan

 

Across the internet, there are millions of resources are available which provide information about Everything.

 

If you found all content under one roof then it will save your time, effort & you will more concentrated on your important activity.

Data Integrity App


 

Our Data integrity app will helpful for understanding what Data integrity & CSV really means & How 21 CFR Part 11, EU Annex 11 & other regulatory guidelines affects in pharmaceutical Industry.

 

Data Integrity App Include 

- Basic Data Integrity Concepts

- ERES & Its Requirement

- CSV & Its best practices 

- Mock Inspection and General Q&A

- Checklist for inspection

- Inspection Readiness

- Useful SOP’s

- Stay Regulatory Compliant.

 

“Stay One Step Ahead in Pharma IT Compliance” 


Data Integrity App Link:


https://play.google.com/store/apps/details?id=com.innovativeapps.dataintegrity

 

Try our "Data Integrity" app which helps you to better understand current regulatory agencies thinking on Data Integrity & CSV.


Comments

Post a Comment

Popular posts from this blog

What is CSV, Its Need, Purpose & Benefits in pharma Industry.

Image
History of CSV:  The concept of validation was derived from engineering principles of validation of mechanical system that has been extended to the software industry. To extend it further during mid-1970’s, Ted Byers and Bud Loftus, two Food and Drug Administration (FDA) officials first proposed the concept of validation in order to improve the quality of pharmaceuticals (Agalloco 1995).  In 1987 the FDA published a document entitled ‘FDA Guidelines on General Principles of Process Validation’.  It state that  "Process validation is establishing documented evidence which provides a high degree of assurance that a specific process will consistently produce a product meeting its predetermined specifications and quality attributes."   Feeling the necessity of Validation, FDA published a guide to the inspection of Computerized Systems in Pharmaceutical Processing, also known as the ‘bluebook’ (FDA 1983).  For MHRA this is Annex 11 of the EU GMP regulations (EMEA 19
Read more

GxP Assessment & Categorization of Computerized System

Image
The first stage of whether a system requires a validation is to identify whether the system has a GxP impact. The result of the GxP Assessment and system Category checklist decided whether Validation required for computerized system. If Outcome is “GxP Applicable” then follow Computer system validation procedure and other risk assessment for validating the system. All systems which handle data or processes which fall under the impact of GxP or any other regulatory requirements must be validated Determine whether the application has been validated elsewhere you in organization. The amount of work required may be significantly reduced by referring some of the deliverables in as in state or with slight changes. The details must be addressed in the change control. If required any “Non GxP Applicable “systems that process data critical to operations of the business such as those involving financial, certain personal data etc. Quality assurance, IT, CSV responsibility person, HOD of
Read more