<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>Defending Food Safety</title>
      <link>http://www.defendingfoodsafety.com/</link>
      <description />
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Wed, 25 Apr 2012 00:42:40 -0600</lastBuildDate>
      <pubDate>Wed, 25 Apr 2012 00:42:40 -0600</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="defendingfoodsafety" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.defendingfoodsafety.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.defendingfoodsafety.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.defendingfoodsafety.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.defendingfoodsafety.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.defendingfoodsafety.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.defendingfoodsafety.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.defendingfoodsafety.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.defendingfoodsafety.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><item>
         <title>Managing Foodborne Illness Outbreaks, Recalls and Claims</title>
         <description>&lt;p&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:OfficeDocumentSettings&gt;
  &lt;o:AllowPNG/&gt;
 &lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:WordDocument&gt;
  &lt;w:View&gt;Normal&lt;/w:View&gt;
  &lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
  &lt;w:TrackMoves/&gt;
  &lt;w:TrackFormatting/&gt;
  &lt;w:PunctuationKerning/&gt;
  &lt;w:ValidateAgainstSchemas/&gt;
  &lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
  &lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
  &lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
  &lt;w:DoNotPromoteQF/&gt;
  &lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
  &lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
  &lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
  &lt;w:Compatibility&gt;
   &lt;w:BreakWrappedTables/&gt;
   &lt;w:SnapToGridInCell/&gt;
   &lt;w:WrapTextWithPunct/&gt;
   &lt;w:UseAsianBreakRules/&gt;
   &lt;w:DontGrowAutofit/&gt;
   &lt;w:SplitPgBreakAndParaMark/&gt;
   &lt;w:EnableOpenTypeKerning/&gt;
   &lt;w:DontFlipMirrorIndents/&gt;
   &lt;w:OverrideTableStyleHps/&gt;
  &lt;/w:Compatibility&gt;
  &lt;m:mathPr&gt;
   &lt;m:mathFont m:val="Cambria Math"/&gt;
   &lt;m:brkBin m:val="before"/&gt;
   &lt;m:brkBinSub m:val="&amp;#45;-"/&gt;
   &lt;m:smallFrac m:val="off"/&gt;
   &lt;m:dispDef/&gt;
   &lt;m:lMargin m:val="0"/&gt;
   &lt;m:rMargin m:val="0"/&gt;
   &lt;m:defJc m:val="centerGroup"/&gt;
   &lt;m:wrapIndent m:val="1440"/&gt;
   &lt;m:intLim m:val="subSup"/&gt;
   &lt;m:naryLim m:val="undOvr"/&gt;
  &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267"&gt;
  &lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/&gt;
  &lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/&gt;
  &lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/&gt;
  &lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/&gt;
  &lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="0" Name="Balloon Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/&gt;
  &lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/&gt;
  &lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="37" Name="Bibliography"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/&gt;
 &lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;/p&gt;
&lt;p style="text-align:justify" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;&lt;img align="right" src="http://www.defendingfoodsafety.com/uploads/image/Recall Window(1).jpg" style="width: 257px; height: 213px;" alt="" /&gt;A long-time industry colleague and friend recently told me that it was the things he &lt;i style="mso-bidi-font-style:normal"&gt;couldn&amp;rsquo;t&lt;/i&gt; see which he feared most. Lurking somewhere in his processing equipment, or on a product sitting in a sales cooler, there are a few colonies of pathogenic bacteria waiting patiently for their chance to wreak havoc in our business and lives. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Over the last decade, foodborne illness outbreak surveillance has improved significantly.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;As a result of improved surveillance, more illnesses are being identified and more outbreaks are being reported. By extension, many of these outbreaks are being associated with an increasing number of food products (ranging from waffles to cookie dough) and more companies are being affected. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;These improvements, while having an overall positive impact on public health, have also had a tremendous (and sometimes less than positive) impact on the food industry. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Indeed, literally thousands of spotlights (taking various forms) are now steadily and continuously crisscrossing the nation, searching for problems in our food products.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;These &amp;ldquo;spotlights&amp;rdquo; take the form of verification testing by processors, incoming product testing by customers, regulatory sampling by federal inspectors and patient isolate testing ordered by concerned physicians.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;With such vast resources being dedicated to looking for problems in today&amp;rsquo;s food, the question is not whether your product will be caught in the spotlight.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;The real question is when.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Thus, assuming contamination is inevitable, and assuming that (once a product leaves your control) that contamination will be found, all food companies should begin planning now for how they will react if and when a outbreak or recall occurs.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Fortunately, with advance planning, a company can begin limiting the fallout from an outbreak-related crisis the moment it learns about a potential problem. After learning that its product may be associated with an emerging outbreak, any company should immediately and directly engage federal, state and local health investigators. Proactive engagement is essential to: (1) quickly identify and then contain the problem (&lt;i style="mso-bidi-font-style:normal"&gt;i.e&lt;/i&gt;., keep the problem from expanding); (2) help solve the immediate public health issue; and (3) ensure that the continuing investigation is conducted appropriately.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;These steps are critical for numerous reasons.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;First, in the food industry, we know that the potential downstream consequences of any upstream food safety problems can also be catastrophic.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Just consider, for a moment, the processing of ready-to-eat food products. If a single raw material supplier unknowingly introduces contaminated ingredients into the supply stream, each of the downstream products manufactured with those ingredients will be affected. Thus, when product contamination is suspected, it is critical to identify &lt;b style="mso-bidi-font-weight:normal"&gt;&lt;i style="mso-bidi-font-style:
normal"&gt;all&lt;/i&gt;&lt;/b&gt; potentially affected lots and notify &lt;b style="mso-bidi-font-weight:
normal"&gt;&lt;i style="mso-bidi-font-style:normal"&gt;all&lt;/i&gt;&lt;/b&gt; customers to contain &lt;b style="mso-bidi-font-weight:normal"&gt;&lt;i style="mso-bidi-font-style:normal"&gt;all&lt;/i&gt;&lt;/b&gt; affected product.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Doing so will help alleviate the impact of any possible contamination, and also demonstrate to investigators that your company is committed to protecting the public (in addition to being the &amp;ldquo;right thing&amp;rdquo; to do, this will also pay significant dividends in your dealings with the regulators following the recall).&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;In addition, it is important to recognize that public health officials are increasingly being asked to investigate and solve a growing number of overlapping outbreaks at any given time. With limited resources to conduct investigations properly and methodically, we have found that federal and state investigators will sometimes adopt and embrace incorrect assumptions about the source of an outbreak. And, whether explained by inadequate resources, limitations in time or a lack of individual expertise, once an incorrect hypothesis is embraced, it becomes very difficult for public health officials to admit possible errors, set aside potential bias and identify alternative sources. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;For this reason, the moment any association is suspected, a food company should: (1) actively engage public health officials to address their immediate questions and concerns; (2) learn as much as possible about the status, scope and direction of the investigation; (3) aggressively identify the full range of potential cases and alternative sources; (4) politely but forcibly challenge, (where issues are identified) developing assumptions and hypotheses; and (5) persuasively demonstrate, where possible, that the company&amp;rsquo;s product is not likely involved. From our experience, investigators tend to be more open and thorough when all parties are actively engaged and at least someone &amp;ndash; even if only emblematically &amp;ndash; is looking over their shoulders. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;In those circumstances where a company&amp;rsquo;s product is ultimately linked to an outbreak, and a recall is warranted, management should also begin anticipating and planning for the claims and lawsuits which will inevitably follow.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;This, of course, includes enlisting experienced food safety regulatory and litigation counsel as early as possible in the investigative and recall process. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;In addition to assisting with the recall itself, counsel should also be used to help address the regulatory issues which will follow. Once a recall is announced, federal investigators will often perform a comprehensive assessment of a food company&amp;rsquo;s operations to search for and &amp;ldquo;find&amp;rdquo; at least one problem.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;These findings will then, in most instances, be documented in an FDA Letter of Warning or USDA Notice of Intended Enforcement. Unfortunately, this practice is followed even if a company was operating to virtual perfection.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;In turn, when responding to the government&amp;rsquo;s criticisms (whether warranted or not), it is critical for management to consider how each of the comments it makes will potentially impact future litigation. Certain regulatory &amp;ldquo;terms of art&amp;rdquo; often used in these communications are understood to have one meaning by government and industry, but can be mischaracterized by opposing counsel or misunderstood by a jury.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;For this reason, management should carefully draft responses that: (1) put the recall into context; (2) articulate clearly the company&amp;rsquo;s position with respect to the alleged problem (even if it may differ from the government&amp;rsquo;s position); (3) detail each of the positive elements of the company&amp;rsquo;s food safety programs; and (4) address appropriately and artfully the governmental requests in a way that will be appreciated and understood by a jury.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Appreciating how the company&amp;rsquo;s post-recall communications with the government may be used by opposing counsel in lawsuits months or years later, can significantly reduce a company&amp;rsquo;s potential litigation exposure.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;When claims are eventually asserted, food companies should work with experience food safety litigation counsel.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;This is because many companies (and their lawyers) managing a recall and outbreak for the first time are not equipped to effectively challenge any one of the complex epidemiological, microbiological and long-term damage issues often present in these cases. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNoSpacing"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;In many lawsuits, significant questions also exist about the true source of a claimant&amp;rsquo;s illness.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Unfortunately, most people incorrectly believe that they got sick from the &amp;ldquo;last thing they ate.&amp;rdquo; In those cases where the target defendant is not at fault, the key to proving the company&amp;rsquo;s innocence often turns on a painstaking analysis of health department records, patient questionnaires, shipping records, witness interviews and key depositions. &lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;The emotional edge a plaintiff brings to the table can also be tempered in some cases by raising challenges to the source of the alleged illness.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;If we can show significant problems with an outbreak investigation and its conclusions, or that our client produced and distributed thousands of safe and wholesome meals the week it processed the meal in question (and, the plaintiff was the only person who allegedly became ill), a jury will likely be more disposed to set aside emotion and focus instead on what really made the plaintiff sick.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Most jurors will also understand and appreciate a plaintiff&amp;rsquo;s obligation to exercise reasonable care for his or her own safety. Depending upon the circumstances, a plaintiff may have admitted to health department investigators eating a rare or undercooked hamburger despite the federally-mandated safe handling labels warning her not to.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Where a plaintiff shows no appreciation of the inherent risk, a jury will be more disposed to set aside sympathy and attribute fault to the plaintiff. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Additionally, many claimants (and their attorneys) will also significantly inflate and exaggerate damage claims to maximize potential recovery at settlement or trial. When a plaintiff&amp;rsquo;s overreaching is challenged appropriately and tactfully, his or her dishonesty in many cases will significantly diminish the potential sympathy a jury might otherwise be inclined to feel.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Thus, while emotion is always a factor, it can in many instances be effectively controlled.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;In the end, our own mantra is &amp;ldquo;proudly defending the hard working people who feed our families.&amp;rdquo;&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;We believe strongly in this statement, and what it means.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Having worked with food companies for nearly a decade, we have observed (first hand) the valiant efforts of the hardworking individuals and food companies who labor tirelessly to improve the safety of our food.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Thus, in most cases, we will also have a great story to tell about the significant efforts our clients undertake to ensure the food they sell &amp;ndash; and feed to their families &amp;ndash; is as safe as it can be.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Although we enjoy one of the safest and affordable food supplies in the world, we continue to face incredible risk.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;Because of improved surveillance, increased scrutiny from regulators, and a swelling interest from the media and lawyers, fewer mistakes are avoiding detection. Thus, it is critical for all companies to remember that, if there is a chance that your product can be contaminated, there is a significant chance that the contamination (whether through downstream testing or an emerging outbreak) will be found. &lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size:10.0pt;
font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;If it also critical for all food companies to begin planning and preparing for this contingency today.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;No matter how hard you try, there are (and perhaps always will be) a few colonies of pathogenic bacteria in you equipment or coolers waiting patiently to wreak havoc in your business and lives.&lt;/span&gt;&lt;/p&gt;
&lt;p style="text-align: justify;" class="MsoNormal"&gt;&lt;span style="font-size: 10pt; font-family: &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;;"&gt;** This article, authored by &lt;a href="http://www.defendingfoodsafety.com/uploads/file/STEVENS [DETAILED BIO](1).pdf"&gt;&lt;strong&gt;Shawn K. Stevens&lt;/strong&gt;&lt;/a&gt;, is also featured in the April/May edition of &lt;a href="http://www.foodquality.com/view/0/index.html"&gt;&lt;strong&gt;Food Quality Magazine&lt;/strong&gt;&lt;/a&gt;. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/kKckZuZpP7U" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/kKckZuZpP7U/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2012/04/articles/food-safety-news/managing-foodborne-illness-outbreaks-recalls-and-claims/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category>
         <pubDate>Sat, 14 Apr 2012 13:37:00 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2012/04/articles/food-safety-news/managing-foodborne-illness-outbreaks-recalls-and-claims/</feedburner:origLink></item>
            <item>
         <title>Testing the Tester [Part 2]</title>
         <description>&lt;p&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;o:OfficeDocumentSettings&gt;
  &lt;o:PixelsPerInch&gt;72&lt;/o:PixelsPerInch&gt;
  &lt;o:TargetScreenSize&gt;544x376&lt;/o:TargetScreenSize&gt;
 &lt;/o:OfficeDocumentSettings&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:WordDocument&gt;
  &lt;w:View&gt;Normal&lt;/w:View&gt;
  &lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
  &lt;w:TrackMoves/&gt;
  &lt;w:TrackFormatting/&gt;
  &lt;w:PunctuationKerning/&gt;
  &lt;w:ValidateAgainstSchemas/&gt;
  &lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
  &lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
  &lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
  &lt;w:DoNotPromoteQF/&gt;
  &lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
  &lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
  &lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
  &lt;w:Compatibility&gt;
   &lt;w:BreakWrappedTables/&gt;
   &lt;w:SnapToGridInCell/&gt;
   &lt;w:WrapTextWithPunct/&gt;
   &lt;w:UseAsianBreakRules/&gt;
   &lt;w:DontGrowAutofit/&gt;
   &lt;w:SplitPgBreakAndParaMark/&gt;
   &lt;w:EnableOpenTypeKerning/&gt;
   &lt;w:DontFlipMirrorIndents/&gt;
   &lt;w:OverrideTableStyleHps/&gt;
  &lt;/w:Compatibility&gt;
  &lt;w:DoNotOptimizeForBrowser/&gt;
  &lt;m:mathPr&gt;
   &lt;m:mathFont m:val="Cambria Math"/&gt;
   &lt;m:brkBin m:val="before"/&gt;
   &lt;m:brkBinSub m:val="&amp;#45;-"/&gt;
   &lt;m:smallFrac m:val="off"/&gt;
   &lt;m:dispDef/&gt;
   &lt;m:lMargin m:val="0"/&gt;
   &lt;m:rMargin m:val="0"/&gt;
   &lt;m:defJc m:val="centerGroup"/&gt;
   &lt;m:wrapIndent m:val="1440"/&gt;
   &lt;m:intLim m:val="subSup"/&gt;
   &lt;m:naryLim m:val="undOvr"/&gt;
  &lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
 &lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267"&gt;
  &lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 7"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 8"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" Name="toc 9"/&gt;
  &lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/&gt;
  &lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="0" Name="Default Paragraph Font"/&gt;
  &lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/&gt;
  &lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/&gt;
  &lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="0" Name="Balloon Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/&gt;
  &lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/&gt;
  &lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/&gt;
  &lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/&gt;
  &lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/&gt;
  &lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/&gt;
  &lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/&gt;
  &lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/&gt;
  &lt;w:LsdException Locked="false" Priority="37" Name="Bibliography"/&gt;
  &lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/&gt;
 &lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
&lt;/style&gt;
&lt;![endif]--&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;&lt;img align="right" src="http://www.defendingfoodsafety.com/uploads/image/E coli Plate(1).jpg" style="width: 213px; height: 203px;" alt="" /&gt;In our last column, I discussed how current &lt;a href="http://www.fsis.usda.gov/"&gt;&lt;strong&gt;FSIS&lt;/strong&gt;&lt;/a&gt; policy (which invariably reacts critically to any positive testing results) discourages companies from aggressively testing to find pathogens in their products. &lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;When adulterants are found in ground beef products, the results must be shared with FSIS and determinations made regarding which products are potentially affected and how they will be disposed. Unfortunately, in many instances, FSIS will use a company&amp;rsquo;s positive findings as a catalyst to aggressively and sometimes unreasonably second-guess its actions and response.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;This costly and unwarranted burden has, in many cases, discouraged the development and creation of truly effective testing programs by industry.&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Now, FSIS is in the process of reviewing a petition from the Center for Science in the Public Interest which asks the agency to declare numerous strains of &lt;strong&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/salmonella-1/"&gt;&lt;i style="mso-bidi-font-style:normal"&gt;Salmonella&lt;/i&gt;&lt;/a&gt; &lt;/strong&gt;as adulterants in raw meat and poultry.&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;The agency&amp;rsquo;s response to recent questions on this issue suggests that FSIS is seriously considering the policy. Dan Engeljohn, assistant administrator FSIS&amp;rsquo;s Office of Policy &amp;amp; Program Development, recently told attendees at an annual meat industry conference that FSIS is currently &amp;ldquo;assessing [the policy], and how we&amp;rsquo;d go forward if we were to adopt it.&amp;rdquo;&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size: 10pt; line-height: 115%; font-family: &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;;"&gt;This sounds to me like the decision has already been made.&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;As FSIS considers it next steps, however, it needs to maintain a reasoned approach which recognizes the fact that it is currently impossible, given current technology, to completely eradicate ubiquitous organisms from raw beef and poultry products.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;For this reason, whatever policy FSIS develops, the agency should at the same time reassess how it will react and respond to processors who aggressively test to find &lt;i style="mso-bidi-font-style:normal"&gt;Salmonella&lt;/i&gt; (or other pathogens) in their products.&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;From my experience, the majority of beef processors would welcome additional controls aimed at reducing the numbers and levels of pathogens in incoming raw trim used to process hamburger.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;If, however, the agency continues to penalize (rather congratulate) processors who test for and then find these pathogens in their finished products, then our food supply will not likely become any more safe.&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;Thus, in my view, as FSIS considers its policy going forward, the agency should also recognize that it has an unparalleled opportunity to develop and embrace rules that adequately enforce the new standards at slaughter, but also encourage (rather than discourage) additional testing.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;If FSIS can incentivize the creation of new cutting-edge programs designed to find pathogens in products before they reach consumers, as opposed to destroying any incentive to test &lt;i style="mso-bidi-font-style:normal"&gt;and&lt;/i&gt; find (through its often oppressive reaction when pathogens are found), then the agency will have substantially advanced the calling of food safety.&lt;span style="mso-spacerun:yes"&gt;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size:10.0pt;line-height:115%;font-family:&amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;"&gt;So, as we wait with interest to see whether FSIS will declare &lt;i style="mso-bidi-font-style:
normal"&gt;Salmonella&lt;/i&gt; as an adulterant, we also wait to see if FSIS will continue to unfairly (and, in my view, improperly) test the tester.&lt;/span&gt;&lt;/p&gt;
&lt;p class="Body1"&gt;&lt;span style="font-size: 10pt; line-height: 115%; font-family: &amp;quot;Arial&amp;quot;,&amp;quot;sans-serif&amp;quot;;"&gt;** This article, authored by &lt;a href="http://www.defendingfoodsafety.com/uploads/file/STEVENS [DETAILED BIO](2).pdf"&gt;&lt;strong&gt;Shawn K. Stevens&lt;/strong&gt;&lt;/a&gt;, is also featured in the April edition of the &lt;a href="http://www.provisioneronline.com/"&gt;&lt;em&gt;&lt;strong&gt;National Provisioner&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/Z3sdzEDa7fA" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/Z3sdzEDa7fA/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2012/03/articles/food-safety-news/testing-the-tester-part-2/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">E. Coli Testing</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS testing regulations and requirements</category><category domain="http://www.defendingfoodsafety.com/tags">N=60</category><category domain="http://www.defendingfoodsafety.com/tags">big-six</category><category domain="http://www.defendingfoodsafety.com/tags">combo testing</category><category domain="http://www.defendingfoodsafety.com/tags">finished product testing</category><category domain="http://www.defendingfoodsafety.com/tags">ground beef testing</category><category domain="http://www.defendingfoodsafety.com/tags">testing regulations</category>
         <pubDate>Wed, 28 Mar 2012 13:53:48 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2012/03/articles/food-safety-news/testing-the-tester-part-2/</feedburner:origLink></item>
            <item>
         <title>Testing the Tester [Part 1]</title>
         <description>&lt;p&gt;&lt;img align="right" src="http://www.defendingfoodsafety.com/uploads/image/MICRO TESTING.jpg" style="width: 196px; height: 219px;" alt="" /&gt;Microbiological sampling can be an effective tool to help companies verify that their interventions are working. But how much testing is really expedient given the current food safety climate? &lt;/p&gt;
&lt;p&gt;Today, many companies are testing for &lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/listeria-1/"&gt;&lt;strong&gt;&lt;em&gt;Listeria&lt;/em&gt;&lt;/strong&gt;&lt;/a&gt;, &lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/salmonella-1/"&gt;&lt;em&gt;&lt;strong&gt;Salmonella&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;,&lt;em&gt; &lt;/em&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/e-coli-o157h7/"&gt;&lt;strong&gt;&lt;em&gt;E. coli &lt;/em&gt;O157:H7&lt;/strong&gt;&lt;/a&gt;, generic &lt;em&gt;E. coli&lt;/em&gt;, various other indicator organisms and, now, six additional STECs.  Many companies perform raw material sampling, environmental sampling, equipment sampling and finished product sampling.  &lt;/p&gt;
&lt;p&gt;Even so, some argue, it is still not enough.&lt;/p&gt;
&lt;p&gt;Unfortunately, not even companies on the cutting edge of food safety, who have implemented state of the art testing programs which far exceed &lt;a href="http://www.fsis.usda.gov/"&gt;&lt;strong&gt;FSIS&lt;/strong&gt;&lt;/a&gt; requirements, are immune from outbreaks, recalls and criticism. This is because testing can never provide a one hundred percent guarantee that a product is sterile.  Contamination in foods is by nature quite sporadic and, thus, difficult to detect.&lt;/p&gt;
&lt;p&gt;Although finished ground beef product testing is not mandated by federal law, many companies nevertheless embrace finished product testing as a means to better monitor their processes and to further enhance the safety of their products.  These companies not only deserve our commendation, but they also deserve to be treated better by USDA.&lt;/p&gt;
&lt;p&gt;This is because current USDA policy discourages companies from finding pathogens in their products. When E. coli O157:H7 is found, the results must be reported to USDA, and determinations made regarding which products are potentially affected and how they will be disposed. Unfortunately, in many instances, USDA will use a company&amp;rsquo;s positive findings as a catalyst to aggressively second-guess its actions and response.  &lt;/p&gt;
&lt;p&gt;Indeed, rather than allowing processors who test and find to quickly address those findings and divert affected product, the agency too often responds with additional regulatory intrusion and unwarranted criticism.  Moreover, the more companies test, and the more they find, the more onerous and oppressive agency intervention can and potentially will become. Similarly, in the unfortunate event that a company (despite its best efforts) finds itself associated with an outbreak or recall, USDA is virtually certain to conclude in a Notice of Intended Enforcement issued following the recall that the companies&amp;rsquo; testing program was somehow deficient &amp;ndash; no matter how good the program actually was.  &lt;/p&gt;
&lt;p&gt;This reality, unfortunately, demonstrates the glaring disconnect between the science of food safety and the expectations of regulatory inspectors.&lt;/p&gt;
&lt;p&gt;Thus, although companies that perform more testing stand a far better chance of finding contamination and reducing their risk of being associated with an outbreak or recall, they cannot reduce the risk entirely.  Thus, to encourage more (not less) sampling, USDA should begin adjusting its policies to create more (not less) incentive for companies to test to find.  &lt;/p&gt;
&lt;p&gt;If we are to make further strides in food safety, we must develop science-based solutions which examine the root causes of contamination.   And, USDA needs to take a closer look at how it responds to processors who aggressively test their finished products.  In the end, it needs be pathogens &amp;ndash; not companies doing the right thing &amp;ndash; who feel they are being tested.&lt;/p&gt;
&lt;p&gt;** This article, authored by &lt;a href="http://www.defendingfoodsafety.com/uploads/file/STEVENS [DETAILED BIO].pdf"&gt;&lt;strong&gt;Shawn K. Stevens&lt;/strong&gt;&lt;/a&gt;, is also featured in the March edition of the &lt;a href="http://www.provisioneronline.com/"&gt;&lt;em&gt;&lt;strong&gt;National Provisioner&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;. &lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/AJ_KzN64dTs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/AJ_KzN64dTs/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2012/03/articles/food-safety-news/testing-the-tester-part-1/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category><category domain="http://www.defendingfoodsafety.com/tags">food product testing</category><category domain="http://www.defendingfoodsafety.com/tags">micro</category><category domain="http://www.defendingfoodsafety.com/tags">regulatory compliance</category><category domain="http://www.defendingfoodsafety.com/tags">testing regulations</category><category domain="http://www.defendingfoodsafety.com/tags">testing requirements and standards</category><category domain="http://www.defendingfoodsafety.com/tags">testing"</category>
         <pubDate>Mon, 12 Mar 2012 13:21:24 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2012/03/articles/food-safety-news/testing-the-tester-part-1/</feedburner:origLink></item>
            <item>
         <title>FSIS Extends Deadline for Implementation of Non-O157:H7 STEC Rule</title>
         <description>&lt;p&gt;&lt;img align="right" src="http://www.defendingfoodsafety.com/uploads/image/FSIS GROUND BEEF.jpg" style="width: 256px; height: 174px;" alt="" /&gt;The USDA&amp;rsquo;s Food Safety and Inspection Service (&amp;quot;&lt;a href="http://www.fsis.usda.gov/"&gt;&lt;strong&gt;FSIS&lt;/strong&gt;&lt;/a&gt;&amp;quot;) recently announced they will extend the agency&amp;rsquo;s implementation date for non-O157:H7 STEC sampling and testing to June 4, 2012.&lt;/p&gt;
&lt;p&gt;The extension, according to FSIS, was announced to give establishments additional time to validate their test methods and detect non-O157:H7 STECs prior to entering the stream of commerce.&lt;/p&gt;
&lt;p&gt;As part of its zero-tolerance policy for E. coli O157:H7, FSIS will begin sampling both domestically produced and imported raw beef manufacturing trimmings and other raw ground beef components for the serogroups O26, O103, O45, O111, O121 and O145.&lt;/p&gt;
&lt;p&gt;In a statement, &lt;a href="http://www.meatami.com/"&gt;&lt;strong&gt;AMI&lt;/strong&gt;&lt;/a&gt; Executive Vice President Jim Hodges applauded the temporary delay, but argued again that additional research is still needed given the significant shift in agency policy.&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;&lt;em&gt;&amp;ldquo;Even with a 90 day delay, imposing this new regulatory program in June puts the cart before the horse and will needlessly cost tens of millions of federal and industry dollars &amp;ndash; costs that likely will be borne by taxpayers and consumers.  In short, the policy is not likely to yield a significant public health benefit and given that research should precede and dictate the policy, the process that FSIS has followed in this matter is no way to develop good public policy.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In the end, significant questions still exist regarding the prevalence and virulence of non-O157:H7 STECs in beef products.  Time will tell whether the substantial resources being directed toward these new pathogens will, indeed, translate into a substantial improvement in public health.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/G_InKd7K2ak" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/G_InKd7K2ak/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2012/02/articles/food-safety-news/fsis-extends-deadline-for-implementation-of-nono157h7-stec-rule/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">Adulterants</category><category domain="http://www.defendingfoodsafety.com/tags">Adulteration</category><category domain="http://www.defendingfoodsafety.com/tags">E. coli</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">Food Regulatory Lawyers and Attorneys</category><category domain="http://www.defendingfoodsafety.com/tags">NON-O157:H7</category><category domain="http://www.defendingfoodsafety.com/tags">Non-O157</category><category domain="http://www.defendingfoodsafety.com/tags">STECs</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category>
         <pubDate>Mon, 27 Feb 2012 16:40:16 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2012/02/articles/food-safety-news/fsis-extends-deadline-for-implementation-of-nono157h7-stec-rule/</feedburner:origLink></item>
            <item>
         <title>CDC Criticized For Outbreak Reporting Policy</title>
         <description>&lt;p&gt;&lt;a href="http://www.cdc.gov/"&gt;&lt;img align="right" alt="" style="width: 261px; height: 149px;" src="http://www.defendingfoodsafety.com/uploads/image/Picture1.jpg" /&gt;&lt;/a&gt;Government health agencies have come under fire in recent days for the manner in which they conducted a recent foodborne illness investigation.&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://www.cdc.gov/"&gt;&lt;strong&gt;CDC&lt;/strong&gt;&lt;/a&gt;, in the final report of the outbreak, was criticized for referring only to a &amp;ldquo;Chain A&amp;rdquo; when describing a company that likely had been supplied with contaminated product, likely produce. The outbreak, and any possible attendant risk to public health, had ended by the time the report was published. The CDC determined that the contamination likely occurred before the product ever reached the restaurants.&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;&lt;em&gt;Investigative efforts were unable to identify a specific food associated with illness, but data indicate that contamination likely occurred before the product reached Restaurant Chain A locations. &lt;br /&gt;
&lt;/em&gt;&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;&lt;em&gt;This outbreak now appears to be over. &lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Despite the reported unlikelihood of any possible additional risk, many are accusing the CDC of jeopardizing the public health by not identifying &amp;ldquo;Chain A.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;A Seattle-based plaintiffs&amp;rsquo; food safety attorney has been leading the charge against the unnamed company, the FDA and the CDC. His complaints stem from CDC&amp;rsquo;s decision not to disclose the identity of the restaurant chain. It is his contention that &amp;ldquo;the public has a right to know and to use the information as it sees fit, and people &amp;ndash; especially government employees &amp;ndash; have no right to decide what we should and should not know.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;CDC&amp;rsquo;s policy, according to Robert Tauxe, is to disclose the identity of an outbreak source &amp;ldquo;only when people can use that information to take specific action to protect their health.&amp;quot; While some decry the policy, it is in place to promote cooperation between governmental health agencies and companies that may be associated with illnesses.&lt;/p&gt;
&lt;p&gt;On the one hand, cooperation between agencies and business during the course of an outbreak is critical. The most important thing, I think we can all agree, is to protect public health in the event of an ongoing outbreak. In the event that public health is at risk, CDC and FDA release the names of companies and the potentially implicated products. &lt;br /&gt;
Without cooperation, however, CDC investigators worry that it will take longer to identify the source of outbreaks, potentially resulting in unnecessary illnesses. Thus, if an outbreak is over, current policy is not to name the offending company. Often, as in this case, it is a supplier who provided the contaminated product and not the restaurant itself.&lt;/p&gt;
&lt;p&gt;In the end, CDC is not interested in blaming or punishing. Their job is to protect the public from health hazards and they feel they can better accomplish that by not revealing the names of companies who received contaminated products.&lt;/p&gt;
&lt;p&gt;Others, however, take the position that it is a consumer&amp;rsquo;s right to know if a restaurant is associated with an outbreak, even after it is over. They argue that, when it comes to public health, it is not for the government to decide what information people should and should not have access to.&lt;/p&gt;
&lt;p&gt;In the case of the outbreak at issue, the investigation revealed:&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;&lt;em&gt;Collaborative investigative efforts of state, local, and federal public health agencies indicated that eating food from a Mexican-style fast food restaurant chain, Restaurant Chain A, was associated with &lt;strong&gt;some &lt;/strong&gt;illnesses.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;CDC and FDA do the best they can with the resources they have. Their investigation showed a statistical association between the outbreak and the restaurant chain. The restaurant chain, in turn, did all it could to assist the CDC in determining the root source. This cooperation is reflected in the CDC report:&lt;/p&gt;
&lt;p style="margin-left: 40px;"&gt;&lt;em&gt;Restaurant Chain A, as well as their food suppliers and distributors, were very cooperative in providing extensive information to public health officials as various leads were explored. &lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Unfortunately, notwithstanding its best efforts, the CDC was unable to trace the illnesses back to a single product. Tracing microscopic bacteria to a single source can in some cases be very challenging.  But to accuse the CDC of colluding to make people sick because it didn&amp;rsquo;t reveal the name of a company that may itself have been a victim of the outbreak is inappropriate.&lt;/p&gt;
&lt;p&gt;Both the restaurant chain and the agencies involved in investigating the outbreak deserve to be praised for their cooperation in trying to determine the source of this outbreak. The chain at issue did not contaminate the food, it arrived that way. As such, there is absolutely no reason to openly criticize the company, especially in light of its own efforts to help CDC and FDA prevent further illness.&lt;/p&gt;
&lt;p&gt;Here is a link to the CDC report: I think it is actually rather impressive.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.cdc.gov/salmonella/restaurant-enteriditis/011912/index.html"&gt;http://www.cdc.gov/salmonella/restaurant-enteriditis/011912/index.html&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/Pk3a22cUnVo" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/Pk3a22cUnVo/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2012/02/articles/food-safety-news/cdc-criticized-for-outbreak-reporting-policy/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/tags">CDC</category><category domain="http://www.defendingfoodsafety.com/tags">Foodborne Illness Defense Lawyers and Attorneys</category><category domain="http://www.defendingfoodsafety.com/tags">Foodborne Illness Outbreak Investigations</category><category domain="http://www.defendingfoodsafety.com/tags">Public Disclosure</category><category domain="http://www.defendingfoodsafety.com/tags">outbreak investigations</category>
         <pubDate>Fri, 10 Feb 2012 16:07:38 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2012/02/articles/food-safety-news/cdc-criticized-for-outbreak-reporting-policy/</feedburner:origLink></item>
            <item>
         <title>FSMA: A One Year Progress Report</title>
         <description>&lt;p&gt;&lt;img align="right" alt="" style="width: 279px; height: 176px;" src="http://www.defendingfoodsafety.com/uploads/image/FDA PROGRESS REPORT.jpg" /&gt;On January 4, 2011, President Obama signed the Food Safety Modernization Act (&amp;quot;FSMA&amp;quot;).&lt;/p&gt;
&lt;p&gt;Since the FSMA was signed into law, the &lt;a href="http://www.fda.gov/default.htm"&gt;&lt;strong&gt;FDA&lt;/strong&gt;&lt;/a&gt; has made significant progress in a number of areas. Although not all of the changes expected under the FSMA&amp;nbsp;have gone into effect, many of the changes have already been implemented. &amp;nbsp;In the past year, for instance, the agency has implemented the following initiatives quickly and with minimal confusion:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Consumer-Friendly Web Search for Recalls. FDA launched a more consumer-friendly recall search engine on the FDA website.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Guidance to Seafood Industry on Food Safety Hazards. FDA issued its updated guide to the seafood industry on hazards associated with fish and fishery products and appropriate controls for those hazards.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Administrative Detention of Foods. Allows FDA to administratively detain food products that it has reason to believe are adulterated or misbranded for up to 30 days, if needed. FDA has begun using this authority.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Prior Notice of Imported Food. FDA issued an interim final rule that requires a person submitting prior notice of imported food, including food for animals, to report the name of any country to which the article has been refused entry.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Joint Anti-Smuggling Strategy. FDA and the Department of Homeland Security issued a joint anti-smuggling strategy to help to identify and prevent smuggled foods from entering the U.S. and posing a threat to national security and consumer safety.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Fee Schedule. FDA announced the fiscal year 2012 fee schedule for certain domestic and foreign facility re-inspections and for failure to comply with recall orders.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Authority to Suspend the Registration of Food Facilities. FDA has the authority to suspend the registration of food facilities to prevent the import and export into the U.S. in certain circumstances involving food that has a reasonable probability of causing serious adverse health consequences or death to humans or animals.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Product Tracing Pilots Launched. FDA announced that the Institute of Food Technologists (IFT) will carry out two new pilot projects aimed at enhancing the agency&amp;rsquo;s and industry&amp;rsquo;s ability to trace products responsible for foodborne illness outbreaks.&lt;br /&gt;
    &amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Reportedly, the FDA has also met the FSMA mandate for foreign inspections. For domestic inspections, the FSMA mandate is based on a 5-year time period.&lt;/p&gt;
&lt;p&gt;In the past year, FDA has defined its high-risk and non-high-risk domestic food facility inventories and in FY11, FDA and various state partners conducted more than 20,000 food facility inspections. At this rate the Agency will likely meet the domestic food inspection frequency mandates contained within FSMA. In addition, FDA is developing new risk-based approaches to domestic inspection to maximize public health benefit.&lt;/p&gt;
&lt;p&gt;Communication and outreach have also played an important role as FDA implements the various FSMA provisions.&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;FDA has participated in more than 350 meetings with industry leaders, farmers, consumers, public officials, and academics.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;On produce safety, FDA has worked very closely with USDA, which has an established relationship with farmers, and taken part in 14 farm tours across the country to gather input on how the proposed rules can work feasibly across the diversity of commodities and growing conditions and practices.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;FDA, the US Department of Agriculture, and the National Institute of Food and Agriculture entered into an agreement to collaborate on the establishment of a competitive grant program for food safety training and other projects.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;FDA held three public meetings on preventive controls, import provisions, and changes to inspection and compliance programs in a preventive controls environment.&lt;/li&gt;
    &lt;li&gt;FDA has participated in more than 70 meetings globally to discuss the international impact of FSMA. This includes trips by the Deputy Commissioner for Foods to China, Mexico, Canada and the European Union.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;FDA participated in, and helped fund, the establishment of the Produce Safety Alliance and the Food Safety Preventive Controls Alliance to help industry, especially small and very small firms, to comply with the requirements.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;FDA provided information to the business community through the extension services of 49 land-grant colleges and universities.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;FDA established a FSMA webpage that now has more than 10,000 subscribers, includes more than 100 Frequently Asked Questions by topic, and features videos, webinars, presentations, and print materials.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;While the impact of many of the changes implemented by FDA to date have been relatively minor, some of the most comprehensive regulatory changes &amp;ndash; such as the requirement that food companies adopt written food safety plans &amp;ndash; are still to come.  We, of course, continue wait in earnest to see, exactly, what the agency has in store.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/48PEi3IVX-8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/48PEi3IVX-8/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2012/01/articles/food-safety-news/fsma-a-one-year-progress-report/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category>
         <pubDate>Mon, 16 Jan 2012 15:24:28 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2012/01/articles/food-safety-news/fsma-a-one-year-progress-report/</feedburner:origLink></item>
            <item>
         <title>The Food Safety Modernization Act:  Are We Almost There Yet?</title>
         <description>&lt;p&gt;&lt;img align="right" src="http://www.defendingfoodsafety.com/uploads/image/FDA3.jpg" style="width: 228px; height: 120px" alt="" /&gt;With the passage of the Food Safety Modernization Act (FSMA), &lt;strong&gt;&lt;a href="http://www.fda.gov/"&gt;FDA&lt;/a&gt;&lt;/strong&gt; has been tasked to cultivate approximately 50 new rules, guidance documents, reports and studies &amp;ndash; all of which all must be implemented within very specific timeframes.&lt;/p&gt;
&lt;p&gt;In turn, while many of the new provisions have yet to be implemented, numerous milestones (despite popular belief) have already been met. These milestones have also, at least in part, touched upon many of the most significant changes under the new law, including increased agency authority, new requirements for preventative controls and new import standards and expectations. Although many of these topics (along with additional anticipated developments still lurking just over the horizon) will be discussed in greater detail in our next issue, we wanted to provide a quick primer of both where we&amp;rsquo;ve been and how much further we still need to go.&lt;/p&gt;
&lt;p&gt;Notably, FDA&amp;rsquo;s implementation of the FSMA first started gaining real momentum three months after passage (in March 2011), when FDA hosted a public meeting focused on the legislation&amp;rsquo;s new import safety requirements. The meeting attracted more than 500 attendees and, although many topics were discussed, the debate focused mainly on four key import safety provisions: Accredited Third-Party Certification; Import Certifications of Food; the Voluntary Qualified Importer Program; and the Foreign Supplier Verification Program. In essence, these new initiatives will require food product importers to ensure that each of their foreign suppliers are following the same standards that are and will be expected of food processors here in the U.S.&lt;/p&gt;
&lt;p&gt;It became clear from the meeting, however, that setting such standards, and then ensuring compliance, will create significant challenges. The amount of food that is imported into the United States has been steadily and rapidly increasing for years. This is especially true with high risk foods like fruits, vegetables and seafood. In turn, much of the food imported annually originates from countries (and economies) without the resources or infrastructure to develop and implement the robust food safety programs which are taken for granted here in the United States.&lt;/p&gt;
&lt;p&gt;Nevertheless, the FDA has announced that it will expect those U.S. food companies who chose to import, process or sell foreign products to ensure not only the safety of the products themselves, but to also ensure that their foreign suppliers are complying with each of the regulatory requirements under the FSMA. These requirements, for instance, will mandate that each foreign supplier implement a written food safety plan that satisfies the requirements of FDA.&lt;/p&gt;
&lt;p&gt;In the weeks following the March 2011 import safety meeting, FDA then began focusing additional effort on widening it regulatory powers here at home. On May 5, 2011, FDA issued a new rule allowing it to administratively detain foods which the agency has reason to believe may be adulterated or misbranded. The new rule went into effect on July 2, 2011.&lt;/p&gt;
&lt;p&gt;Effective the following day, on July 3, 2011, the FDA then gave itself additional authority, which allows the agency to suspend the registration of regulated U.S. food facilities. This new power gives FDA the ability to suspend (or threaten to suspend) the registration of any regulated food facility if the facility is producing food which, in the judgment of the agency, presents a reasonable probability of causing serious adverse health consequences or death.&lt;/p&gt;
&lt;p&gt;Since July, the agency has been moving forward on other fronts as well. With the assistance of the Department of Health and Human Services (HHS), FDA has also begun to develop and implement a joint-anti smuggling strategy to identify and prevent smuggled foods from reaching the United States. HHS and FDA report that they will be partnering with the Department of Homeland Security and the U.S. Customs and Border Patrol to implement multi-phase strategies and technologies to counter existing and emerging smuggling threats. The threat of smuggled food, of course, extends all the way from consumer safety to national security and terrorism.&lt;/p&gt;
&lt;p&gt;And, as many of you know, the FDA was also accepting public comment &amp;ndash; through last August &amp;ndash; on the docket for &amp;ldquo;Preventive Controls for Registered Human Food and Animal Food/Feed Facilities.&amp;rdquo; According to FDA, the comments received will be used by the agency to help shape the new regulations which will mandate that all regulated food facilities implement written food safety plans no later than July 2012. While many industry groups have taken advantage of the opportunity to share their perspectives with FDA, substantial uncertainty continues to exist with regard to not only what the new standards will specifically say, but how they will be uniformly and fairly enforced across the vast array of differing food processing operations across the country.&lt;/p&gt;
&lt;p&gt;In this regard, despite the agency&amp;rsquo; progress on many fronts, virtually all regulated food companies continue to wonder what is going to be asked of them and when. Although we have talked generally in previous articles about approaching deadlines and anticipated expectations, it will remain difficult for any food company to effectively prepare for the new anticipated regulatory changes until FDA actually publishes the new requirements.&lt;/p&gt;
&lt;p&gt;Additionally, in the absence of any clear direction yet from FDA regarding what, specifically, the new regulations with say, many small and medium-sized companies remain worried about their long-term survival. Given the unprecedented increase in new FDA regulation triggered under the FSMA, many small businesses (some already struggling as a result of the lethargic economy) are fearful that the investments which will be required to ensure compliance could ultimately impact their ability to compete and potentially lead to financial collapse.&lt;/p&gt;
&lt;p&gt;Indeed, Kathy Means, Vice President of Government Relations and Public Affairs at the Produce Manufacturer&amp;rsquo;s Association, recently echoed such fears, warning that while &amp;ldquo;[e]very business must have a food safety plan, these plans should be adaptable and not burdensome to small businesses.&amp;rdquo; After all, Means concluded, &amp;ldquo;the reality is that pathogens simply do not respect the size or type of an operation.&amp;rdquo; Thus, we remain hopeful that the public comments already received by FDA from industry and key stakeholders will lead to practical standards which all companies can both efficiently and effectively implement to improve their food safety programs.&lt;/p&gt;
&lt;p&gt;In spite of the progress already made by FDA, the implementation of effective regulations (whatever their form) remains a significant challenge. In addition to the difficulties associated with developing a single set of clear and effective standards, FDA will need significant additional funding to properly, uniformly and fairly enforce those standards. Already, FDA has expressed frustration over the contrast between Congressional expectations and the limited funding which may ultimately be allocated. The agriculture appropriations bill recently passed by the House of Representatives, for instance, would decrease funding to the FDA next year by $87 million.&lt;/p&gt;
&lt;p&gt;With that said, the FDA, seems to recognize the breadth of changes it faces, and now has more than two dozen separate working groups focused on implementing the FSMA. And, at the end of the day, we remain confident that FDA is doing all it can, and trying to do it well.&lt;/p&gt;
&lt;p&gt;As with any piece of monumental legislation, especially one which directly affects every consumer in our nation, FDA has wisely solicited assistance directly from the food industry in a sincere effort to make the coming changes workable for all.&lt;/p&gt;
&lt;p&gt;In the meantime, as we are driven by FDA further down this new regulatory path, we simply hope the continuing journey remains as smooth and bump-free as possible. &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/VMTl1h2hQ5g" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/VMTl1h2hQ5g/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/12/articles/food-safety-news/the-food-safety-modernization-act-are-we-almost-there-yet/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">FDA</category><category domain="http://www.defendingfoodsafety.com/tags">FSMA</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Modernization Act</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Requirements</category><category domain="http://www.defendingfoodsafety.com/tags">New Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">New Requirments</category>
         <pubDate>Thu, 15 Dec 2011 15:03:59 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/12/articles/food-safety-news/the-food-safety-modernization-act-are-we-almost-there-yet/</feedburner:origLink></item>
            <item>
         <title>Whether You Like It Or Not, Plaintiffs' Lawyers Have To Eat Too</title>
         <description>&lt;p&gt;&lt;img align="right" src="http://www.defendingfoodsafety.com/uploads/image/SHARK(3).jpg" style="width: 249px; height: 193px" alt="" /&gt;If there&amp;rsquo;s any doubt that the legal profession will continue to significantly impact the way we do business, I wanted to share some additional perspective. When conditions are ripe, lawyers (like pathogens) tend to multiply quickly.&lt;/p&gt;
&lt;p&gt;Most of us recall the large west coast E. coli O157:H7 outbreak in the early 1990s, in which nearly 600 people fell ill and some lost their lives. At that time, there were few reported outbreaks, very few food safety attorneys and hardly any foodborne illness lawsuits.&lt;/p&gt;
&lt;p&gt;Since then, we have witnessed stunning changes within the industry. Beginning in 1994, USDA required raw meat products to carry safe-handling labels. In turn, Mike Espy issued a policy statement declaring E. coli O157:H7 to be an adulterant in ground beef. In 1998, USDA solidified its zero tolerance standards (for fecal and ingesta), and required establishments to implement comprehensive HACCP plans.&lt;/p&gt;
&lt;p&gt;Meanwhile, enhanced surveillance increased our ability to detect food-borne illnesses nationwide. The CDC created PulseNet so public health agencies could upload and compare the PFGE (DNA) patterns of pathogens isolated from ill persons nationally. From 195 PFGE patterns in the mid-1990s, the database has grown to nearly 400,000 today. Having access to such information has helped investigators determine: (1) whether reported food-borne illness cases are genetically similar; and (2) whether they may have originated from a common source.&lt;/p&gt;
&lt;p&gt;This, of course, has also led to a recent increase in reported outbreaks and recalls. Rarely a day goes by when we don&amp;rsquo;t hear about food safety in the news. And, with increased media coverage and public awareness, many attorneys have taken notice.&lt;/p&gt;
&lt;p&gt;While a Google search for &amp;ldquo;slip and fall attorney&amp;rdquo; yields about 125,000 returns, &amp;ldquo;food poisoning lawyer&amp;rdquo; garners nearly 500,000. The result is an ever increasing number of lawsuits, often without merit, pursued by lawyers with little or no knowledge of food safety.&lt;/p&gt;
&lt;p&gt;Because of increasing scrutiny from regulators, the media and lawyers, fewer mistakes are also avoiding detection. Thus, we should do all we can to reduce our risk and exposure to the greatest extent possible. We should embrace a robust food safety culture, closely monitor our suppliers, continuously refine our HACCP Plans, and aggressively ensure incoming and outgoing product has been appropriately tested. We are, after all, members of an incredible industry that works tirelessly to provide our families with the safest food possible.&lt;/p&gt;
&lt;p&gt;So, recognizing that plaintiffs&amp;rsquo; attorneys have to eat too, we should each do our part to ensure they&amp;rsquo;re shopping for our products &amp;ndash; and not our customers.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/_24zyoAYrEw" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/_24zyoAYrEw/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/11/articles/food-safety-news/whether-you-like-it-or-not-plaintiffs-lawyers-have-to-eat-too/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/tags">Defending Foodborne Illness Lawsuits</category><category domain="http://www.defendingfoodsafety.com/tags">Foodborne Illness Litigation</category><category domain="http://www.defendingfoodsafety.com/tags">Outbreak Cases</category>
         <pubDate>Mon, 14 Nov 2011 15:09:48 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/11/articles/food-safety-news/whether-you-like-it-or-not-plaintiffs-lawyers-have-to-eat-too/</feedburner:origLink></item>
            <item>
         <title>Not a Happy Campylobacter</title>
         <description>&lt;p&gt;&lt;img align="right" style="width: 258px; height: 191px" alt="" src="http://www.defendingfoodsafety.com/uploads/image/Campylobacter(5).jpg" /&gt;There has been a lot of attention drawn to recent &lt;strong&gt;&lt;em&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/salmonella-1/"&gt;salmonella&lt;/a&gt; &lt;/em&gt;&lt;/strong&gt;and &lt;em&gt;&lt;strong&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/listeria-1/"&gt;listeria&lt;/a&gt;&lt;/strong&gt;&lt;/em&gt; outbreaks, and, in turn, those pathogens themselves. In the meantime, the pathogen &lt;em&gt;&lt;strong&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/campylobacter-1/"&gt;Campylobacter&lt;/a&gt;&lt;/strong&gt;&lt;/em&gt; has worked itself into relative obscurity. This may seem surprising, as &lt;strong&gt;&lt;a href="http://www.cdc.gov/"&gt;CDC&lt;/a&gt;&lt;/strong&gt; estimates that Campylobacter associated illnesses affect as many as 845,000 Americans each year.&lt;/p&gt;
&lt;p&gt;Campylobacter is a spiral-shaped bacteria that causes disease (Campylobacteriosis) in both humans and animals and is often found in the intestinal tracts of poultry, cattle, swine, domestic animals, and sometimes humans. The bacteria pass through feces and can also be found in untreated water. It is the leading cause of diarrheal illness in the United States (USDA).&lt;/p&gt;
&lt;p&gt;Symptoms of infection due to the bacteria usually occur 2 to 5 days after consuming contaminated food, however, it may take as long as 10 days for symptoms to appear. This is similar to E. coli and the two are often confused for one another. The most common symptom is diarrhea which can often times be bloody. Other symptoms include fever, nausea, abdominal pain, headache, vomiting, and muscle pain. Like most FBIs, those most susceptible to contracting Campylobacteriosis are young children, elderly persons, and pregnant women.&lt;/p&gt;
&lt;p&gt;In most instances, campylobacter infections resolve without serious illness occurring. It is important to note, however that even though complications from Campylobacter infections are rare, they can occur. The following are the most common:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;Gullian-Barre&amp;acute; Syndrome (GBS): most common cause of generalized paralysis. GBS occurs when antibodies built up to fight the disease attack nerve cells.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Reactive Arthritis: inflammation of the joints, eyes, reproductive or urinary organs.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Appendicitis&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In the event that a widespread outbreak was to occur, even statistically insignificant numbers of individuals affected by such complications could spell disaster for a company. The resulting lawsuits could easily result in millions of dollars in settlements and significant brand damage.&lt;/p&gt;
&lt;p&gt;As with preventing all foodborne illnesses, maintaining sanitary conditions and remaining cognizant of potential hazards can make all the difference in preventing Campylobacter outbreaks. With continued awareness of harmful bacteria such as Campylobacter, and how we can prevent it from occurring in our food, we can continue to prevent serious foodborne illnesses from affecting our families and ourselves.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/MwaFe-a6t3g" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/MwaFe-a6t3g/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/10/articles/food-safety-news/not-a-happy-campylobacter/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/tags">CDC</category><category domain="http://www.defendingfoodsafety.com/tags">Campylobacter</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category><category domain="http://www.defendingfoodsafety.com/tags">foodborne Illness</category>
         <pubDate>Sun, 23 Oct 2011 12:50:14 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/10/articles/food-safety-news/not-a-happy-campylobacter/</feedburner:origLink></item>
            <item>
         <title>Getting To The CORE Of Foodborne Illness Outbreaks</title>
         <description>&lt;p&gt;&lt;img align="right" style="width: 266px; height: 154px" alt="" src="http://www.defendingfoodsafety.com/uploads/image/Nationwide Illnesses(1).jpg" /&gt;The &lt;a href="http://www.fda.gov/"&gt;&lt;strong&gt;FDA &lt;/strong&gt;&lt;/a&gt;recently announced the implementation of a fully-staffed network dedicated to rapidly responding to human and animal foodborne illness outbreaks. This group is called the Coordinated Outbreak Response and Evaluation (CORE) Network.&lt;/p&gt;
&lt;p&gt;Kathleen F. Gensheimer, formally Maine&amp;rsquo;s state epidemiologist, will lead CORE, in the new position of Chief Medical Officer/Outbreak Director. Under the leadership of Gensheimer and the FDA, CORE will be staffed by epidemiologists, veterinarians, microbiologists, environmental health specialists and risk communications specialists.&lt;/p&gt;
&lt;p&gt;Their primary objectives of the new group are to: (1) rapidly respond to emerging outbreaks; and (2) research past outbreaks in order to develop new preventative methods in the hopes of mitigating or preventing future outbreaks.&lt;/p&gt;
&lt;p&gt;Gensheimer, quoted in the FDA&amp;rsquo;s press release, stated, &amp;ldquo;A real benefit of the network approach is enhancing communication and coordination with federal, state and local food safety agencies, as well as industry and consumers. Given my background at the state public health level, this is a major priority for me.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Before CORE was created, there was no centralized staff, but rather various offices of the FDA that responded to incidents. CORE, FDA is hopeful, will provide a more in-depth process of monitoring and evaluating foodborne illness outbreaks as well as facilitating faster responses when outbreaks do occur.&lt;/p&gt;
&lt;p&gt;The lack of coordination between the multiple governmental agencies involved in foodborne illness outbreaks has, historically, resulted in a host of problems. In some instances, these have included errors in trace back investigations conducted by local health department personnel which have prevented the true source of an outbreak from being identified.&lt;/p&gt;
&lt;p&gt;The FDA confirms that CORE will work closely in all outbreak investigations with the Centers for Disease Control and Prevention (CDC), the U.S. Department of Agriculture (USDA), as well as public health and agriculture agencies.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;The centralized staff of the CORE Network will work closely with FDA&amp;rsquo;s field emergency response coordinators and the investigative and analytical teams in the District offices and associated laboratories,&amp;rdquo; said Dara Corrigan, associate commissioner for regulatory affairs. &amp;ldquo;Working together will help to both standardize and strengthen how we conduct foodborne outbreak activities in the field.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Ideally, CORE will fundamentally change the manner in which foodborne illness investigations are conducted in a way that allows for faster resolutions, more effective trace back and most importantly, fewer illness.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/XV4YnkCLE9Y" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/XV4YnkCLE9Y/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/10/articles/food-safety-news/getting-to-the-core-of-foodborne-illness-outbreaks/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">CDC</category><category domain="http://www.defendingfoodsafety.com/tags">CORE</category><category domain="http://www.defendingfoodsafety.com/tags">Coordinated Outbreak Response and Evaluation Network</category><category domain="http://www.defendingfoodsafety.com/tags">FDA</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">Foodborne Illness Outbreak Investigations</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category>
         <pubDate>Mon, 10 Oct 2011 12:42:18 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/10/articles/food-safety-news/getting-to-the-core-of-foodborne-illness-outbreaks/</feedburner:origLink></item>
            <item>
         <title>We Think We Have An Adequate Food Safety Plan, But How Will It Be Enforced?</title>
         <description>&lt;p&gt;&lt;img align="right" style="width: 210px; height: 169px" alt="" src="http://www.defendingfoodsafety.com/uploads/image/FDA  DOLLAR SIGN(2).jpg" /&gt;With the passage of any new legislation, there is bound to be a period of lengthy adjustment. When that legislation is as broad and sweeping as the Food Safety Modernization Act (&amp;ldquo;FSMA&amp;rdquo;), the period of adjustment can last for years.&lt;/p&gt;
&lt;p&gt;In&amp;nbsp;a recent&amp;nbsp;column, we addressed the new federal requirement that food companies (beginning in June 2012) adopt written food safety plans, alternatively referred to as Hazard Analysis and Critical Control Point (&amp;ldquo;HACCP&amp;rdquo;) plans. While the initiative may appear relatively simple and straightforward, in practice it may prove difficult for &lt;strong&gt;&lt;a href="http://www.fda.gov/"&gt;FDA&lt;/a&gt;&lt;/strong&gt; to enforce the new requirements both uniformly and fairly. Thus, we wanted to take a moment to highlight some of the momentous challenges associated with the eventual implementation of the FDA&amp;rsquo;s new food safety rules.&lt;/p&gt;
&lt;p&gt;The concept of HACCP was jointly developed in the 1960's by Pillsbury and NASA in a project aimed at keeping astronaut's food pathogen-free. Microbiological testing, they knew, was only effective to a point. So, they collaborated on a program aimed at understanding where and how failures in food safety occur. The result was HACCP; a program designed to seek out and identify the processing points where food safety risks could be reduced to the greatest extent possible. In the 1990s, FDA mandated HAACP for sea food production, and HACCP was eventually required by FSIS in meat and poultry establishments.&lt;/p&gt;
&lt;p&gt;The program has been largely successful in the meat industry, and has led to a pronounced reduction in the number of foodborne illnesses and outbreaks. As with any regulatory initiative, however, it requires continuous refinement as science, technology and consumer attitudes mature. In spite of HACCP&amp;rsquo;s far-reaching success in the meat industry, it is important to note that the meat industry produces a fairly limited set of distinct products. And, all beef slaughter operations, by nature of the processes used, follow relatively similar HACCP programs. The risks are finite, and can be addressed from one plant to another with identical (or at least similar) interventions. Thus, within the meat industry, establishing uniformity in enforcement and compliance, while never easy, has at least proven somewhat manageable.&lt;/p&gt;
&lt;p&gt;The FDA on the other hand, is a whole different kettle of fish. Under the new requirements, each and every food processor will have to identify, categorize and then formally address a unique set of hazards. In other words, the HACCP program at a factory which makes frozen waffles is going to be fundamentally different than the one for a processor who makes yogurt, crackers, seasonings or egg salad sandwiches. There are tens of thousands of food processors in the U.S. making hundreds of thousands of products.&lt;/p&gt;
&lt;p&gt;So, how will the FDA ultimately approach the development and implementation of an inspection apparatus that deals uniformly and fairly with thousands of companies producing hundreds of thousands of distinct food products? This, of course, is the million (or, perhaps, billion) dollar question. This is also a question which should be flagged and debated today, as opposed to next year when compliance (however that term is ultimately defined by FDA) will be required.&lt;/p&gt;
&lt;p&gt;In a perfect world, FDA could simply publish guidance materials outlining a single HAACP methodology (with a single set of compliance standards) that could be applied uniformly to every manufacturing facility and food product. This, however, would prove impossible. As noted, there are simply too many different food companies producing too many dissimilar food products, and there is no such thing as a one-size-fits-all science-based HACCP program.&lt;/p&gt;
&lt;p&gt;Additionally, even if a uniform set of compliance benchmarks could be adopted and understood by all, it remains unclear how the FDA would uniformly enforce those standards throughout its many districts. In each of the FDA&amp;rsquo;s jurisdictional districts, there will inherently be countless different inspectors each sharing different qualifications. Thus, the follow-on dilemma for FDA will be how to ensure that the cookie producer in New York is ultimately being judged by the same standards as the one in California.&lt;/p&gt;
&lt;p&gt;That, of course, presumes that the FDA inspectors will be adequately trained in HACCP. Indeed, before the FDA can determine whether any company is in compliance (again, once this term is better defined by the agency), FDA inspectors will need to gain significant expertise in HACCP. They should, ideally, hold a degree in food science, and have a clear understanding of the risks which exist in the specific products they oversee (which, as noted, could exceed thousands if not more). As of today, however, many FDA and other public health inspectors lack the appropriate food science background. Thus, there is and will continue to be a shortfall of the qualified inspectors needed to build an inspection apparatus of the size and scope necessary to visit, even on a rotating basis, each of the food processing plants in the country.&lt;/p&gt;
&lt;p&gt;And, that&amp;rsquo;s just here at home. In today's rapidly globalizing world, many of the food products in our nation&amp;rsquo;s grocery stores, gas stations, drug stores and specialty shops contain imported ingredients. From salt and pepper to noodles, brownies and whipped cream, the things we consume often contain ingredients from faraway places. It remains to be seen who, if anyone, will oversee these products.&lt;/p&gt;
&lt;p&gt;Thus, it stands to reason that the FDA will have to substantially increase the number and qualifications of its inspectors, not only in the United States, but also possibly abroad, to meet the goals of the FSMA. The FDA must also recognize, however, enforcement will be complicated tremendously if the inspectors who are tasked to ensure compliance lack the basic experience and training needed to oversee a science based a system which, while appearing simple on paper, can in practice be extremely complex.&lt;/p&gt;
&lt;p&gt;With that said, both FDA and industry have time to address many of these challenges, and I have no doubt they can do so successfully. Companies and business owners, however, need to pitch in as well.&lt;/p&gt;
&lt;p&gt;The new legislation presents a unique opportunity for industry to partner with FDA in order to prepare for and streamline the implementation of FSMA. In advance of each pending deadline, FDA will invite industry to comment on its proposed rules and regulations. In turn, offer written suggestions, and ask the FDA to define, as precisely as possible, what its ultimate expectations will be. Companies should take maximum advantage of these opportunities, as it will be their best chance to play a role in developing the rules (and, by extension, the expectations) which will one day govern their food safety programs.&lt;/p&gt;
&lt;p&gt;As with any large undertaking, active engagement (as well as preparation and planning) will make all the difference between success and failure. Use the time you have now to prepare for the sweeping changes which will soon be at your doorsteps. Lastly, if you do nothing else, work alongside and communicate with the FDA as these changes are instituted. How, exactly, your food safety plan is ultimately enforced may eventually be up to you. &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/PP8F5bdipBo" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/PP8F5bdipBo/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/09/articles/food-safety-news/we-think-we-have-an-adequate-food-safety-plan-but-how-will-it-be-enforced/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">Enforcement</category><category domain="http://www.defendingfoodsafety.com/tags">FDA</category><category domain="http://www.defendingfoodsafety.com/tags">FSMA</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Modernization Act</category><category domain="http://www.defendingfoodsafety.com/tags">HACCP</category><category domain="http://www.defendingfoodsafety.com/tags">Written Food Safety Plans</category>
         <pubDate>Wed, 28 Sep 2011 12:33:46 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/09/articles/food-safety-news/we-think-we-have-an-adequate-food-safety-plan-but-how-will-it-be-enforced/</feedburner:origLink></item>
            <item>
         <title>USDA Formalizes Rules On Non-O157:H7 STECs</title>
         <description>&lt;p&gt;&lt;img align="right" style="width: 214px; height: 193px" alt="" src="http://www.defendingfoodsafety.com/uploads/image/USDA PLATE(4).jpg" /&gt;Just yesterday, FSIS formally published its &lt;u&gt;&lt;span style="color: blue"&gt;&lt;a href="http://www.fsis.usda.gov/OPPDE/rdad/FRPubs/2010-0023.pdf"&gt;&lt;strong&gt;&lt;span style="color: blue"&gt;final determination and request for comments&lt;/span&gt;&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/u&gt; relating to its decision last week to declare non-O157 STECs as adulterants in ground beef and trim products.&amp;nbsp;Since the announcement last week, there has been a great deal of concern within the industry over the scope and breadth of the proposed new regulations.&lt;span&gt;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Generally, FSIS intends to carry out verification procedures, including sampling and testing to ensure control of both O157:H7 and, now, the six other STECs.&lt;/p&gt;
&lt;p&gt;To allow industry time to implement possible changes to food safety systems, however, FSIS will generally not regard products found to have these pathogens as formally &amp;quot;adulterated&amp;quot; until it begins this routine testing. As of right now, FSIS intends to begin a routine sampling program for the non-O157 STECs no later than March 5, 2012.&lt;/p&gt;
&lt;p&gt;A significant concern for industry at this early stage is the elapsed time between micro-sampling and results.&amp;nbsp;At this point, FSIS estimates that negative (or presumptive positive) results could be available within 48 hours of sampling. For samples that are initially reactive&amp;nbsp;an additional three to five days may be necessary for a confirmed positive or confirmed negative result.&lt;/p&gt;
&lt;p&gt;Fortunately, the antimicrobial interventions used by beef manufacturers to control &lt;i&gt;E. coli&lt;/i&gt; O157:H7 are believed to be equally effective in controlling non-O157 STECs. Thus, while it is inviting industry comment, the agency &amp;quot;does not anticipate&amp;quot; at this point that industry will have to incur additional cost by implementing new or different interventions. They do, however, &amp;ldquo;anticipate that many firms will want to implement their own testing programs and even conduct the same kind of testing that FSIS plans to carry out.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;According to FSIS, establishments that manufacture raw, non-intact beef products (or intact raw beef components of those products) will be expected to evaluate whether non-O157:H7 STECs are a hazard reasonably likely to occur.&amp;nbsp;If a company&amp;rsquo;s HACCP plan cites O157 as a hazard reasonably likely to occur. If so, those companies will also be expected to reassess their HAACP plans and address the new hazard accordingly; likely by testing for it.&lt;/p&gt;
&lt;p&gt;Finally, in the event that FSIS finds a non-O157 STEC in a regulatory sample, it will conduct a for cause food safety assessment (FSA), &amp;quot;as it does currently for &lt;i&gt;E. coli &lt;/i&gt;O157:H7-positive [regulatory] samples.&amp;quot;&lt;/p&gt;
&lt;p&gt;With this as the prelude, FSIS is inviting comments on its proposal from public and industry. Since it currently intends to begin testing for non-O157:H7 STECs as soon as March 2012, however, the agency recommends that any comments be submitted no later than November 1, 2011.&amp;nbsp;Thus, while rules are never &lt;i&gt;really &lt;/i&gt;meant to be broken, they are, at least in this case, meant to be critiqued.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So, while FSIS has indeed created a &amp;quot;new set rules&amp;quot; as they apply to non-O157:H7 STECs, you may be able to influence, at least in part, how those new rules will ultimately be implemented and enforced.&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/G3oJLZ2uXSI" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/G3oJLZ2uXSI/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/09/articles/food-safety-news/usda-formalizes-rules-on-nono157h7-stecs/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">Proposed Rules</category><category domain="http://www.defendingfoodsafety.com/tags">Rulemaking</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category><category domain="http://www.defendingfoodsafety.com/tags">non-O157:H7 STECs</category>
         <pubDate>Thu, 22 Sep 2011 12:28:31 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/09/articles/food-safety-news/usda-formalizes-rules-on-nono157h7-stecs/</feedburner:origLink></item>
            <item>
         <title>USDA Declares "Big Six" Non-O157:H7 STECs As Adulterants</title>
         <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;img alt="" align="right" style="width: 255px; height: 159px" src="http://www.defendingfoodsafety.com/uploads/image/USDA HELP DESK(1).jpg" /&gt;After years of deliberation, USDA has formally declared six additional pathogenic &lt;i&gt;E. coli &lt;/i&gt;serogroups (O26, O45, O103, O111, O121 and O145) to be adulterants in non-intact raw beef. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;From this point forward, any raw ground beef or tenderized steaks found to contain these pathogens will be prohibited from sale to consumers.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;While some within the beef industry reacted warmly to the news, others where not so receptive. In a September 13&lt;sup&gt;th&lt;/sup&gt;, press release, AMI Executive Vice President James H. Hodges criticized the foundation of the new policy:&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin-left: 40px"&gt;&lt;em&gt;&lt;span style="font-size: 10pt"&gt;&amp;ldquo;&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;This new policy is not supported by science and likely will not benefit public health.&lt;/span&gt;&amp;nbsp;&lt;span style="font-size: 10pt"&gt; Indeed, in the policy notice USDA acknowledged that &lt;/span&gt;&lt;span style="font-size: 10pt"&gt;&amp;lsquo;&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;we do not know how many illnesses will actually be prevented.&lt;/span&gt;&amp;nbsp;&lt;span style="font-size: 10pt"&gt; It is not clear whether or not there will be a reduction in the number of illnesses.&lt;/span&gt;&amp;nbsp;&lt;span style="font-size: 10pt"&gt; It is also challenging to know what the industry cost will be because it is difficult to predict how many establishments will start to test and what the size distribution will be or to what extent industry will take additional measures that will prevent, reduce, or control those hazards, as they do with regard to O157 STEC.&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;&amp;rdquo;&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&lt;span style="font-size: 10pt"&gt;Indeed, in many ways, the issue has given way to more questions than answers. Processors, especially small ones, are asking how they will be able to adapt to the likely array of new testing requirements and protocols which may soon be be expected of industry.&amp;nbsp;Moreover, as of today, the time needed to carryout the tests has been causing significant problems for those companies which are already testing.&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&lt;span style="font-size: 10pt"&gt;&amp;ldquo;&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;It can be a cumbersome process,&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;&amp;rdquo;&lt;/span&gt;&lt;span style="font-size: 10pt"&gt; Craig Letch, director of quality assurance for Beef Products Inc., told Meatingplace. Letch said that while testing for &lt;i&gt;E. coli&lt;/i&gt; O157:H7 can hold up a product shipment for days, there have been times when products being tested for the new strains have been held for even longer, &lt;/span&gt;&lt;span style="font-size: 10pt"&gt;&amp;ldquo;&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;if in fact you have reactivity.&lt;/span&gt;&lt;span style="font-size: 10pt"&gt;&amp;rdquo;&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&lt;span style="font-size: 10pt"&gt;Many companies, especially those dealing in fresh products, simply do not have the space or capacity to hold their products for nearly a week before shipment. The added expense of not just testing, but then instituting new programs and holding product for extended periods of time, could significantly and adversely affect both industry and consumers alike.&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&lt;span style="font-size: 10pt"&gt;I have always been the first to commend USDA for demonstrating a real commitment to food safety.&amp;nbsp;In the absence of any real studies supporting this decision, however, the policy appears to have been driven more by sensationalism than by science.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&lt;span style="font-size: 10pt"&gt;While it may feel good to declare a bug an adulterant, there is little to show, at this point, that it will have any effect on making our food safer. &lt;/span&gt;&lt;/p&gt;
&lt;p style="margin: 0in 0in 0pt"&gt;&lt;span style="font-size: 10pt"&gt;I sincerely hope that I am proven wrong. &lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/9kS2NJu7ihU" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/9kS2NJu7ihU/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/09/articles/food-safety-news/usda-declares-big-six-nono157h7-stecs-as-adulterants/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">Adulterants</category><category domain="http://www.defendingfoodsafety.com/tags">Beef</category><category domain="http://www.defendingfoodsafety.com/tags">Ground Beef</category><category domain="http://www.defendingfoodsafety.com/tags">Testing</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category><category domain="http://www.defendingfoodsafety.com/tags">non-O157:H7 STECs</category>
         <pubDate>Thu, 15 Sep 2011 12:13:01 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/09/articles/food-safety-news/usda-declares-big-six-nono157h7-stecs-as-adulterants/</feedburner:origLink></item>
            <item>
         <title>The New Food Safety Modernization Act: What IS a Food Safety Plan?</title>
         <description>&lt;p&gt;&lt;span style="font-size: 10pt"&gt;&lt;img alt="" align="right" style="width: 280px; height: 202px" src="http://www.defendingfoodsafety.com/uploads/image/FDA1.png" /&gt;Anyone involved in the food industry has now heard about the recent passage of the Food Safety Modernization Act (&amp;ldquo;FSMA&amp;rdquo;). &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;Although the FSMA imposes many new and (some might argue) exotic requirements on industry, the one that will likely have the greatest impact on food companies is the mandate that they &amp;ldquo;develop and implement written food safety plans.&amp;rdquo;&amp;nbsp;In turn, many companies are now asking, what does this &lt;i&gt;really&lt;/i&gt; mean?&amp;nbsp;Although none of us can be certain until the &lt;strong&gt;&lt;a href="http://www.fda.gov/"&gt;FDA&lt;/a&gt;&lt;/strong&gt; begins enforcing the new laws (starting in June 2012), we &lt;i&gt;can&lt;/i&gt; give you a pretty good sense of what to expect.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;Following the passage of the FSMA, and in an attempt to keep things &lt;i&gt;sounding&lt;/i&gt; as simple as possible, the FDA announced in its promotional materials that, moving forward, food companies will simply be required to adopt &amp;ldquo;Food Safety Plans.&amp;rdquo;&amp;nbsp;But things, of course, are not always as simple as they sound. In regulatory and legal terms, this means that regulated food companies will soon be required to develop and then closely follow the Hazard Analysis and Critical Control Point (&amp;ldquo;HACCP&amp;rdquo;) methodology.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;So, what is HACCP?&amp;nbsp;Well, at its most basic level, it&amp;rsquo;s a system designed to address the food safety hazards we fear most.&amp;nbsp;The HACCP concept was first developed by Pillsbury in the 1960s, as a quality control program to govern the production of food for the United States space program.&amp;nbsp;Under the HACCP methodology, a food processor would first identify the hazards reasonably likely to affect the safety of its food (including the introduction of chemical, physical and microbiological contamination), and then establish various critical control points where interventions could be used to prevent, reduce or control those hazards.&amp;nbsp;Ultimately, HACCP was critically important for NASA as it worked to ensure that the meals its astronauts were taking into space would be as safe (and as free from unwanted contamination) as possible.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;Years later, in the early 1980s, Foster Farms (a California company) was one of the first meat processors to introduce HACCP into its own operations.&amp;nbsp;Thereafter, in 1985, HACCP gained additional notoriety when the National Academy of Science recommended HACCP as a means to modernize the USDA&amp;rsquo;s meat inspection system. Eventually, in the 1990s, USDA mandated HACCP for all meat and poultry production in the United States. At about the same time, FDA mandated HACCP for all seafood production, and extended these requirements in 2001 (in response to numerous outbreaks involving unpasteurized juices) to the domestic juice industry. And, more recently, recognizing how HACCP has improved the overall safety of these products, FDA successfully petitioned to have the new FSMA extend HACCP to all other segments of the food industry. Thus, with only a few exceptions, the FDA will soon require &lt;i&gt;all&lt;/i&gt; food companies regulated by the agency to develop and closely follow their own HACCP plans.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;In turn, according to the FDA, the underlying goal of HACCP is to prevent problems from occurring in the first instance.&amp;nbsp;Although describing the HACCP methodology can be somewhat complex, food companies will generally be required to: (1) formally consider and identify all reasonably foreseeable food safety hazards; (2) develop written plans addressing each of those hazards; and (3) closely follow those plans to reduce or eliminate such hazards to the greatest extent possible. &amp;nbsp;More specifically, the underlying principles of HACCP will require regulated food companies to do the following:&lt;/span&gt;&lt;/p&gt;
&lt;ol type="1" style="margin-top: 0in"&gt;
    &lt;li style="text-align: justify; margin: 0in 0in 0pt"&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Assess Hazards:&lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt;&amp;nbsp;Conduct a hazard analysis to identify reasonably foreseeable food safety hazards, and develop reasonably appropriate control measures for each;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol type="1" start="2" style="margin-top: 0in"&gt;
    &lt;li style="text-align: justify; margin: 0in 0in 0pt"&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Determine Critical Control Points:&lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt;&amp;nbsp;Identify appropriate critical control points (&amp;ldquo;CCPs&amp;rdquo;) where a control measure can be applied to prevent or reduce an identified hazard; &lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol type="1" start="3" style="margin-top: 0in"&gt;
    &lt;li style="text-align: justify; margin: 0in 0in 0pt"&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Establish Critical Limits:&lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt; Define acceptable and unacceptable science-based limits for all CCPs, and use those limits to ensure the production of a consistently safe product. &lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol type="1" start="4" style="margin-top: 0in"&gt;
    &lt;li style="text-align: justify; margin: 0in 0in 0pt"&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Establish Monitoring Procedures:&lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt; Monitor each CCP continuously in order to identify and immediately address any deviations from the critical limits which may occur;&amp;nbsp;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol type="1" start="5" style="margin-top: 0in"&gt;
    &lt;li style="text-align: justify; margin: 0in 0in 0pt"&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Establish Corrective Actions:&lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt; Develop procedures to be followed in the event of a deviation, which should include an assessment of the root cause, the disposition of affected product, and a written record of any corrective actions; &amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol type="1" start="6" style="margin-top: 0in"&gt;
    &lt;li style="text-align: justify; margin: 0in 0in 0pt"&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Establish Verification Procedures:&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt;Test and critique the HACCP plan, once designed (and periodically thereafter), to verify that the HACCP plan is working correctly;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;ol type="1" start="7" style="margin-top: 0in"&gt;
    &lt;li&gt;&lt;strong&gt;&lt;span style="font-size: 10pt"&gt;Establish a Record Keeping System: &lt;/span&gt;&lt;/strong&gt;&lt;span style="font-size: 10pt"&gt;Develop a system to maintain and catalog all HACCP documentation for at least 2 years, in such a form that any records can be promptly made available to the FDA if requested by the agency for inspection.&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;Recognizing this may be a lot to swallow, there are plenty of resources available to help companies develop their own HACCP plans. As a starting point, and although they should never be used as a substitute for a well-designed program which will withstand agency scrutiny &lt;i&gt;in your specific facility&lt;/i&gt;, both the FDA and numerous industry associations have published basic guidance materials online (and will likely be publishing additional materials in the months to come). &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;In addition to these background materials, there are numerous industry consultants and lawyers who will be available to help you develop, refine and critique your HACCP plan. In this regard, all companies should strongly consider obtaining advice from a qualified expert in the field as they work to ensure compliance. This is because a company&amp;rsquo;s HACCP plan will not only need to be scientifically &lt;i&gt;and&lt;/i&gt; legally sound, but the plan itself will, for all practical purposes, become a direct extension of in-plant federal FDA regulation. Put simply, the FDA&amp;rsquo;s new regulations will not only require that your HACCP plan be adequate, but that it also be followed precisely.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-size: 10pt"&gt;So, what &lt;i&gt;IS&lt;/i&gt; a Food Safety Plan? &amp;nbsp;Technically speaking, it is a comprehensive science-based HACCP plan.&amp;nbsp;In lay terms, however, it&amp;rsquo;s a proven system designed to address the food safety hazards we fear most.&lt;/span&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/IyiX3DYuhbo" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/IyiX3DYuhbo/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/08/articles/food-safety-news/the-new-food-safety-modernization-act-what-is-a-food-safety-plan/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">FDA</category><category domain="http://www.defendingfoodsafety.com/tags">FSMA</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Modernization Act</category><category domain="http://www.defendingfoodsafety.com/tags">HACCP</category><category domain="http://www.defendingfoodsafety.com/tags">Hazard Analysis and Critical Control Points</category><category domain="http://www.defendingfoodsafety.com/tags">Written Food Safety Plans</category>
         <pubDate>Tue, 30 Aug 2011 11:58:40 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/08/articles/food-safety-news/the-new-food-safety-modernization-act-what-is-a-food-safety-plan/</feedburner:origLink></item>
            <item>
         <title>The Food Safety Modernization Act:  FDA's Six Month "Progress Report"</title>
         <description>&lt;p&gt;&lt;img alt="" align="right" style="width: 202px; height: 204px" src="http://www.defendingfoodsafety.com/uploads/image/New Picture (80).jpg" /&gt;The Food Safety Modernization Act (&amp;ldquo;FSMA&amp;rdquo;) has now been law for more than six months. In turn, FDA issued a progress report on its implementation efforts since the FSMA was signed into law last January:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Preventive Controls:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In April, almost 500 persons participated in the agency&amp;rsquo;s public meeting seeking information on preventive controls used by industry to identify and address hazards associated with specific types of food and specific processes. FDA is actively seeking further industry comment (through August 22) on its rulemaking for preventive controls. Please click on the following links to review the &lt;a href="http://www.regulations.gov/#!documentDetail;D=FDA-2011-N-0238-0001"&gt;&lt;strong&gt;docket on preventive controls&lt;/strong&gt;&lt;/a&gt; and submit your comments &lt;strong&gt;&lt;a href="http://www.regulations.gov/#!submitComment;D=FDA-2011-N-0238-0001"&gt;electronically&lt;/a&gt;&lt;/strong&gt; or &lt;strong&gt;&lt;a href="http://www.regulations.gov/#!documentDetail;D=FDA-2011-N-0238-0001"&gt;via mail&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Imported Foods:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;More than 500 persons were given the opportunity in a March public meeting to weigh in on each of the four FSMA import safety provisions: Accredited Third-Party Certification; Import Certifications of Food; Voluntary Qualified Importer Program; and Foreign Supplier Verification Program.&lt;/p&gt;
&lt;p&gt;On May 5, 2011 FDA issued an interim final rule requiring that a person submitting prior notice of imported food, including food for animals, to report the name of any country to which the article has been refused entry.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Food Smuggling:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;On July 3, 2011 FDA issued a joint anti-smuggling strategy developed with the Department of Health and Human Services (HHS) and the Department of Homeland Security (DHS) to prevent smuggled foods from entering the United States and potentially threatening consumer safety and national security.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Registration Suspension:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Effective July 3, 2011 FDA has the power to suspend the registration of a food facility, thus ceasing operations, if it believes there is a &amp;ldquo;reasonable probability&amp;rdquo; that food from the facility could cause harm to humans or animals.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Administrative Detention of Food:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Also on July 3, 2011 the rule on criteria under which FDA may order administrative detention of food product went into effect. FSMA lowered the standard, granting FDA the power to detain food product for up to 30 days if it has &amp;ldquo;reason to believe&amp;rdquo; that a product is adulterated or misbranded and may cause harm to humans or animals. Click on the following link to review the &lt;strong&gt;&lt;a href="http://www.regulations.gov/#!documentDetail;D=FDA-2011-N-0197-000"&gt;Rule on Administrative Detention&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Seafood:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;FDA issued an updated guide to the seafood industry on appropriate controls for hazards associated with fish and fishery products. Industry may employ different controls if the alternative controls satisfy the applicable statute and regulations. Click on the following link to view &lt;strong&gt;&lt;a href="http://www.fda.gov/Food/GuidanceComplianceRegulatoryInformation/GuidanceDocuments/Seafood/FishandFisheriesProductsHazardsandControlsGuide/default.htm"&gt;Seafood Hazard and Control Guidance&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Inspections and Compliance:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In June, almost 700 people participated in the agency&amp;rsquo;s public meeting regarding FDA&amp;rsquo;s development of guidance and regulations and/or the implementation of: Enforcement Authorities; Frequency and Targeting of Facility Inspections; Manner of Inspection in a Preventive Controls Environment; and Enhancement of the Reportable Food Registry (RFR).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Funding:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;FDA&amp;rsquo;s progress report did not touch on what might be FSMA&amp;rsquo;s biggest obstacle: funding. The agriculture appropriations bill recently passed by the House of Representatives would decrease funding to the FDA next year by $87 million.&lt;/p&gt;
&lt;p&gt;Hopefully, the agency is receiving abundant, constructive advice from industry that will lead to practical regulations which facilities can utilize to improve their food safety, regardless of whether FDA is able to frequently stand over their shoulders and inspect.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/6qvOBKUGyQE" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/6qvOBKUGyQE/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/08/articles/food-safety-news/the-food-safety-modernization-act-fdas-six-month-progress-report/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">Business Compliance</category><category domain="http://www.defendingfoodsafety.com/tags">FDA</category><category domain="http://www.defendingfoodsafety.com/tags">FDA Attorney</category><category domain="http://www.defendingfoodsafety.com/tags">FDA Lawyer</category><category domain="http://www.defendingfoodsafety.com/tags">FSMA</category><category domain="http://www.defendingfoodsafety.com/tags">FSMA Compliance</category><category domain="http://www.defendingfoodsafety.com/tags">Final HACCP Rule</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Modernization Act</category><category domain="http://www.defendingfoodsafety.com/tags">HACCP</category><category domain="http://www.defendingfoodsafety.com/tags">Preventative Controls</category><category domain="http://www.defendingfoodsafety.com/tags">Rule-Making</category><category domain="http://www.defendingfoodsafety.com/tags">Written Food Safety Plans</category><category domain="http://www.defendingfoodsafety.com/tags">regulations</category>
         <pubDate>Mon, 15 Aug 2011 11:19:25 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/08/articles/food-safety-news/the-food-safety-modernization-act-fdas-six-month-progress-report/</feedburner:origLink></item>
            <item>
         <title>FDA Continues Work On Rules Governing Preventative Controls</title>
         <description>&lt;p&gt;&lt;img alt="" align="right" style="width: 211px; height: 209px" src="http://www.defendingfoodsafety.com/uploads/image/FSMA.jpg" /&gt;Moving forward, the Food Safety Modernization Act (&amp;ldquo;FSMA&amp;rdquo;) requires the U.S. Food and Drug Administration (&amp;ldquo;&lt;strong&gt;&lt;a href="http://www.fda.gov/"&gt;FDA&lt;/a&gt;&lt;/strong&gt;&amp;rdquo;) to issue rules governing preventive controls in FDA registered food facilities.&amp;nbsp;In turn, food facilities must develop, no later than June 2012, written Hazard Analysis and Critical Control Point (HACCP) plans which are compliant with those rules.&lt;/p&gt;
&lt;p&gt;Under FSMA, HACCP plans must identify all known or reasonably foreseeable hazards that may be associated with a food facility and then spell out the preventive controls which assure that the hazards will be minimized or prevented and food will not be contaminated.&lt;/p&gt;
&lt;p&gt;Effective preventive controls yield safer food and are, undoubtedly, one of the top weapons against foodborne illness. Given the incredibly diverse range of food facilities and products which FDA regulates, how can its rule on preventive controls reconcile with the equally diverse range of controls needed by these facilities?&lt;/p&gt;
&lt;p&gt;Hopefully, industry input will help. &amp;ldquo;The preventive-controls requirement of FSMA is one of the most important aspects of this historic law on food safety,&amp;rdquo; said Michael R. Taylor, deputy FDA commissioner for foods. &amp;ldquo;It&amp;rsquo;s imperative that we get information, data and feedback from industry and other stakeholders.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;FDA held a public meeting regarding preventive control rule-making in April (click on the following link to view the &lt;strong&gt;&lt;a href="http://www.fda.gov/Food/FoodSafety/FSMA/ucm250377.htm"&gt;public meeting transcript&lt;/a&gt;&lt;/strong&gt;), and is now seeking industry comment in electronic or written form through August 22, 2011. Click on the following link to&amp;nbsp;submit your comments &lt;strong&gt;&lt;a href="http://www.regulations.gov/#!documentDetail;D=FDA-2011-N-0238-0001"&gt;electronically&lt;/a&gt;&lt;/strong&gt; or &lt;strong&gt;&lt;a href="http://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm256923.htm"&gt;via mail&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;FDA regulated food facilities should take care to review the status of preventive control rule-making, and also provide comments to help, where possible,&amp;nbsp;shape the new regulations.&amp;nbsp; Click on the following link for updates on the &lt;strong&gt;&lt;a href="http://www.regulations.gov/#!documentDetail;D=FDA-2011-N-0238-0001"&gt;status of FDA preventative control rule-making&lt;/a&gt;&lt;/strong&gt;.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/_YbWAfidjnw" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/_YbWAfidjnw/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/07/articles/food-safety-news/fda-continues-work-on-rules-governing-preventative-controls/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">FDA</category><category domain="http://www.defendingfoodsafety.com/tags">FSMA</category><category domain="http://www.defendingfoodsafety.com/tags">Final HACCP Rule</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Modernization Act</category><category domain="http://www.defendingfoodsafety.com/tags">HACCP</category><category domain="http://www.defendingfoodsafety.com/tags">Preventative Controls</category><category domain="http://www.defendingfoodsafety.com/tags">Rule-Making</category><category domain="http://www.defendingfoodsafety.com/tags">Written Food Safety Plans</category><category domain="http://www.defendingfoodsafety.com/tags">regulations</category>
         <pubDate>Fri, 22 Jul 2011 10:49:31 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/07/articles/food-safety-news/fda-continues-work-on-rules-governing-preventative-controls/</feedburner:origLink></item>
            <item>
         <title>Should State and Local Health Departments Be Accredited?</title>
         <description>&lt;p&gt;&lt;img alt="" align="right" style="width: 229px; height: 194px" src="http://www.defendingfoodsafety.com/uploads/image/PH.png" /&gt;I will dare to venture that many people do not appreciate the vital role our local and state health departments must play in the health of our communities. Health departments perform a wide range of wellness initiatives, including, just to name a few: reaching out to new parents, educating about disease prevention and management, promoting clean air and water, administering to low-income families and the elderly, and supplying disaster assistance. In addition, our health departments track a dizzying array of statistics to monitor and improve our well being.&lt;/p&gt;
&lt;p&gt;Health departments also play an important role in assuring food safety by teaching about safe food handling practices, inspecting grocery stores and restaurants, and investigating foodborne illnesses and outbreaks.&lt;/p&gt;
&lt;p&gt;Given the significance of public health, a movement has been underway since 2007 to create a national system for ensuring the accountability and quality of our health departments. Spurred by two Institute of Medicine studies which found that public health in America was in disarray, the non-profit Public Health Accreditation Board (&amp;ldquo;PHAB&amp;rdquo;) was created and tasked with launching a national public health accreditation program.&lt;/p&gt;
&lt;p&gt;The CDC, a sponsor of PHAB, stated that &amp;quot;Just as the public expects hospitals, law enforcement agencies and schools to be accredited so should they come to expect public health departments.&amp;quot; The accreditation program, set to launch this coming fall, requires health departments to meet stringent requirements for 10 essential areas of public health activities and demonstrate a commitment to constant improvement. Some of the benefits of accreditation include:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;People from the east to west coast can expect the same quality of health services no matter where they live;&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;The accreditation process provides measurable feedback to health departments on their strengths and weaknesses so they can better serve;&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Accreditation is an opportunity for health departments to promote what they do and show taxpayers that dollars are well spent; and&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Top health professionals will be drawn to employment at accredited departments.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;One area in which health departments will be evaluated is their ability to investigate environmental health hazards. Whether a health department meets this standard could mean the difference between your company&amp;rsquo;s future success or future decline.&lt;/p&gt;
&lt;p&gt;Largely due to an increase of reported foodborne illnesses and outbreaks (brought about by advances such as PulseNet and PFGE and MLVA testing), health departments are under increasing pressure to solve more and more outbreaks at any one time. In turn, this pressure, and limited or unqualified resources, can lead health departments to reach erroneous conclusions about the sources of foodborne illness outbreaks. Unfortunately, I have defended several wrongly accused, innocent companies.&lt;/p&gt;
&lt;p&gt;I have had the pleasure of interacting with some incredible health departments, but based on my numerous poor experiences, it is a solid step for all health departments to apply to this voluntary accreditation program. If a health department does not apply to compare itself against the other health departments in the country, and the national standards approved by PAHB, then communities should ask why. Accredited or not, however, if a health department report comes across my desk, we will, as always, thoroughly verify its conclusions before advising our clients.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/TgkcBQPW9bg" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/TgkcBQPW9bg/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/06/articles/food-safety-news/should-state-and-local-health-departments-be-accredited/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/tags">Foodborne Illness Investigations</category><category domain="http://www.defendingfoodsafety.com/tags">Health Department Accreditation</category>
         <pubDate>Sat, 18 Jun 2011 10:39:40 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/06/articles/food-safety-news/should-state-and-local-health-departments-be-accredited/</feedburner:origLink></item>
            <item>
         <title>OIG Questions E. coli O157:H7 Testing; Still No Approval Of Carcass Irradiation</title>
         <description>&lt;p&gt;&lt;img align="right" style="width: 153px; height: 221px" alt="" src="http://www.defendingfoodsafety.com/uploads/image/GB TRAY(1).png" /&gt;In November 2009, U.S. Rep. Rosa DeLauro, Chairwoman of the House Agriculture-FDA Appropriations Subcommittee, asked the USDA&amp;rsquo;s &lt;strong&gt;&lt;a href="http://www.usda.gov/oig/index.htm"&gt;Office of Inspector General&lt;/a&gt; &lt;/strong&gt;(&amp;ldquo;OIG&amp;rdquo;) to investigate the efficacy of the Food Safety and Inspection Service&amp;rsquo;s (&amp;ldquo;&lt;strong&gt;&lt;a href="http://www.fsis.usda.gov/"&gt;FSIS&lt;/a&gt;&lt;/strong&gt;&amp;rdquo;) N-60 sampling method to test beef trim for &lt;em&gt;&lt;strong&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/e-coli-o157h7/"&gt;E. coli &lt;/a&gt;&lt;/strong&gt;&lt;/em&gt;&lt;strong&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/e-coli-o157h7/"&gt;O157:H7&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In response, the OIG spent six months, from January to June 2010, auditing the FSIS&amp;rsquo;s N-60 program, and then issued the first portion of its findings in March 2011. Click on the following link to view a copy of the &lt;strong&gt;&lt;a href="http://www.usda.gov/oig/webdocs/24601-9-KC.pdf"&gt;&amp;ldquo;Phase I&amp;rdquo; report&lt;/a&gt;&lt;/strong&gt;. The detailed, 40-page report concludes that FSIS must thoroughly reevaluate its N-60 sampling program for testing beef trim.&lt;/p&gt;
&lt;p&gt;The report demonstrates that an incredible amount of work has been done, and remains to be done, by both the OIG and the FSIS on this issue. The OIG has not yet even performed &amp;ldquo;Phase II&amp;rdquo; of its investigation. The bottom line is that FSIS will increase the amount of testing it performs for &lt;em&gt;E. coli &lt;/em&gt;O157:H7.&lt;/p&gt;
&lt;p&gt;While some positive changes will flow from the OIG investigation (perhaps from the Phase II evaluation of whether plants are following proper protocols for their own sampling and testing), there are valid questions about the investigation&amp;rsquo;s merit. Should so many more resources be invested in the concept of testing when we can never test to zero? As the prevalence of &lt;em&gt;E. coli &lt;/em&gt;O157:H7 in beef continues to decrease, are we just going to continually increase our testing to look for a needle in the haystack that, thankfully, is now rarely present? Can the FSIS rely more heavily on the robust &lt;em&gt;E. coli &lt;/em&gt;O157:H7 testing already being done by industry?&lt;/p&gt;
&lt;p&gt;Testing is an important part of the validation process, but as OIG concedes, &amp;ldquo;testing alone cannot suffice to ensure that consumers are safe from a pathogen like &lt;em&gt;E. coli &lt;/em&gt;O157:H7.&amp;rdquo; It is striking that the response to Rep. DeLauro&amp;rsquo;s request to the OIG regarding N-60 testing was expedited, but the industry&amp;rsquo;s petition to the FSIS for carcass irradiation has gone unanswered (&lt;strong&gt;&lt;a href="http://www.defendingfoodsafety.com/2010/02/articles/food-safety-news/despite-safety-benefits-fsis-delays-approval-of-new-food-safety-technology/"&gt;Despite Safety Benefits, FSIS Delays Approval Of New Food Safety Technology&lt;/a&gt;&lt;/strong&gt;).&lt;/p&gt;
&lt;p&gt;Over five years ago, the American Meat Institute (&amp;ldquo;AMI&amp;rdquo;) submitted a petition to the FSIS to approve the use of carcass e-beam irradiation technology in meat plants. AMI requested that the petition be granted so that low levels of irradiation could be applied to the surface of chilled beef carcasses as a food safety processing aid. The use of this technology has proven to be an effective measure in reducing the presence of pathogens in raw meat products.&lt;/p&gt;
&lt;p&gt;Carcass irradiation is an intervention that could immediately increase the safety of our food. We implore the FSIS to approve carcass irradiation without any further delay.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/wbyy15mdJJM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/wbyy15mdJJM/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/05/articles/food-safety-news/oig-questions-e-coli-o157h7-testing-still-no-approval-of-carcass-irradiation/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/articles">    Food Safety Regulations</category><category domain="http://www.defendingfoodsafety.com/tags">Beef Product Testing</category><category domain="http://www.defendingfoodsafety.com/tags">E. coli O157:H7</category><category domain="http://www.defendingfoodsafety.com/tags">FSIS</category><category domain="http://www.defendingfoodsafety.com/tags">N=60</category><category domain="http://www.defendingfoodsafety.com/tags">OIG</category><category domain="http://www.defendingfoodsafety.com/tags">USDA</category><category domain="http://www.defendingfoodsafety.com/tags">carcass irradiation</category>
         <pubDate>Sat, 28 May 2011 10:31:26 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/05/articles/food-safety-news/oig-questions-e-coli-o157h7-testing-still-no-approval-of-carcass-irradiation/</feedburner:origLink></item>
            <item>
         <title>Staphylococcus In Raw Animal Products Likely Creates Little Cause For Concern</title>
         <description>&lt;p&gt;&lt;img align="right" style="width: 227px; height: 199px" alt="" src="http://www.defendingfoodsafety.com/uploads/image/Staph(2).jpg" /&gt;Attention grabbing headlines in recent media reports have suggested that &lt;strong&gt;&lt;em&gt;&lt;a href="http://www.defendingfoodsafety.com/food-safety-law/common-food-borne-pathogens/staphylococcus-1/"&gt;Staphylococcus aureus&lt;/a&gt;&lt;/em&gt;&lt;/strong&gt; (&lt;em&gt;S. aureus&lt;/em&gt;) exists in nearly half of U.S. meat.&amp;nbsp; The authors of a study published in the journal Clinical Infectious Diseases recently suggested that &amp;ldquo;U.S. meat and poultry is widely contaminated.&amp;rdquo; Researchers collected and analyzed samples of beef, chicken, pork and turkey and reported that nearly half of the samples &amp;mdash; 47 percent &amp;mdash; were contaminated with S. aureus bacteria, and more than half of those bacteria &amp;mdash; 52 percent &amp;mdash; were resistant to at least three classes of antibiotics.&lt;/p&gt;
&lt;p&gt;In turn, many of these stories have improperly questioned the safety of our meat supply.&amp;nbsp; The study, however, likely creates little cause for concern.&lt;/p&gt;
&lt;p&gt;Setting aside the fact that &lt;em&gt;S. aureus&lt;/em&gt; are easily destroyed when meat (or any other food products) are cooked properly, American Meat Institute (&amp;ldquo;AMI&amp;rdquo;) concluded, and we agree, that the research was also misleading for the following reasons:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;The study&amp;rsquo;s small sample size was insufficient to reach the sweeping conclusions conveyed in a press release about the study. The study involved only 136 samples of meat and poultry from 80 brands in 26 retail grocery stores in five U.S. cities. In comparison, when the U.S. Department of Agriculture studies the prevalence of bacteria, their work involves thousands of samples collected over long periods of time to ensure accuracy.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;Data from the Centers for Disease Control and Prevention show steady declines in foodborne illnesses linked to consumption of meat and poultry overall and indicate that human infections with &lt;em&gt;S. aureus&lt;/em&gt; comprise less than one percent of total foodborne illnesses.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;According to a new white paper authored by Ellin Doyle, Ph.D., of the University of Wisconsin&amp;rsquo;s Food Research Institute, &lt;em&gt;S. aureus&lt;/em&gt; bacteria are found in half of all human nasal passages, and only two foodborne outbreaks of the antibiotic resistant strain of this bacteria (&amp;ldquo;MRSA&amp;rdquo;) have been identified and both were attributed to food handlers contaminating food &amp;ndash; not to the food source itself.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
    &lt;li&gt;The study criticizes U.S. production methods and suggests that they cause antibiotic resistant bacteria to develop, but Doyle&amp;rsquo;s white paper documents that similar incidence patterns can be observed in livestock in many countries with a variety of different production methods.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Industry has developed amazing processes and technologies to render American meat and poultry the safest in the world, and consumers can take simple steps to make it even safer. This study made headlines about bacteria being found in &amp;ldquo;nearly half&amp;rdquo; of our meat. The reality is, however, that consumers should treat all raw meat as if it contains bacteria. Raw meat must be stored and prepared separately from ready-to-eat foods. Restaurants and homes must have cutting boards designated solely for raw meat. Hands, utensils and any surfaces which come into contact with raw meat must be carefully washed. Finally, cooking raw meat to the proper temperatures will destroy bacteria.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/IHYbD8Kz_8w" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/IHYbD8Kz_8w/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/05/articles/food-safety-news/staphylococcus-in-raw-animal-products-likely-creates-little-cause-for-concern/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/tags">S. aureus</category><category domain="http://www.defendingfoodsafety.com/tags">Staphylococcus aureus</category><category domain="http://www.defendingfoodsafety.com/tags">beef supply</category><category domain="http://www.defendingfoodsafety.com/tags">meat supply</category>
         <pubDate>Sat, 14 May 2011 10:18:07 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/05/articles/food-safety-news/staphylococcus-in-raw-animal-products-likely-creates-little-cause-for-concern/</feedburner:origLink></item>
            <item>
         <title>The New Food Safety Modernization Act (FSMA) - What Your Company Needs To Know</title>
         <description>&lt;p&gt;The FDA's &lt;strong&gt;Food Safety Modernization&amp;nbsp;Act (FSMA)&amp;nbsp;&lt;/strong&gt;is now LAW.&lt;/p&gt;
&lt;p&gt;On April 21, 2011, nationally-recognized food safety professionals gathered at Marquette University Law School in Milwaukee to explain the new legislation and how the&amp;nbsp;new laws will affect&amp;nbsp;the food industry.&amp;nbsp; Representatives from federal and state food regulatory agencies, leaders of numerous food industry groups, and food safety executives from some of the largest food companies in the nation offered their unique perspectives, and answered pressing questions, regarding the new law&lt;/p&gt;
&lt;p&gt;This industry-leading food safety conference (the New Food Safety Modernization Act -- Approved)&amp;nbsp;was a huge success.&amp;nbsp; In turn, we are looking forward, in coming months, to offer a similar program as FDA continues to develop and&amp;nbsp;publish the new food safety regulations which will soon follow.&lt;/p&gt;
&lt;p&gt;Click on the following link to download a copy of the seminar program, and feel free to contact us for additional details regarding future events:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.defendingfoodsafety.com/uploads/file/FSMA PROGRAM AND REGISTRATION INFORMATION(1).pdf"&gt;&lt;img align="middle" src="http://www.defendingfoodsafety.com/uploads/image/FSMA SUMMIT.jpg" style="width: 533px; height: 698px;" alt="" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DefendingFoodSafety/~4/ansPbjpMcdE" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/DefendingFoodSafety/~3/ansPbjpMcdE/</link>
         <guid isPermaLink="false">http://www.defendingfoodsafety.com/2011/04/articles/food-safety-news/the-new-food-safety-modernization-act-fsma-what-your-company-needs-to-know/</guid>
         <category domain="http://www.defendingfoodsafety.com/articles">          Food Safety News</category><category domain="http://www.defendingfoodsafety.com/tags">FDA </category><category domain="http://www.defendingfoodsafety.com/tags">FSMA</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Modernization Act Seminar and Conference</category><category domain="http://www.defendingfoodsafety.com/tags">Food Safety Summit</category><category domain="http://www.defendingfoodsafety.com/tags">Legislation"</category><category domain="http://www.defendingfoodsafety.com/tags">New</category><category domain="http://www.defendingfoodsafety.com/tags">New Food Safety Regulatory Requirements</category><category domain="http://www.defendingfoodsafety.com/tags">Regulatory Seminar</category>
         <pubDate>Wed, 27 Apr 2011 14:59:03 -0600</pubDate>
         <dc:creator>Shawn Stevens</dc:creator>
      
      <feedburner:origLink>http://www.defendingfoodsafety.com/2011/04/articles/food-safety-news/the-new-food-safety-modernization-act-fsma-what-your-company-needs-to-know/</feedburner:origLink></item>
      
   </channel>
</rss>

