<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Current Quality Blog &#187; Plan Deviation</title>
	<atom:link href="http://currentquality.com/blog/tag/plan-deviation/feed/" rel="self" type="application/rss+xml" />
	<link>http://currentquality.com/blog</link>
	<description>Advancing Your Quality Assurance Knowledge</description>
	<lastBuildDate>Tue, 24 May 2011 12:04:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Planned Deviations:  Beware of THIS Compliance Risk!</title>
		<link>http://currentquality.com/blog/planned-deviations-beware-of-this-compliance-risk/</link>
		<comments>http://currentquality.com/blog/planned-deviations-beware-of-this-compliance-risk/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 17:54:07 +0000</pubDate>
		<dc:creator>Sandra Gauvin</dc:creator>
				<category><![CDATA[Planned Deviations]]></category>
		<category><![CDATA[Compliance Risk]]></category>
		<category><![CDATA[Non-conformance]]></category>
		<category><![CDATA[Nonconformance]]></category>
		<category><![CDATA[Plan Deviation]]></category>
		<category><![CDATA[Planned Devaitions]]></category>
		<category><![CDATA[Planned Deviation]]></category>

		<guid isPermaLink="false">http://currentquality.com/blog/?p=526</guid>
		<description><![CDATA[In the biotech industry it&#8217;s common for a company to use a process known as planned deviations (some companies also call it planned temporary departures) when it&#8217;s known in advance they will deviate from prescribed Standard Operating Procedures (SOPs).  It&#8217;s like knowing a nonconformance is going to happen before it actually occurs.
An example as to [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>In the biotech industry it&#8217;s common for a company to use a process known as planned deviations (some companies also call it planned temporary departures) when it&#8217;s known in advance they will deviate from prescribed Standard Operating Procedures (SOPs).  It&#8217;s like knowing a nonconformance is going to happen before it actually occurs.</p>
<p>An example as to when a company would use this process is prior to validation batch runs for new drugs that will be manufactured.  A company must submit documented evidence to the FDA that their manufacturing process and controls will maintain the drugs identity, strength, quality, and purity at all times.  Typically a company will do a few trial batch runs beforehand to make sure they&#8217;ve worked out all of the &#8216;kinks&#8217; in their manufacturing process.  This means they will temporarily deviate from their manufacturing SOP.</p>
<p>Overall, there should be very few instances where it&#8217;s appropriate and justifiable to use the planned deviation process because of what it implies&#8230;.you&#8217;re deviating from your SOP&#8217;s. However, I&#8217;ve seen companies use this process when another process wasn&#8217;t working properly. For example, if I needed to get a manufacturing SOP revised quickly but the Document Control process was &#8216;broken&#8217; so that it took me greater than 4 weeks to get a revision approved&#8230;.I would initiate a planned deviation and circumvent the Document Control process altogether.</p>
<p>With this mindset, you can see how planned deviations can become excessive and out of control. If the FDA notices an increasing trend and also recognizes that you&#8217;re using this process to circumvent broken processes, you may get a 483.  I&#8217;ve actually heard of companies that initiated a planned deviation because they were deviating from their planned deviation SOP&#8230;.stop the insanity!</p>
<p>To minimize your exposure to compliance risk, you can do the following:</p>
<ol>
<li>Create an approval board with senior management so that all planned deviations are scrutinized before given approval.  Most people will think twice if they have to get senior management involved.</li>
<li>Create a performance metric that monitors the number of planned deviations per month&#8230;.this added visibility and will help limit their use.  Also, make sure the acceptable monthly target is low.  For example, less than 5 per month.</li>
<li>Eliminate the use of planned deviations altogether and use your nonconformance process to document these events.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://currentquality.com/blog/planned-deviations-beware-of-this-compliance-risk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

