Dr. D. Marcozzi Head of Clinical and CSV QA dept. of SIGMA-TAU

Presentazione sul tema: "Dr. D. Marcozzi Head of Clinical and CSV QA dept. of SIGMA-TAU"— Transcript della presentazione:

1 Dr. D. Marcozzi Head of Clinical and CSV QA dept. of SIGMA-TAU
Riunione Gruppo GCP Qual è il Processo della Computer System Validation? Dr. D. Marcozzi Head of Clinical and CSV QA dept. of SIGMA-TAU Milano, 31 marzo, 2005 Q

2 Parleremo di: Q CONVALIDA FORNITORI Analisi e Gestione del RISCHIO
Nuova visione delle CONVALIDE Q

3 Cos’è la CONVALIDA? Si si …un bel vestito…. Q

4 Cos’è la CONVALIDA? Q

5 Mi dicono che avrei fatto una CONVALIDA??
Cos’è la CONVALIDA? Mi dicono che avrei fatto una CONVALIDA?? Q

6 Cos’è la CONVALIDA? O meglio…………. Q

7 Che cos’è la Computerized System Validation (CSV)
Q

8 Primo: cos’è un Computerized System?
Personnel Software Documentation Instrument Hardware Control System Operating Environment Procedures Infrastructure Q

9 Validation is…. Q “Establishing documented evidence which provides a
high degree of assurance that a specific process will consistently produce a product meeting its pre-determined specifications and quality attributes” Q

10 Current Validation is the entire procedure of gathering documented evidence that a computer-related process or a system performs according to its intended function reliably and consistently throughout its life. Q

11 Le parole “CHIAVE” Q Documented Process/system Pre-Determined
Quality Attributes Entire Procedure Reliably and consistently Life Q

12 The life cycle concept of Computer Validation
Validation is a PROCESS, not an event Validation activities span the entire System Life Cycle: Planning Requirements Analysis Design Implementation Testing Acceptance On going Retirement Q

13 Planning and Implementation A Life cycle approach
Requirements Maintenance System Selection Operation Specify & Design Documentation User Qualification Build Supplier Testing Q

14 Planning and Implementation A Life cycle approach
URS PQ FS OQ DS IQ System Build Q

15 Planning and Implementation A Life cycle approach
Validation Plan Specifications URS, FS, DS (required) Test Planning (IQ,OQ,PQ) Doc. come testare il sistema Testing Test e risultati Review Validation Report Q

16 Validation activity and “life cycle” COSTRUCTION & CODE REVIEW
PROJECT ACTIVITY USER REQUIREMENTS FUNCTIONAL SPEC. HW E SW DES. SPEC. SW MODULE DES. SPEC. MECH. & ELECTRIC SPEC. HW MANUF. & ASSEMBLY CODE SW MODULES EQUIP. MANUF. & ASSEMBLY HW TESTING SW MOD.& INTEGR. TESTING EQUIP TESTING HW, SW, EQUIP. INSTALL. HW ACCEPTANCE TESTING SYSTEM ACCEPTANCE TEST. MAINTENANCE CHANGE CONTROL LIFE CYCLE PHASE PLANNING & SPECIFICATION DESIGN CONSTRUCTION TESTING INSTALLATION ACCEPTANCE TESTING OPERATION VALIDATION ACTIVITY VALIDATION PLAN SUPPLIER AUDITS SPEC. REVIEW DESIGN REVIEW COSTRUCTION & CODE REVIEW MONITOR SUPPLIER IQ OQ PQ VALIDATION REPORT ONGOING OPERATION Q

17 Validation Scope and Effort
should be commensurate with impact and value of data, process, results. . . size and complexity of the system and how critical it is in your routine and non-routine operations Q

18 Q Tanto più un sistema è critico e complesso tanto maggiore
sarà lo “sforzo” di convalida…quindi… Q

19 Sistemi Be-spoke Sistemi Customizzati Sistemi Standard Q

20 Basic Approach to Validation
Validation is a process, not an event Planning activity should be performed as a Team Keep the validation process under control Q

21 Le finalità….da GCP Qualora si avvalga di sistemi elettronici di elaborazione dei dati e/o sistemi di inserimento a distanza per la gestione dei dati relativi alla sperimentazione, lo Sponsor…. Garantire e documentare che il sistema elettronico per l’elaborazione dei dati sia conforme ai requisiti di completezza, precisione, affidabilità stabiliti dallo Sponsor e che questi siano conformi alle caratteristiche prefissate (cioè Validazione) Q

22 Le finalità Validating Data Validating the System handling the Data Q

23 Nel 1999… l’FDA Q A L C O A Pubblica una nuova Guidance for Industry
“Computerized System Used in Clinical Trials” Per essere accettabili, i dati debbono soddisfare certi elementi fondamentali di qualità se raccolti e registrati elettronicamente o su carta I dati debbono essere: ttribuibili (Source & Recorder are Known) eggibili (Human readable) ontemporanei (Recorded when observed) riginali (Honest data/not fraud) ccurati (Correct, repeatable results) A L C O A Q

24 ALCOA Q

25 Ed ora… gli attori… FORNITORE CLIENTE Q

26 CLIENTE FORNITORE Q

27 CLIENTE IT USER QA Q

28 FORNITORE COMMERCIALE e…… Q

29 According to specific rules or guidelines defined for each environment
QA Q

30 Il peso del QA…. IT QA Q

31 Il peso del QA…. Q QA IT Requisiti Regolatori Requisiti di Processo
Requisiti Tecnici QA IT Pianificazione e Testing Qualifica dei fornitori Qualità della documentazione Q

32 Il QA… ovunque nella CSV
Valutazione Fornitori Risk Assessment Definizione Requisiti Utente Definizione delle politiche di convalida Piani e test di convalida Revisione ed Approvazione dei documenti di convalida Q

33 Il QA… ovunque nella CSV
Approvazione dei cambiamenti Revisione ed Approvazione delle SOPs di convalida e CSV generali Audit periodici Punto di riferimento normative CSV Q

34 E le SOPs? Q QA Training Vendor Evaluation
Gestione Documentazione di Convalida Change Control Configuration Management Problem Reporting Security Back-up Restore Archiving Clinical Data Maintenance Disaster Recovery/Business Continuity Periodic Review QA Q

35 FORNITORE COMMERCIALE e…… Q

36 Planning and Implementation A Life cycle approach
URS PQ FS OQ DS IQ System Build Q

37 Evaluation should preferably be derived from a reliable audit of the software developer (supplier), performed by the end user’s organization or a trusted and competent third part. Q

38 Da GMP….. Q ...Validation should be considered as part of the complete
life cycle of a computer system. This cycle includes the stages of planning, specification, programming, testing, commissioning, documentation, operation, monitoring and modifying… (by supplier!). The software is a critical component of a computerized system. The user of such software should take all reasonable steps to ensure that it has been produced in accordance with a System of Quality Assurance. Q

39 CS Validation Documents
Client responsibility Supplier responsibility Planning GAMP Specifications Testing Validation Summary On-Going Test Plan Design Spec. Functional Spec. Quality and Project Plan Factory/Site Acceptance Test Master Index Validation Report. Report IQR, OQR, PQR Audit Report Validation Plans Validation Master Plan User Requirement Specifications SOPs Protocolli DQ, IQ, OQ, PQ User Manuals Q

40 Why do we have to audit the Suppliers?
The primary purpose of an audit is to assess the controls, procedures, and practices which are in place for the development and maintenance of a product Is a form of review that provides confidence concerning the validity and accuracy of a product or process now and in the future Audits should be viewed as a learning experience and should be conducted as a cooperative effort Q

41 SW Supplier Evaluation
Intent “To ensure that the supplier produces a quality product, and to obtain information to plan computer validation activities” “Tools” Collection of available information Request for Information (questionnaire) Audit Follow up Q

42 Supplier Evaluation Tools
RISKS EVALUATION THROUGH REFERENCES EVALUATION THROUGH EXPERIENCES REQUEST FOR INFORMATION 3RD PARTY AUDIT SPECIFIC FIRM AUDIT COSTS Q

43 Supplier Qualification model
Site Audit Telephone Audit SYSTEM RISK CATEGORY EVALUATION COST Request for Information (RFI) Information from other companies or from market Q

44 Check…Independence of SW Validation
Validation activities should be conducted using the basic quality assurance precept of “independence of review”. Self-validation is extremely difficult; an independent review is always better. Q

45 Check…Independence of SW Validation
Computer system validation should be performed by persons other than those responsible for building the system. Q

46 Validation: Client Responsibility !
Manufacturer has flexibility in choosing how to apply the validation principles, but retains ultimate responsibility for demonstrating that the software has been validated. PLANNING Normative Guidelines Q

47 Client Responsibility !
Client with regulatory responsibility needs to assess the adequacy of the software developer’s activities and determine what additional efforts are needed to establish that the software is validated. Q

48 Supplier selection (and supplier) is important
...but Validation Responsibility is always on the Client’s side Q

49 Validated Packages don’t exist!!
Supplier may provide a “Validation Package”, showing that the standard version of the product has been validated “in Factory” Client has to perform an “on-Site” Validation Q

50 Q

51 Quindi…. Q La validazione è una nostra responsabilità
Si deve Validare nel nostro “ambiente” Non è una responsabilità del Fornitore del sistema I sistemi forniti (anche quelli più standard) sono validabili, da validare e non già validati Q

52 Prima Verificare!!! Dopo e sempre Validare!!!
Quanto più il fornitore è affidabile…di QUALITA’ Tanto meno sforzo di convalida dovremo pianificare Prima Verificare!!! Dopo e sempre Validare!!! Q

53 Solo un accenno…. prendiamo spunto dalla realtà!
Ora parliamo di RISK MANAGEMENT…. RISK ANALYSIS….. Solo un accenno…. prendiamo spunto dalla realtà! Q

54 Q

55 Q

56 Da FDA…. Q Pharmaceutical CGMPs for the 21st century
A Risk-Based Approach Final Report september 2004 In August 2002, FDA announced a significant new initiative, Pharmaceutical Current Manufacturing Practices (CGMPs) for the 21st Century, to enhance and modernize the regulation of pharmaceutical manufacturing and product quality for veterinary and human drugs…. Objective: Encourage implementation of risk-based approaches that focus both industry and Agency attention on critical areas Q

57 Da FDA…. Q 21 CFR Part 11 Guidance…
Whit the issuance in 2003 of the guidance for industry part11, Electronic Records, Electronic Signature- Scope and Application, many barriers to scientific and technological advances were removed, and the use of risk-based approaches to managing computer systems is encouraged. Q

58 Risk Analysis / Computer Validation
Protect against the risks to patient safety Maximize the business benefits Help to determine the extent of validation Give a rationale to justify Validation approach in case of Inspection Concentrate the validation effort Q

59 A Good Start Perform Assessment
Dove siamo? Da cosa cominciamo? Dove vogliamo andare? Q

60 Risk Analysis: the Value
The more you know about your computer system Test The more you focus the validation Better you will use your resources…. and money! Q

61 Nuovo approccio alle Convalide….
Q

62 Good Automated Manufacturing Practice
Nel 1990 GAMP… Nasce nell’ambiente GMP Good Automated Manufacturing Practice Scopo della linea-guida è quello di assistere le aziende farmaceutiche, biotecnologiche, medical devices nell’implementazione di sistemi automatizati validati e compliant con i requisiti normativi Q

63 Q …nuove GAMP… 2001 Più attenzione al Processo!
Le nuove GAMP coprono tutti i requirements GMP, GCP, GLP e GDP Si potrebbero chiamare GA “M-C-L-D” P Più attenzione al Processo! Q

64 Nuovo approccio alle Convalide….
Q

65 Da… Performance Process A….. QUALIFICATION ! Q

66 FINE….. Grazie per la PAZIENZA!! Q