Www.methoda.com MethodGXP The Solution for the Confusion.

Slides:



Advertisements
Similar presentations
How to Validate a Vendor Purchased Application
Advertisements

Building a Cradle-to-Grave Approach with Your Design Documentation and Data Denise D. Dion, EduQuest, Inc. and Gina To, Breathe Technologies, Inc.
PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
Software Quality Assurance Plan
21 CFR Part 11 course syllabus / Ilan Shaya 21CFR Pat 11 | Objective | Audience |Course Outline | Details 15-16/7/2013.
Medical Device Software Development
Radiopharmaceutical Production
What is GARP®? GARP® is an Acronym for Generally Accepted Recordkeeping Principles ARMA understands that records must be.
Audit of IT Systems SARQA / DKG Scandinavian Conference, October 2002, Copenhagen Sue Gregory.
Regulatory Compliant Performance Improvement for Pharmaceutical Plants AIChE New Jersey Section 01/13/2004 Murugan Govindasamy Pfizer Inc.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Define ● Deliver ● Sustain Sundar Chellamani Technical Director SysComm Project Management Ltd.
Overview Lesson 10,11 - Software Quality Assurance
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Configuration Management
CDRH Software Regulation
Software Configuration Management
Computer Systems & Software
Fundamentals of ISO.
DRAFT Richard Chandler-Mant – R Consultant The Challenges of Validating R Managing R in a Commercial Environment.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
S/W Project Management
SQA Architecture Software Quality By: MSMZ.
Introduction to ISO New and modified requirements.
Evolving IT Framework Standards (Compliance and IT)
Rocky Mountain RAPS Process Validation Presentation 6/7/06 By Clay Anselmo.
Basics of OHSAS Occupational Health & Safety Management System
MethodQMS Quality Management System.
Software System Engineering: A tutorial
FDA Docket No. 2004N-0133 Themes for Renewal of 21 CFR Part 11 Rule & Guidance by Dr. Teri Stokes, GXP International
ISO 9000 & TOTAL QUALITY ISO 9000 refers to a group of quality assurance standards established by the International Organization for Standardization.This.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
The IT Quality Assurance FDA Validation Specialists Phone: 877-MGD-TEST ( ) n n n n Web Site:
FDA Public Meeting on Electronic Records and Signatures June 11, 2004 Presentation of the Industry Coalition on 21CFR Part 11 Alan Goldhammer, PhD Chair.
Part 11, Electronic Records; Electronic Signatures
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Validation Copyright © 2004 Yokogawa Validation. Copyright © 2004 Yokogawa Page 2 Validation ProjectStandard Project > Validation.
Design Documentation Clint Kehres, Brian Krouse, Jenn Shafner.
Joel Gerber Zachary Reaver Kurt Schilling.  Provides physical proof of development  Maintains product design knowledge base  Meets government and corporate.
Part 11 Public Meeting PEERS Questions & Responses The opinions expressed here belong to PEERS members and not the corporate entities with which they are.
The world leader in serving science Validation and Qualification Overview Mike Garry Software Product Manager Spectroscopy Software Platform Team.
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
Pharmaceutical Quality Control & current Good Manufacturing Practice
ERT 421 Good Manufacturing Practice for Bioprocess Engineering Test 1: answer scheme.
InstantGMP™ MD Electronic Device History File Software for Manufacturing Medical Devices.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
SEMINAR ON, PRESENTED BY, POONAM Y AGHARA M – PHARM DEPT. OF PHARMACEUTICS AND PHARMACEUTICAL TECHNOLOGY L. M. COLLEGE OF PHARMACY AHMEDABAD.
21 CFR PART 11.
FDA 21 CFR Part 11 Compliance
Medical Device Software Development
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Международные требования к использованию электронных систем в клинических исследованиях Timur Galimov, CTO.
Project Quality Management
Raechel Huebner Ruthanne Sherer
Pharmaceutical Quality Control & current Good Manufacturing Practice
Software and Systems Integration
Fundamentals of ISO.
Software Requirements
Engineering Processes
Fit-for-Purpose Program: Solving Problems with the Validation of Legacy Systems Joseph Schenk QA Edge, Inc. (302) x11
בקרה תוך שימוש ב 21CFR Part 11 / אילן שעיה סמארט לוג'יק
FDA 21 CFR Part 11 Overview June 10, 2006.
How to conduct Effective Stage-1 Audit
Engineering Processes
Software Reviews.
Computer System Validation
Radiopharmaceutical Production
Presentation transcript:

MethodGXP The Solution for the Confusion

Methoda Computers Ltd 2 Company’s Background  20 years specializing in Quality Assurance, Software Engineering and IT Management  10 years specializing in Software Validation  60 Senior Consultants (at least 10Y experience)  Leading methodology and knowledgebase for software engineering and IT management  Quality certification for ISO-9001  Proven methodology for the FDA regulations

Methoda Computers Ltd 3 The Challenges  Complexness to achieve qualitative product and processes  The need to be compliant with different standards and regulations (CE, FDA, ISO, etc)  Many guides for similar and complementary requirements  Much confusion and unclear instructions  Potential for duplication in documents, processes and activities

Methoda Computers Ltd 4 Too many Guides Design Control Guidance 21 CFR Part 11 General Principle of SW Validation OTS Software GeneralPrinciples of Process Validation General Principles of Process Validation ISO 9000 ISO Pre-market Submissions GAMP 4 cGMP-QSR

Methoda Computers Ltd 5 Main Requirements  "Any software used to automate any part of the device production process or any part of the quality system must be validated for its intended use..“  "Software validation activities may occur both during, as well as at the end of the software development life cycle to ensure that all requirements have been fulfilled."  "A conclusion that software is validated is highly dependent upon comprehensive software testing, inspections, analyses, and other verification tasks performed at each stage...“  “Establish DOCUMENTED EVIDENCE that provides a HIGH DEGREE of assurance that a computer system or software will CONSISTENTLY perform within its predetermined specifications and quality attributes.”

Methoda Computers Ltd 6 21 CFR Part 11- More requirements and challenges  “.. computer systems used to create, modify, and maintain electronic records and to manage electronic signatures are also subject to the validation requirements.“  “… FDA will consider electronic records to be equivalent to paper records, and electronic signatures equivalent to traditional handwritten signatures.”  Ensure the authenticity, integrity, and, when appropriate, the confidentiality of electronic records.... ensure that the signer cannot readily repudiate the signed record as not genuine.”

Methoda Computers Ltd 7 Summary of Challenges  Overload of information and instructions  Compliance with the regulations is essential  Advanced methodology is required for reduced risks and business efficiency Pragmatic solution is required!

Methoda Computers Ltd 8 Pragmatic solution - A risk based approach  GAMP IV A risk based approach will be acceptable, but how do you legally justify your risk assessment?  “General Principles of Software Validation, Draft Guidance Version 1.1” “…The resultant software validation process should be commensurate with risk associated with system, device or process”

Methoda Computers Ltd 9 Pragmatic solution - A risk based approach  Pre-Market: “..risk estimation for software products should be based on the severity of the hazard resulting from failure...”  GPOSV: "The magnitude of software validation effort should be commensurate with the risk associated with the device….“  GAMP 4: The categories are based on the increasing risk of system failure with the progression from standard SW and HR to custom…”

Methoda Computers Ltd 10 Methoda’s Risk Based Approach Pragmatic Solution Policy Risk Based Approach Severity & Category Validation Efforts Part 11 Priorities & Efforts

Methoda Computers Ltd 11 Methoda’s Risk Based Approach  Risk will be determined by assessing:  The Level of Concern to determine the level of the validation activities  The complexity/category of the system to determine the validation deliverables

Methoda Computers Ltd 12 Criteria for the Appropriate Solution  Business efficiency - Quality product and development process  Receiving the right information (and terminology) to support submissions  Integration of all regulatory requirements  Elimination of duplication- globally aligned system eliminates unique local requirements  Cost effective solution

Methoda Computers Ltd 13 MethodGxP - The Solution  Tool-Kit that is ready for implementation  Single Standard Quality System that complies with the QSR, ISO, and CE Mark  Comprehensive procedural framework  Solution life cycle supports good engineering practice  Policy that supports compliance with requirements and regulations

Methoda Computers Ltd 14 MethodGxP - The Solution  Comprehensive Risk Management process to minimize the requirements  Efficiency and NO duplications DO IT RIGHT the FIRST TIME

Methoda Computers Ltd 15 Validation Tasks  System Mapping  Gap Analysis  Policy  Work Plan for closing the gaps  Validation Deliverables: VP, IQ, OQ, PQ, TM, VSR and vendor documented evidences  Maintenance of system  Periodic Review

Methoda Computers Ltd 16 Validation Life Cycle User Requirements Functional Specifications Design Qualification Performance Qualification Operational Qualification Installation Qualification Installation System Validation Plan Validation Summary Report

Methoda Computers Ltd 17 Example of GXP Validation Folder

Methoda Computers Ltd 18 Example of Templates  Gap Analysis Gap Analysis  Systems Validation Policy Systems Validation Policy  Computerized System Validation Program (CSVP) Computerized System Validation Program (CSVP)  Installation Qualification (IQ) Installation Qualification (IQ)  Operational Qualification (OQ) Operational Qualification (OQ)  Performance Qualification (PQ) Performance Qualification (PQ)  User Requirements Specification (URS) User Requirements Specification (URS)  Traceability Matrix (TM) Traceability Matrix (TM)  Validation Summary Report (VSR) Validation Summary Report (VSR)

Methoda Computers Ltd 19 Acceptable Evidence  Documented evidence for Quality System in the development process  Documented evidence for good engineering practice (Specifications, designs, reviews, testing, etc)  For critical systems, a vendor audit may be required

Methoda Computers Ltd 20 Process Recap - MethodGxP Advantages  Cost effective solution  Simple and efficient model  Single Checklist  Easy to understand - easy to use  Compliant with the regulations  Comprehensive solution from concept to maintenance

Methoda Computers Ltd 21 Process Recap - MethodGxP Advantages  A proper Implementation of MethodGxP results in:  Improved system quality  Meeting Goals, Schedule and Budget  Improving Cost/Performance  Control & Management  Satisfied User

Methoda Computers Ltd 22 GxP Implementation Plan for the pharmaceutical market Activity Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 23 Phase 1 - Gap Analysis  Determining the actions needed to bring the system into compliance with established software validation and 21 CFR Part 11 regulations  Input: Regulation requirements and systems’ gaps  Output: Action items to close the gaps – Gap analysis template Gap analysis template Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 24 Phase 2 - Policy  Based on Risk Based Approach  Specifies all validation activities for all regulated computer systems  Input: FDA requirements, good engineering practice  Output: Policy documentPolicy document Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 25 Phase 3 - Work Plan  Detailed action items for each system with priorities and required recourses  Input: Gap analysis and Policy  Output: Work plan Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 26  Deliverables and Activities:  Validation Plan Validation Plan  User Requirements Specification User Requirements Specification  Installation Qualification Installation Qualification  Operational Qualification Operational Qualification  Performance Qualification Performance Qualification  Testing Execution  Traceability Matrix Traceability Matrix  Validation Summary Report Validation Summary Report  Input: Policy  Output: Validated systems Phase 4 - Validation Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 27 Phase 5 - Training  To ensure reliable system operation  To ensure reliable procedures operation  Input: User guide, SOPs  Output: Trained users GAP Analysis Policy Work Plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 28 Phase 6 - Software Validation Maintenance  Any change to equipment and computer systems that may affect the system’s validation status should follow documented procedures and should be formally approved  Input: Changes  Output: Validated systems Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 29 Phase 7 - Periodic Review  Periodic reviews will be performed and documented for each validated system to ensure its validation status is still current  Input: System status  Output: Validated systems Gap analysis Policy Work plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 30 Step 8 - System Retirement  Disposition of system software  Disposition of system documentation  Migration (if necessary) or archiving of data  Input: Retired System  Output: Historical data that can be retrieved Gap analysis Policy Work Plan Validation Training Software Validation maintenance Periodic review System retirement

Methoda Computers Ltd 31