The key to successful compliance of a paperless workflow and approval environment is setting up the right security and access rights, and authenticating signatures effectively.
Objectives of the Presentation
Why Should you Attend
- To learn how to interpret and apply the requirements set forth by FDA in 21 CFR Part 11, a guidance for electronic records and signatures (ER/ES)
- To understand the implications of using ER/ES capability in the business process workflow
- To learn how to evaluate the cost-benefit of using ER/ES capability in FDA-regulated systems
- To understand how to mitigate any risks that emerge as a result of implementing ER/ES capability
- To be able to prepare users for the changes in work processes that will be required in using ER/ES
- To be able to identify and fill key roles and responsibilities required in the process of implementing ER/ES
- To learn how to prepare a rationalization for the use of ER/ES to satisfy potential FDA audit questions
- To learn how to work with FDA during an audit or discussion to ensure they are comfortable with the company's approach and methodology for implementing and supporting ER/ES capability
- To learn by examples how some companies have implemented ER/ES capability and discuss the rationale behind it, cost-benefit analysis conducted, risk assessment conducted and some of the outcomes, both positive and negative
The attendee will learn how to develop a standard approach to establishing and maintaining the use of ER/ES to handle records and approvals in an FDA regulated environment. There are specific best practices that should be considered before choosing to implement these capabilities and operate in a "paperless" environment, and these will be discussed. We will discuss the pros and cons for using ER/ES, and talk about the ramifications of choosing to do so. The attendee will be prepared to make a determination about applying ER/ES capabilities in their workplace, and will be able to implement the best practices for maintaining ER/ES in a compliant manner.
We will touch on those areas that are critical to meeting the requirements set forth in FDA's 21 CFR Part 11, including security and newer technologies that are emerging for capturing, analyzing, storing and reporting information for decision-making purposes.
It's important to look at what are some of the threats and challenges of using ER/ES, and what methods you can use to mitigate these. Similarly, it is important to identify opportunities that might help companies decrease the cost of compliance and improve operational efficiencies and effectiveness through the use of ER/ES.
Who can Benefit
- FDA's 21 CFR Part 11 guidance for electronic records and signatures
- Pros and cons of implementing ER/ES capability
- Cost-benefit analysis of implementing ER/ES capability
- Risks associated with ER/ES implementation and potential mitigation
- Organizational change management required to successfully implement and using ER/ES capability
- Key roles and responsibilities required in the process of implementing, using and supporting systems with ER/ES capability
- Integration of ER/ES capability in existing applications
- Documenting ER/ES rationalization
- Preparing for an FDA audit that will include scrutiny of applications with ER/ES capability
- Examples of companies that have implemented ER/ES capability and discuss the rationale behind it, cost-benefit analysis conducted, risk assessment conducted and some of the outcomes, both successful and unsuccessful Compliance and Audit Managers
- Information Technology Analysts
- Information Technology Developers and Testers
- QC/QA Managers and Analysts
- Clinical Data Managers and Scientists
- Analytical Chemists
- Laboratory Managers
- Automation Analysts
- Computer System Validation Specialists
- GMP Training Specialists
- Business Stakeholders/Subject Matter Experts
- Business System/Application Testers
- This webinar will also benefit any consultants working in the tobacco or life science industries who are involved in computer system implementation, validation and compliance.