What Records are E-Records? A Process Control System Case Study Jeffrey Beck Manager, Quality Engineering Ortho-McNeil Pharmaceutical, Inc.

Slides:



Advertisements
Similar presentations
TEAs UserAdministration+ The paperless way to apply for access to TEA SE and its web applications Revised July 2006 [Click mouse to advance from slide.
Advertisements

Senior Verifier Update Robert Laird Administration and IT (VG363/389)
1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
ICH Q4B Regulatory Acceptance of Analytical Procedures and/or Acceptance Criteria (RAAPAC) Overview and Update Robert H. King, Sr. Office of Pharmaceutical.
0 Chicago, IL March 6 th, 2007 Use Case Requirements, Design and Standards Selection HITSP Use Case Requirements, Design and Standards Selection Date:
21 CFR Part 11 Regulatory Overview and What’s New with the FDA
The Acquisition / Payment Process
1 Exploring Acceptance and Legal Nature of eRecords Within a Paper-Based Framework Electronic Signature & Records Association November 14, 2012 Rafael.
Regulatory Compliant Performance Improvement for Pharmaceutical Plants AIChE New Jersey Section 01/13/2004 Murugan Govindasamy Pfizer Inc.
Target Electronics 27 th November Overview Current System is composed of many discrete units with separate processors that do not talk to each other.
PSU CS 106 Computing Fundamentals II Product Life Cycle & SW Product Life Cycle HM 9/3/2007.
Examine Quality Assurance/Quality Control Documentation
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
6  Methodology: DMAIC Robert Setaputra. PDCA / PDSA PDCA / PDSA is a continuous quality improvement tool. PDCA is introduced by Shewhart. PDSA is Deming’s.
Computer Systems & Software
Basics of Good Documentation Document Control Systems
Radiopharmaceutical Production
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
MethodGXP The Solution for the Confusion.
EDMR Electronic data submittal system Jeffrey A. Ewick, Section Chief Data and Information Services Section Electronic Discharge Monitoring Report.
Component-level testing – Equivalence partitioning, boundary value analysis, path testing Navigation testing – Testing navigation syntax and semantics.
Notebooks and Protocols
FDA Docket No. 2004N-0133 Themes for Renewal of 21 CFR Part 11 Rule & Guidance by Dr. Teri Stokes, GXP International
Student Education Service QUALITY ASSURANCE QAA Update HEFCE consultation on future of quality assessment arrangements QAA Quality Code Alignment - programme.
Document Control Basics of Good Documentation and
Continuing Professional Development Past, present and future Lorraine Osman Vice-President: South African Pharmacy Council Head of Public Affairs: Pharmaceutical.
Technology in Action Alan Evans Kendall Martin Mary Anne Poatsy Twelfth Edition.
Walter Conway, QSA 403 Labs, LLC Sneak Preview: What to Expect from PCI DSS v. 2.0  Changes  Clarifications  Guidance.
PwC 21 CFR Part 11 – A Risk Management Perspective Patrick D. Roche 07 March 2003, Washington D.C.
Massella Ducci Teri Italian approach to long-term digital preservation Policies for Digital Preservation ERPANET Training Seminar.
Part 11, Electronic Records; Electronic Signatures
Business and Information Technology Working Together for the Regulator Stephen Hord, Director of Product Development – UBmatrix.
I Power Higher Computing Software Development Development Languages and Environments.
Seminar 2 – Part 1 Managing Data to Improve Business Performance Ref: Chapter 3 of Turban and Volonino.
Technical Overview. Project Overview Document Library Document List Index TransmittalsPlanning.
Class Scheduler Team Members Bernard Battle Jerad Blake James Knoch Chris Louallen Lenora Pride.
Copyright © 2009 Intel Corporation. All rights reserved. Intel, the Intel logo, Intel Education Initiative, and the Intel Teach Program are trademarks.
WorkManager Concepts & Schema Course Outline The Old “Business Rules” Traditional LBNL CAD Method New “Business Rules” Engineering Data Management WorkManager.
Part 11 Public Meeting PEERS Questions & Responses The opinions expressed here belong to PEERS members and not the corporate entities with which they are.
What Records are E-Records? A Process Control System Case Study Jeffrey Beck Manager, Quality Engineering Ortho-McNeil Pharmaceutical, Inc.
TTI Performance Evaluation Training. Agenda F Brief Introduction of Performance Management Model F TTI Annual Performance Review Online Module.
12.2C: Project (Design/Implementation). Lesson objectives O have experience of using prototyping to create solutions for project work O be aware of the.
Project Chartering & Approval Process
FDA Part 11 Public Meeting Washington, DC June 11, 2004 Paul D’Eramo Executive Director Worldwide Policy & Compliance Management Quality & Compliance Services.
ISO DOCUMENT CONTROL. ISO Environmental Management Systems2 Lesson Learning Goals At the end of this lesson you should be able to: 
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
1 Splitting Available License Entitlements Audience: Authorized Business Partners and Avaya Module Scope: The process of how to split available (not yet.
Statement of Auditing Standard No. 94 The Effect of Information Technology on the Auditor’s Consideration of Internal Control in a Financial Statement.
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
1 Final Regulation Order for Truck and Bus Regulation California Environmental Protection Agency Air Resources Board November 20, 2014.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SAPRAA 5 Sept 2008 eCTD An overview of the full day presentation by Dr Olaf Schoepke at the SAAPI conference in July 2008.
InstantGMP MD/PRO Electronic Device History File Software for Manufacturing Medical Devices in compliance with 21 CFR Part 820 (Quality System Regulation)
Slide#: 1© GPS Financial Services 2008Revised 05/14/2009 cms 2 PR Rep-MasterEmployee ™ Cougar Mountain Software Professional Version.
SEMINAR ON, PRESENTED BY, POONAM Y AGHARA M – PHARM DEPT. OF PHARMACEUTICS AND PHARMACEUTICAL TECHNOLOGY L. M. COLLEGE OF PHARMACY AHMEDABAD.
ACR Appropriateness Criteria® Feedback and Commenting
Software Specification and Configuration Management
PLANNING AND DESIGNING A RESEARCH STUDY
Submission and Approval of Graduate Student Documents
BUSINESS HIGH SCHOOL-RECORD KEEPING
Structure–Feedback on Structure ED-2 and Task Force Proposals
FDA 21 CFR Part 11 Overview June 10, 2006.
STORYBOARD TEMPLATE
Statement of Auditing Standard No. 94
University of Kentucky E-IRB
Final Design Authorization
Require PO Overview when Submitting Invoices
Feasibility Report.
An overview of course assessment
Presentation transcript:

What Records are E-Records? A Process Control System Case Study Jeffrey Beck Manager, Quality Engineering Ortho-McNeil Pharmaceutical, Inc.

Objectives Discuss recent experiences in applying Part 11 guidance to a SCADA/PLC lyophilizer control system, with recipe management functions. Discuss recent experiences in applying Part 11 guidance to a SCADA/PLC lyophilizer control system, with recipe management functions. Provide feedback on: Provide feedback on: –Scope –Definitions/criteria for identifying electronic records –Records required by predicate rules

Recipe Management Overview Each recipe in the process control system is made up of several critical process parameters stored in a named file. Each recipe in the process control system is made up of several critical process parameters stored in a named file. Recipes are first approved through quality system (change control and electronic document management) before being entered and saved in the process control system. Recipes are first approved through quality system (change control and electronic document management) before being entered and saved in the process control system. The control system loads the recipe parameters from its recipe management system, not from the document management system. The control system loads the recipe parameters from its recipe management system, not from the document management system. The recipe parameters are printed to a paper report after the cycle begins, and this report is signed by the operator. The recipe parameters are printed to a paper report after the cycle begins, and this report is signed by the operator.

Recipe Issues Is the recipe in the process control system a required record at all? Is the recipe in the process control system a required record at all? –Some considered it equivalent to software. –Some considered it a part of the Master Production Record. Which record is being relied on to perform regulated activities? Which record is being relied on to perform regulated activities? –Some thought approval of the recipe document was the only regulated activity, others believed loading process parameters into a control system was also regulated.

Resolutions and Criteria The recipe in the process control system is managed as a discrete unit and is therefore a record (under (b)), distinct from the control software. The recipe in the process control system is managed as a discrete unit and is therefore a record (under (b)), distinct from the control software. Loading process parameters is a regulated activity. Both versions of the recipe (document management and process control system) are electronic records under Part 11. Loading process parameters is a regulated activity. Both versions of the recipe (document management and process control system) are electronic records under Part 11. Records used to perform regulated activities may also include stored, reusable inputs to process control and other automated systems. Records used to perform regulated activities may also include stored, reusable inputs to process control and other automated systems. In this case, the electronic recipes may be considered low impact as the likelihood of an undetected error is low. In this case, the electronic recipes may be considered low impact as the likelihood of an undetected error is low.

Conclusions and Comments The narrow scope for Part 11 defined in the current guidance is appropriate, and should be written into a revised regulation. The narrow scope for Part 11 defined in the current guidance is appropriate, and should be written into a revised regulation. Within this narrow scope, the definition of electronic records required by predicate rules would benefit from more detail, supported by some specific examples. Within this narrow scope, the definition of electronic records required by predicate rules would benefit from more detail, supported by some specific examples. The current definition should be refined to make clear that use for regulated activities may include electronic records used as inputs by computer systems. The current definition should be refined to make clear that use for regulated activities may include electronic records used as inputs by computer systems. There may also be a need to clarify which records are required in addition to those specifically identified in predicate rules. There may also be a need to clarify which records are required in addition to those specifically identified in predicate rules.