<?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; Nonconformance</title>
	<atom:link href="http://currentquality.com/blog/category/nonconformance/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>Should You Ever Reopen a Closed Non Conformance Report?</title>
		<link>http://currentquality.com/blog/should-you-ever-reopen-a-closed-non-conformance-report/</link>
		<comments>http://currentquality.com/blog/should-you-ever-reopen-a-closed-non-conformance-report/#comments</comments>
		<pubDate>Fri, 06 Aug 2010 14:04:08 +0000</pubDate>
		<dc:creator>Sandra Gauvin</dc:creator>
				<category><![CDATA[Nonconformance]]></category>
		<category><![CDATA[nc investigation]]></category>
		<category><![CDATA[non conformance report]]></category>
		<category><![CDATA[Non-conformance]]></category>

		<guid isPermaLink="false">http://currentquality.com/blog/?p=1988</guid>
		<description><![CDATA[


Photo:    Help Key by Petr Kratochvil
 


You know that dreaded feeling, when you realize that you forgot to put key information in a non conformance report that&#8217;s since closed and product has been released? &#160;Do you reopen the report or not bother?
Every time you reopen a closed non conformance report, you&#8217;re putting [...]]]></description>
			<content:encoded><![CDATA[<p></p></p>
<div class="mceTemp" draggable="">
<dl id="attachment_2006" class="wp-caption alignleft" style="width: 241px">
<dt class="wp-caption-dt"><a href="http://currentquality.com/blog/wp-content/uploads/2010/08/helpkey.jpg" mce_href="http://currentquality.com/blog/wp-content/uploads/2010/08/helpkey.jpg"><img class="size-medium wp-image-2006" title="Reopen a Non Conformance Report?" src="http://currentquality.com/blog/wp-content/uploads/2010/08/helpkey-300x199.jpg" mce_src="http://currentquality.com/blog/wp-content/uploads/2010/08/helpkey-300x199.jpg" alt="" width="231" height="153"></a><small>Photo:    <a href="http://www.publicdomainpictures.net/view-image.php?image=1819&amp;picture=help-key" mce_href="http://www.publicdomainpictures.net/view-image.php?image=1819&amp;picture=help-key">Help Key</a> by Petr Kratochvil</small></dt>
<dd class="wp-caption-dd"> </dd>
</dl>
</div>
<p>You know that dreaded feeling, when you realize that you forgot to put key information in a non conformance report that&#8217;s since closed and product has been released? &nbsp;Do you reopen the report or not bother?</p>
<p>Every time you reopen a closed non conformance report, you&#8217;re putting your company at risk from a compliance and maybe even a liability perspective. &nbsp;That&#8217;s because an auditor would begin to question the integrity and thoroughness of the investigation. &nbsp;S/he would want to know, was the investigation cut short because the focus was on releasing product and not finding root cause? If the missing information were available at the time of the investigation, would the product still have been released? &nbsp;And if you&#8217;re FDA regulated, did you put patients at risk because non conforming product may have been released?</p>
<p>Once an auditor questions the integrity of an investigation, all investigations are then questioned and they&#8217;ll start looking for trends to support their suspicions&#8230;it&#8217;s like opening pandora&#8217;s box! And keep in mind that if you have an electronic system, the audit trail will document when and how often a record was opened, and what information was added, so it&#8217;s even more obvious to a savvy auditor.</p>
<p>To minimize your risk, you&#8217;ll first need to know how often records have been reopened in the past. &nbsp;If you have an electronic system, then you should be able to quickly run a report. &nbsp;For paper systems, you&#8217;ll unfortunately have to manually look through each report. &nbsp;Any reopened records found will have to be re-evaluated through the eyes of an auditor to determine the severity of the situation.</p>
<p>For example, was the record reopened to fix grammar and typo errors or were lot numbers affected by the non conformance not included in the initial investigation? &nbsp;Either way, you&#8217;ll need to know how you&#8217;ll handle the situation should an auditor ask questions. &nbsp;Moving forward, you should consider how you&#8217;ll control the reopening of closed non conformance reports and write a procedure documenting the control&#8230;this applies even to companies that provide a service as opposed to a manufactured product.</p>
]]></content:encoded>
			<wfw:commentRss>http://currentquality.com/blog/should-you-ever-reopen-a-closed-non-conformance-report/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>NonConformance Report:  4 Key Things To Consider</title>
		<link>http://currentquality.com/blog/nonconformance-report-4-key-things-to-consider/</link>
		<comments>http://currentquality.com/blog/nonconformance-report-4-key-things-to-consider/#comments</comments>
		<pubDate>Fri, 16 Jan 2009 17:42:07 +0000</pubDate>
		<dc:creator>Sandra Gauvin</dc:creator>
				<category><![CDATA[Nonconformance]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[CA]]></category>
		<category><![CDATA[Corrective Action]]></category>
		<category><![CDATA[Investigation]]></category>
		<category><![CDATA[NCR]]></category>
		<category><![CDATA[Non-conformance]]></category>
		<category><![CDATA[Nonconformance Report]]></category>
		<category><![CDATA[Problem Statement]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[Root Cause]]></category>
		<category><![CDATA[Root Cause Analysis]]></category>

		<guid isPermaLink="false">http://currentquality.com/blog/?p=9</guid>
		<description><![CDATA[
Write A Good Problem Statement 
I’ve learned over the years that writing a good problem statement in your NonConformance Report is probably the most important part of any investigation.  If the problem isn’t stated clearly, then it becomes too easy to misinterpret the problem and lead the investigation in the wrong direction.  A Good problem [...]]]></description>
			<content:encoded><![CDATA[<p></p><div>
<p><strong>Write A Good Problem Statement </strong><br />
<span style="font-weight: normal;">I’ve learned over the years that writing a good problem statement in your NonConformance Report is probably the most important part of any investigation.  If the problem isn’t stated clearly, then it becomes too easy to misinterpret the problem and lead the investigation in the wrong direction.  A Good problem statement should tell someone ‘who, what, where, and when’&#8230;.the ‘why’ will be addressed in the actual investigation.</span></p>
<p><span><strong>Start Your Investigation Immediately</strong><br />
Every investigation has an assigned timeframe (specified in your Standard Operating Procedure) in which it must be completed&#8230;.that means approved and closed out.  So the day the NonConformance Report is initiated, the clock starts ticking.  If you wait until you have very little time left before you begin, then you most likely won’t complete a through investigation and may find yourself revisiting the issue.  Set up a timeline that will include milestones along the way so that you are working on the investigation  little-by-little&#8230;.before you know it your NonConformance Report will be completed and on-time! </span></p>
<p><span><strong>Consider All Possibilities When Determining Root Cause</strong><br />
In your NonConformance Report, you want to make sure that you consider everything that may be contributing to the problem and rule each one out until you’ve gotten to the most likely root cause(s)&#8230;.yes there can be more than one root cause.  Sometimes our workload gets a bit crazy and it becomes too easy to quickly jump to a premature conclusion. </span></p>
<p><span><strong>Verify That Your Corrective Action Was Effective</strong><br />
Give yourself enough time to evaluate whether or not the the problem has truly been corrected.  For example, if the problem used to occur whenever you manufactured product X, then you would want to make sure you have at least three cycles of making product X after your corrective action has been implemented.  If the problem hasn&#8217;t occurred during the three cycles, then you most likely got to the root cause.</span></p>
<p><span>Let me know what your experience has been with NonConformance Reports and if this post has been helpful.</span></p>
<p>Thanks,<br />
Sandra</p></div>
]]></content:encoded>
			<wfw:commentRss>http://currentquality.com/blog/nonconformance-report-4-key-things-to-consider/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

