Computer System Validation

Data /Integrity App


 

According to both American FDA and UK MHRA, computer system validation is defined as “Confirmation by examination and provision of objective evidence that software specifications conform to user needs and intended uses, and that the particular requirements implemented through software can be consistently fulfilled”

Validation of computer systems is not a onetime event it periodic activity.

CSV should be performed by person other than those responsible for building system.


Purpose of CSV:

The purpose of the validation process is to provide a high degree of assurance that a specific process (or in this case computer system) will consistently produce a product (control information or data) which meets predetermined specifications and quality attributes.


Need of CSV:

FDA regulations mandate the need to perform Computer System Validation and these regulations have the impact of law.

 Having the evidence that computer systems are correct for their purpose and operating properly represents a good business practice.

 

All CSV activities should be documented with the following:

  • System inventory and assessment – determination of which systems need to be validated
  • User requirement specifications – clearly defines what the system should do, along with operational (regulatory) constraints
  • Functional requirement specifications – clearly defines how the system will look and function for the user to be able to achieve the user requirements.
  • Validation Plan (VP) – defines objectives of the validation and approach for maintaining validation status
  • Validation Risk assessments – analysis of failure scenarios to determine scope of validation efforts
  • Validation Traceability Matrix – cross reference between user and functional requirements and verification that everything has been tested
  • Network and Infrastructure Qualification – documentation showing that the network and infrastructure hardware/software supporting the application system being validated has been installed correctly and is functioning as intended
  • Installation Qualification (IQ) Scripts and Results – test cases for checking that system has been installed correctly in user environment
  • Operational Qualification (OQ) Scripts and Results – test cases for checking that system does what it is intended to do in user environment
  • Performance Qualification (PQ) Scripts and Results – test cases for checking that System does what it is intended to do with trained people following SOPs in the production environment even under worst case conditions
  • Validation Report – a review of all activities and documents against the Validation Plan
  • System Release Documentation – documents that validation activities are complete and the system is available for intended use.

“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

Popular posts from this blog

GxP Assessment & Categorization of Computerized System

Data Integrity Thread

Minimize Data Integrity issue