Risk-based Approach to CSV and Maintaining a System in a Validated State
Live Webinar | Carolyn (McKillop) Troiano | Nov 29, 2022 , 01 : 00 PM EST | 90 Minutes
We will explore the validation of computer systems regulated by the FDA. We will cover multiple approaches, techniques, and tools that can improve the efficiency and effectiveness of validation activities, particularly focused on a risk-based approach. You will go through the phases of validation, including deliverables and FDA requirements. You will also learn about 21 CFR Part 11, FDA’s guidance for electronic records and signatures, and for FDA’s guidance on Data Integrity.
Computer system validation has been regulated by FDA for more than 30 years, as it relates to systems used in the manufacturing, testing, and distribution of a product in the pharmaceutical, biotechnology, medical device, or other FDA-regulated industries. The FDA requirements ensure thorough planning, implementation, integration, testing, and management of computer systems used to collect, analyze and/or report data.
Electronic records and electronic signatures (ER/ES) came into play through guidelines established by FDA in 1997 and disseminated through 21 CFR Part 11. This code describes the basic requirements for validating and documenting ER/ES capability in systems used in an FDA-regulated environment.
In the early 2000s, FDA recognized they could not inspect every computer system at every regulated company and placed the onus on industry to begin assessing all regulated computer systems based on risk. The level of potential risk, should the system fail to operate properly, needed to be the basis for each company’s approach to developing a validation approach and rationale as part of the planning process. System size, complexity, business criticality, GAMP 5 category, and risk rating are the five key components for determining the scope and robustness of testing required to ensure data integrity and product safety. In addition, the requirements should be evaluated in terms of potential risk, should they fail. Each requirement is then tested accordingly. The greater the risk, the more robust the testing.
FDA’s recent focus on data integrity during computer system validation inspections and audits has brought this issue to the forefront of the importance of compliance with systems used in regulated industries. These include all systems that “touch” products, meaning they are used to create, collect, analyze, manage, transfer and report data regulated by FDA. All structured data, including databases, and unstructured data, including documents, spreadsheets, presentations, and image files, audio and video files, amongst others, must be managed and maintained with integrity throughout their entire life cycle.
We will explore the best practices and strategic approach for evaluating computer systems used in the conduct of FDA-regulated activities and determining the level of potential risk, should they fail, on data integrity, process and product quality, and consumer/patient safety. We will walk through the System Development Life Cycle (SDLC) approach to validation, based on risk assessment, and will also discuss 21 CFR Part 11 and the importance of managing electronic records and signatures appropriately.
We will also walk through the entire set of essential policies and procedures, as well as other supporting documentation and activities that must be developed and
followed to ensure compliance. We will provide an overview of practices to prepare for an FDA inspection, and will also touch on the importance of auditing vendors of computer system hardware, software, tools and utilities, and services.
Finally, we will provide an overview of industry best practices, with a focus on data integrity and risk assessment that can be leveraged to assist in all your GxP work.
Why Should You Attend:-
We have used our real-world experience to design a computer system validation course that not only meets FDA, ICH, and Eudralex expectations for risk-based validation but also prepares you to implement these practices in your company.
We’ll talk about the risk-based approach and how that would work for a regulated system. You can learn to evaluate risk potential at the requirement and system levels. We’ll also discuss Computer Software Assurance (CSA) as an approach for validating systems that are based on risk and on critical thinking. Learning about how to evaluate testing that will be streamlined and will best assure the system will do what it purports to do and will be suitable for the intended use.
We are focused on your comprehension and application of the CSV techniques that will result in efficient, effective, and inspection-ready validation initiatives.
Who Should Attend:-