Sunday, Sep 05th

Last update10:35:17 AM GMT

Headlines
You are here Compliance Matters Blog

Compliance Matters

White Paper Released: An Intro to 21 CFR Part 11

White Paper: An Introduction to 21 CFR Part 11In August 2003, the FDA issued the document "Guidance for Industry: Part 11, Electronic Records; Electronic Signatures — Scope and Application", which shared the Agency's current thinking regarding the scope and enforcement of 21 CFR Part 11 Electronic Records; Electronic Signatures.  The guidance document assured a concerned industry and its suppliers that fewer records would be subject to the regulation, and that there would be some discretion when it came to enforcement of the requirements for validation, audit trails, record retention, record copying, and legacy systems (i.e., those systems in operation before Part 11 become effective in August 1997).  This was to last until the Agency had time to re-think the regulation.  Though many important aspects of Part 11 would still be enforced, they were more readily complied with, and the industry and its suppliers breathed a sigh of relief... and began to ramp up compliance, not knowing if/when the Agency would re-issue the regulation and begin full enforcement.

That breather may be about to come to an end.

Risk-Based Validation: Decreasing Documentation?

Risk Based ValidationRecently, one of my colleagues here at Tanis and I, along with a customer, were discussing whether we had seen a decrease in the amount of documentation generated since the industry more formally adopted a "risk-based" approach to validation. 

Our customer was surprised that their work effort had not seemed to decrease since adopting a risk-based approach.  What we determined was that the same work effort is being expended, but the effort is earlier in the life cycle of the project.  This is a direct result of performing a Risk Assessment during the early stage of the project, when positive changes to the system can still be made, as opposed to the previous unfortunate method of finding problems during commissioning or validation testing.

Why a Validation contractor?

Validation ContractorWhen faced with a new validation project, the considerations to weigh when making the "Outsource" vs. "Perform In-House" decision are similar to projects outside of validation:

  • Do we have the time?
  • Do we have the experience?
  • Do we have an available contractor that's flexible enough to meet our needs?

Depending on the answers, outsourcing may be the way to go for your project.  Consider:

What makes a great validation company?

Validation ProtocolsI’ve spent 16 years in compliance-related positions on both sides of the table.  I’ve seen a lot of validation companies and interacted with a lot of validation departments, and I can tell you they’re not all the same.  Here’s some criteria to help differentiate between a good validation company (who will create and execute protocols for you) and a great validation company (who will offer so much more):

Why a blog?

A couple of people have asked me why I’m writing a validation- and compliance-related blog.  Then I remind Tanis Technical Ken Woycheskothem about the great Computer Systems Validation (or similar) session we attended at the ISPE conference… last year!  There’s just not enough opportunities for us to informally discuss these issues and share our knowledge.

The regulations under which we all operate are subject to interpretation, and the regulatory agencies expect us to hash a lot of it out.

My goal is to bring forth topics on which we can all contribute: feel free to use the Comments feature to add your insight to any discussion, or suggest new topics by emailing me at This e-mail address is being protected from spambots. You need JavaScript enabled to view it .