Life Sciences

How Much System Access Should We Give An FDA Inspector?

fda-inspection

 

On Thursday, April 23, 2015, we delivered a webinar on 21 CFR Part 11, based on a recent blog series. During the Q&A session at the end, someone asked the following question:

Life Sciences - How Artificial Intelligence Can Enhance the Clinical Data Review and Cleaning Process
How Artificial Intelligence Can Enhance the Clinical Data Review and Cleaning Process

This guide analyzes how artificial intelligence – including machine learning – can be used by pharmaceutical and medical device companies to improve the clinical data review and cleansing process.

Get the Guide

The Scope section requires access to electronic records and signatures (ER/ES) at all times. What if the electronic system used by a company is so complex that an FDA inspector couldn’t navigate by himself in it and would require someone from the company to retrieve any ER/ES? What is your experience on this? 

In our experience, FDA inspectors do not access systems themselves (and you generally wouldn’t want them to, since you want to limit what you share with them to the specific scope of their audit). Instead, they usually ask someone to demonstrate compliance within the system. During an audit, a reasonable amount of time is usually given to produce requested materials or demonstrate compliance.

On a related note, the most effective way to ensure a smooth audit is to maintain documents/records in “audit ready” condition, which requires establishing and adhering to record storage and retention procedures. Companies should also establish and maintain policies and procedures related to preparing for and conducting audits.

If you have any comments or follow-up questions on this topic, we’d love to hear from you. To see what other questions were asked during the webinar, click here.

About the Author

As the Head of Validation in Perficient’s life sciences practice, Sally Miranker is responsible for overseeing the Computer System Validation (CSV) methodology, System Development Life Cycle (SDLC), and all project-related validation activities. She has over 20 years of experience in the industry with almost a decade focused on implementing computer systems within regulated environments. Her knowledge and experience contribute to her ability to ensure that Perficient’s internal and client systems are implemented effectively, in compliance with internal procedures and external regulations, and following best industry practices. Prior to joining the company in 2009 via the acquisition of BioPharm Systems, Sally held a Siebel Systems Analyst position at Amylin Pharmaceuticals.

More from this Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to the Weekly Blog Digest:

Sign Up