<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Food Safety News</title>
      <link>http://www.foodsafetynews.com/</link>
      <description>Global Food Safety News &amp; Information : Presented By Marler Clark LLP, PS</description>
      <language>en</language>
      <copyright>Copyright 2012</copyright>
      <lastBuildDate>Wed, 08 Feb 2012 21:28:17 -0800</lastBuildDate>
      <pubDate>Wed, 08 Feb 2012 21:28:17 -0800</pubDate>
      <generator>http://www.sixapart.com/movabletype/?v=4.32-en</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

      
      <item>
         <title>War on Foodborne Illness: Why Restaurants Need to Join the Fight</title>
         <description><![CDATA[<div>Headlines about another restaurant involved in an outbreak are almost a daily occurrence now. Some major restaurant chains have had at least one outbreak. It begs the question, why? In my experience working with the restaurant industry on food safety, I come across a lot of resistance from operators who are naïve about their chances of contributing to an outbreak. They simply don't think it will ever happen to them.</div><div><br /></div><div>Many people took notice of the impact of foodborne illness when headlines reported on the Jack in the Box outbreak of 1993. That outbreak resulted in 750 children poisoned with 4 dying. In this case, E. coli went undetected and slipped past all controls to find its way into the hands and stomachs of the victims. In author Jeff Benedict's book "Poisoned," the Jack in the Box executives claimed they had no idea they were serving food that could kill kids. Some of the same causes for that outbreak are still happening today. Unfortunately, it seems that some restaurant organizations need to have a food safety crisis with real measurable casualties before they clean up their act and put real sustained controls in place.&nbsp;</div><div><br /></div><div>One possible reason for an increase in foodborne illness outbreaks is that some people think the USDA, FDA and health departments offer enough regulation and provide adequate protection against foodborne illness. However, this is a false sense of security. The USDA is getting ready to cut 259 jobs. It's unlikely that this will be beneficial in protecting our food supply. With budgets diminishing and health departments consolidating their services, health departments are developing new ways to reduce their regulatory oversight of the food service industry. The city of Chicago and the Maricopa County Health Department have already put new plans in place to allow responsible operators to police themselves. If this trend continues, public health officials will only have time to track down these emerging threats rather than trying to prevent them.&nbsp;</div><div><br /></div><div>To further complicate the problem, food manufacturers are hiring third-party auditors to prove their food is safe, only to have that practice backfire with the recent cantaloupe and peanut outbreaks. In those cases, the auditors received harsh criticism for not identifying problems, and they gave exceptional scores to the manufacturers that hired them. Third-party auditors are useful tools only when they identify all the food safety deficiencies.</div><div><br /></div><div>Without more oversight of food safety practices, we'll continue to see headlines such as these:</div><div><br /></div><div><a href="http://www.foodsafetynews.com/2012/01/cdc-mum-about-fast-food-mexican-chain-in-salmonella-outbreak/">68 Sickened at 'Mexican-style' Restaurants in 10 States</a></div><div><br /></div><div><a href="http://www.foodsafetynews.com/2011/01/sprouts-outbreak-toll-now-at-112-in-18-states/">112 people sick from sprouts contaminated with Salmonella (linked to alfalfa sprouts served at Jimmy John's restaurants)</a></div><div><br /></div><div><a href="http://www.foodsafetynews.com/2012/01/146-norovirus-cases-linked-to-illinois-restaurant/">146 people infected with norovirus may have become sick after eating at Bob Chinn's Crab House</a></div><div><br /></div><div>So, with many restaurants failing to understand that there is a war on foodborne illness happening, who is left to fight? For decades it has been left to local health departments. But we cannot solely rely on the public health sector to set policy and management practices for the restaurant industry. The time has come for the industry as a whole to step up and join the fight. Restaurant owners and operators should hold each other to a higher standard by educating themselves about foodborne illness and striving to serve safe food to the public.</div><div><br /></div><div>Many in the industry are already taking responsibility. There are plenty of food-safety-conscious owners and operators who are implementing policies and best practices for preventing foodborne illness and promoting food safety in their organizations. This can be expensive, but there really is no comparison to the cost of paying damages from an outbreak. Jeff Benedict reported that it cost Jack in the Box $98 million in damages. Their insurance barely paid it all. How many restaurant organizations out there have a $100 million insurance policy? For many restaurants, having an outbreak spells bankruptcy. Jack in the Box learned its lesson the hard way. As a result, the company hired food safety expert David Theno and revamped its entire food safety program.&nbsp;</div><div><br /></div><div>Restaurant owners and managers need to understand that they are potentially handling contaminated product every day. This means it's essential to control all factors that can lead to foodborne illness.</div><div><br /></div><div>------------------------&nbsp;</div><div><br /></div><div><i>Dennis Keith is founder and CEO of the consulting company Respro Food Safety Professionals.&nbsp;</i></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/the-war-on-foodborne-illness-why-restaurants-need-to-join-the-fight/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/the-war-on-foodborne-illness-why-restaurants-need-to-join-the-fight/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Thu, 09 Feb 2012 01:59:05 -0800</pubDate>
         <author>dennis@resprofsp.com (Dennis Keith)</author>
      
      </item>
      
      <item>
         <title>Does High Risk Meat Get USDA Endorsement?</title>
         <description><![CDATA[<div>On February 2, I wrote a commentary that appeared on Food Safety News entitled <a href="http://www.foodsafetynews.com/2012/02/usda-inspected-and-passed-high-risk-meat/?utm_source=newsletter&amp;utm_medium=email&amp;utm_campaign=120202">"USDA Inspected and Approved High-Risk Meat."</a>&nbsp;</div><div><br /></div><div>One sentence in the editorial stated "USDA has concluded that Hannaford's high risk practices likely led to this outbreak," a reference to Salmonella infections linked to supermarket ground beef. Investigators were unable to trace the contaminated ground beef to any one supplier.</div><div><br /></div><div>USDA officials subsequently contacted me, claiming that the agency did not say Hannaford's practices led to the outbreak, and requested I issue a correction. What the agency stated was that Hannaford's "high-risk practices" for grinding beef, including a lack of grinding logs, were a barrier in its investigation of the outbreak. &nbsp;</div><div>&nbsp;</div><div>I am writing this today not only as a correction, but also to describe how USDA-approved meat laced with E.coli and Salmonella automatically create "high-risk practices" at retail meat markets, hospital cafeteria and meat establishments that purchase boxed beef from source slaughter plants. &nbsp;Americans need to know how "high-risk" meat is getting into our food chain.</div><div><br /></div><div>Following the 1993 Jack In The Box outbreak, USDA required the meat industry to implement HACCP (Hazard Analysis Critical Control Point) systems. The agency's previous meat inspection system had been organoleptic, i.e., dependent upon the senses such as smell, sight and touch. &nbsp;Bacteria such as E.coli O157:H7 and Salmonella cannot be detected via organoleptic methods. USDA claimed that HACCP was built upon science-based inspection and meat production, not in organoleptic senses. The "science-based" foundation of USDA-style HACCP was microbial testing of meat, which can indeed detect the presence of invisible pathogens.</div><div><br /></div><div>All meat plants were then required to devise their own customized HACCP plans, plus associated practices which would result in the production of consistently safe meat and poultry. Each year, the largest slaughter plants issue annual certifications and letters of guarantee, in which they describe the variety of policies and procedures utilized to produce safe food. Most, if not all, large plants now have these certifications and letters of guarantee available on their websites enabling customers to print copies. The information below comes directly from a variety of these websites.</div><div><br /></div><div>The largest slaughter plants are highly efficient assembly and disassembly lines, deftly slaughtering and processing up to 6,000 beef daily. To their credit, they have invested millions (some claim BILLIONS) to develop and implement a plethora of scientific interventions which have clearly made our food safer. It is estimated that such scientific advancements add 6 - 8 cents per lb to the cost of beef.</div><div>&nbsp;&nbsp;</div><div>The list of laudable interventions and policies is lengthy and exhaustive, including but not limited to:</div><div><br /></div><div>- Prerequisite programs</div><div>- Pre-Operational sanitation programs</div><div>- Operational sanitation programs</div><div>- Hide-on carcass washes</div><div>- Critical Control Points (CCPs), which are points in the process where controls can be used to prevent, eliminate or reduce pathogens to an undetectable level</div><div>- Steam vacuuming beef carcasses on the kill floor</div><div>- Pre-evisceration and post-evisceration sprays, water and/or lactic acid sprays</div><div>- Thermal pasteurization systems: hot water or steam</div><div>- Standard operating procedures (SOPs)</div><div>- Standard sanitation operating procedures (SSOPs)</div><div>- Good manufacturing practices (GMPs)</div><div>- Pest control management</div><div>- Humane handling protocols</div><div>- Allergen control programs</div><div>- Testing of carcasses for E.coli, primary generic E.coli</div><div>- Salmonella testing programs</div><div>- Listeria testing programs</div><div>- Test and hold protocols</div><div>- Organic acid sprays of carcasses in the cooler</div><div>- Product recall programs</div><div>- Certificates of Analysis (COAs)</div><div><br /></div><div>And many, many more.</div><div><br /></div><div>In recent years, the largest slaughter plants have implemented an additional step with which I am greatly impressed. &nbsp;When beef carcasses are broken down into component parts such as rounds, loins, ribs, etc, each individual piece of intact meat is placed into a vacuum packaged bag, and then boxed for shipment. &nbsp;Immediately prior to placement into the vacuum bag, each piece of intact meat is exposed to an antimicrobial spray which further controls pathogens. These intact pieces of meat are, in my opinion, super sanitary, having been exposed to yet one more antimicrobial intervention. Consumers can eat this meat with a high degree of confidence in its safety.</div><div>&nbsp;&nbsp;</div><div>I am quite impressed with a statement found in one slaughter company's certification: &nbsp;"We apply lactic acid to carcasses just prior to Fabrication, peroxyacetic acid to conveyor belts in our Fabrication process, and peroxycacetic acid to primal and sub-primals prior to packaging and to trim on the conveyor belt prior to placing into boxes or bins."&nbsp;This company leaves no stone unturned in its commitment to safe food.</div><div><br /></div><div>A statement from another slaughter plant: "Primal and sub-primal [intact] products are subject to an antimicrobial spray after trimming but prior to or at bagging. The antimicrobial treatment has been tested in our establishments and has shown to be effective in the reduction of bacteria and is monitored as per our application program."</div><div><br /></div><div>These plants are a credit to our industry.</div><div><br /></div><div>Interestingly, the source slaughter plants test ground beef and boneless trimmings for the presence of pathogens, but do not test intact beef cuts. If pathogens were detected on intact cuts, the slaughter plant (and perhaps USDA) would know that its highly heralded HACCP systems had failed.</div><div><br /></div><div>What is the true frequency of pathogens in intact beef cuts? &nbsp;At a meat industry conference in Chicago on Sept. 17, 2008, then-USDA Under Secretary for meat inspection Dr. Richard Raymond revealed results of a recent agency experiment. &nbsp;Dr. Raymond stated that the agency had tested 24 pieces of intact beef cuts for the presence of E.coli O157:H7. &nbsp;Of the 24 intact cuts, 8 had E. coli O157:H7 on them, and six of the eight were loin cuts. Even if this test was an anomaly, USDA officials are painfully aware of the true incidence of pathogens on intact beef cuts. &nbsp;So, how does USDA respond to this threat to public health? &nbsp;The agency gives a Pass Card to the source slaughter plants, blithely allowing the plants to ship into commerce intact cuts which are surface-contaminated with E. coli O157:H7, as well as Salmonella, much to the chagrin of Hannaford and its customers.</div><div><br /></div><div>An article in the Portland Press Herald quotes Daniel Engeljohn, assistant administrator of USDA's Food Safety and Inspection Service:</div><div><br /></div><div><i>"Engeljohn noted that there is a lower sanitary standard for the cuts of meat that are used for trimmings than there is for the ground beef that comes in tubes."</i></div><div><br /></div><div>I respectfully disagree. The "cuts of meat" to which Engeljohn refers are the intact cuts described above. &nbsp;These cuts were exposed not only to the plethora of kill-floor interventions listed above, but also to the antimicrobial spray prior to their being packaged, as described above. If consumers can't trust the safety of beef after that phalanx of scientific interventions, we'd better not trust beef at all. Part of Engeljohn's concerns has to do with testing, which will be discussed below.</div><div><br /></div><div>Several slaughter plants include disclaimers which state that no technology exists that can guarantee fresh meat products are free of pathogens, and that no one is able to guarantee pathogen free raw materials. These statements are absolutely true: &nbsp;raw meat, which has not been exposed to a kill step such as irradiation or full cooking, cannot be guaranteed to be pathogen free.</div><div><br /></div><div>Slaughter plants take one additional step to protect themselves from liability for foodborne outbreaks emanating from consumption of their products. In spite of the fact their intact primal cuts have been exposed to the arduous gauntlet of antimicrobial interventions previously described in this report, some packers claim that their intact beef cuts are "NOT INTENDED FOR GRINDING."</div><div><br /></div><div>Slaughter plants thus admit that an inordinate percentage of their intact cuts are laced with deadly pathogens. So much for the efficacy of their "science based" interventions. Packers use this clever machination to insulate themselves from bacterial liability, even though in all likelihood the bacteria entered the food chain on their kill floor.</div><div>&nbsp;&nbsp;</div><div>USDA does NOT object to such disclaimers. Unfortunately, USDA itself admits that the official USDA Mark of Inspection is meaningless. Agency publications have stated:</div><div><br /></div><div><i>"Grinders with prerequisite programs should not rely on the <b>mark of inspection</b> (emphasis added) to accept incoming product."</i></div><div>&nbsp;</div><div><i>"An establishment that receives, grinds, or otherwise processes raw beef products cannot conclude that E. coli O157:H7 is not reasonably likely to occur in its production process because the product it receives bears the <b>mark of inspection</b>" (emphasis added).</i></div><div><br /></div><div>When USDA itself admits that the Mark of Inspection is valueless, coupled with slaughter plants stating that their meat is "NOT INTENDED FOR GRINDING," consumers should be fully forewarned that all raw meat carries a high risk of pathogen contamination. All liability for foodborne sicknesses has now been cleverly shifted onto consumers.</div><div><br /></div><div>USDA has declared E. coli O157:H7 to be an "adulterant," prohibiting the shipment of adulterant-contaminated meat into commerce. USDA recently proposed adding six more subtypes of E. coli to the list of adulterants. More specifically, USDA states that E. coli O157:H7 is an adulterant in ground beef and in boneless trimmings. Herein lies the rub however: &nbsp;when E. coli O157:H7 is found on the exterior of intact cuts, USDA classifies the pathogen as a mere contaminant, certainly not a lethal adulterant. Therefore, slaughter plants can ship into commerce intact cuts of meat which are surface-contaminated with E. coli O157:H7, with full agency endorsement.</div><div>&nbsp;&nbsp;</div><div>Subsequently, when downstream restaurants, hospital cafeterias and further processing plants open these intact cuts and process them into steaks, roasts and ground beef, only then do these heretofore feckless contaminants mysteriously morph into lethal adulterants!</div><div><br /></div><div>Processing these intact cuts produce boneless trimmings, which have always been made into ground beef. Grinding trim emanating from these intact cuts is precisely what USDA refers to as "high-risk practices." &nbsp;Why? &nbsp;USDA officials have stated many times that grinding such trim is high risk because the trimmings have not been tested, nor treated with antimicrobials. &nbsp;We need to closely scrutinize this agency statement.</div><div><br /></div><div>First of all, this agency statement contradicts an industry mantra of the last eight years which is that "We can't test our way to safe food," an erudite statement. Testing alone does not produce safe food. Testing does not remove pathogens from meat, nor does testing apply antimicrobial interventions against raw meat. &nbsp;Testing is but an indicator of pathogen presence, a brief window in time which reveals the presence of absence of pathogens in a small, limited amount of meat.</div><div><br /></div><div>USDA's statement lulls consumers into thinking that we can build safety into meat via testing. Pillsbury's original HACCP protocol built safety into meat at each step of the processing line. Testing does not build safety into food.</div><div><br /></div><div>USDA's contention that processing intact cuts and grinding the associated trimmings as being a "high risk practice" exposes the biased underpinnings of USDA-style HACCP. We must remember that intact cuts originated from those same beef carcasses which were exposed to the wide array of science-based interventions on the kill floor, in the cooler, and in the fabrication room. While still on the original carcass, these intact cuts were exposed to steam pasteurization, lactic acid sprays, hot water rinses, trimming, and all those interventions previously listed.</div><div><br /></div><div>To top it off, in addition to all these kill-floor interventions, the packers now apply an antimicrobial spray to the intact cuts just before the cuts are vacuum packaged. &nbsp;After packaging, if the intact cuts are still laced with adulterants, major insanitary conditions persist at the meat plant. USDA disagrees.</div><div><br /></div><div>Instead, USDA and many in the meat industry continue to pass downstream all pathogen liability to the end users: &nbsp;retail meat markets (such as Hannaford), restaurants, hospital cafeterias, and individual households. The end users are reminded to use proper food handling and cooking protocol, including prevention of cross contamination. &nbsp;An article written by Leslie Bridgers at the Portland Press Herald regarding the Hannaford recall included the following quote from USDA's Daniel Engeljohn:</div><div><br /></div><div><i>"[USDA] Investigators found that Hannaford would grind trimmings and tube meat without cleaning the equipment in between, he said, raising the possibility of cross contamination."</i>&nbsp;</div><div>&nbsp;</div><div>Since when has USDA developed a commitment to the prevention of cross contamination? &nbsp;The fact that the agency allows slaughter plants to ship into commerce intact cuts of meat surface-contaminated with E. coli O157:H7 virtually guarantees that entities which process those intact cuts will cross contaminate their facilities. Intact cuts are touched by gloves, aprons, knives, tables, saws, wrapping equipment, etc. Perhaps USDA perceives that everyone handling intact cuts should replace their gloves and aprons between each intact cut of meat, should wash and sanitize their cutting boards, table tops, saws and all related equipment between each intact cut?</div><div><br /></div><div>Large retail meat markets like Costco and further processing plants will process dozens if not hundreds of boxes (each containing several pieces) of intact cuts on a daily basis. The probability of cross-contamination is daunting. &nbsp;And the very idea of cleaning and sanitizing all equipment countless times daily, as well as replacing gloves and aprons, is simply not viable.</div><div>&nbsp;&nbsp;</div><div>Commingling trimmings with other grindable meat such as "tube meat" does NOT introduce pathogens into the finished product. In all likelihood, pathogens arrived on the exterior of intact cuts in boxes proudly bearing the official USDA Mark of Inspection, which states "USDA Inspected and Passed." This means that USDA knowingly allows E. coli residing on intact cuts to be emblazoned with the agency's Mark of Inspection. Thus, we now have USDA Inspected and Passed Salmonella and E. coli. When E. coli-laced intact cuts are further processed, those same pathogens are deposited onto steaks, roasts and into ground beef. &nbsp;The commingling of trimmings from multiple sources does NOT introduce E. coli, but spreads it. Don't ask USDA to acknowledge this.</div><div>&nbsp; &nbsp;</div><div>USDA's Recall Press Release of the Hannaford recall on Dec,15, 2011 included these statements:</div><div><br /></div><div><i>"Based on an examination of Hannaford's limited records, FSIS was unable to determine responsible suppliers."</i></div><div><i><br /></i></div><div><i>"FSIS has not yet been able to identify FSIS-regulated suppliers of raw beef ground at Hannaford Stores related to the outbreak that could be subject to recall action."&nbsp;</i></div><div><br /></div><div>USDA is thus critical of the lack of grinding logs at Hannaford stores. While the existence of copious logs would have greatly aided in the determination of noncompliant source slaughter plants, we must remember that the lack of grinding logs did NOT contribute to the outbreak! &nbsp;Grinding logs, or the absence thereof, have no connection to the introduction of bacteria into meat. &nbsp;An establishment may have superlative grinding logs, and will still produce unsafe meat. Garbage in, Garbage out.</div><div>&nbsp;&nbsp;</div><div>However, how can USDA be critical of Hannaford's lack of evidence showing the sources of meat being ground? &nbsp;For many years, the agency itself has steadfastly refused to authorize its own inspectors to document all source evidence at the time of sample collection!</div><div><br /></div><div>Example: &nbsp;at a Senate Field Hearing on Dec. 11, 2002, I suggested that when an agency inspector collects a sample of ground beef for E.coli O157:H7 analysis at a USDA Lab, that both the inspector and a plant official should immediately document the source(s) of the meat being ground. &nbsp;Representing USDA at the hearing was William Smith, then-Deputy Administrator of the Office of Field Operations. He now heads up the agency's OPEER department. &nbsp;Smith made these two responses to my suggestion for evidence documentation:</div><div><br /></div><div><span class="Apple-tab-span" style="white-space:pre">	</span><i>"....we could have inspectors doing more important things"</i></div><div><i><br /></i></div><div><i>"....a number of packers would also be very upset about us collecting information on negative [adverse] findings."</i></div><div><br /></div><div>On behalf of USDA, Smith admitted not only that the agency doesn't want the inspectors documenting evidence in real time, but also that the source slaughter plants would be "very upset" if the agency were ever audacious enough to empower inspectors to document evidence with no restrictions.</div><div><br /></div><div>In subsequent years, I've continually pressured the agency to document all source evidence in real time, only to be continually rebuffed. &nbsp;Finally, on Oct. 8, 2010, USDA issued Notice 58-10, which authorized inspectors to collect all source evidence at the time of sample collection. How many years has USDA been inspecting meat, and not followed commonly accepted scientific sampling criteria which require documenting all evidence? &nbsp;Copious documentation of unrestricted evidence should have been part and parcel of USDA's meat inspection program since Day One, but has not. Yet, the agency criticizes Hannaford for its lack of grinding logs.</div><div><br /></div><div>USDA collects routine samples of ground beef for laboratory analysis for E. coli O157:H7, referred to as "verification sampling." From Jan. 1, 2009 to Nov. 30, 2010, the agency's routine verification sampling revealed 64 samples that were positive for E. coli O157:H7. &nbsp;Of these 64, 29 were collected at plants which purchased all their meat from but one slaughter provider. In all 29 cases, USDA refused to do a traceback to the one well-identified source. The agency deliberately refused to go to the source plant and require corrective actions to prevent recurrences. USDA adroitly avoided any enforcement actions at the source plant, in spite of these 29 golden opportunities to protect public health.&nbsp;</div><div>&nbsp;</div><div>Eventually, USDA mismanagement of public health issues caught up to them. On Aug. 3, 2011, USDA Secretary Tom Vilsack gave a speech in Milwaukee, in which he addressed this issue. He stated:</div><div><br /></div><div><span class="Apple-tab-span" style="white-space:pre">	</span><i>"In 90 days, I expect the agency to announce the first step in transforming our traceback policy..."</i></div><div><br /></div><div>The FIRST STEP? &nbsp;You mean to say that after several decades of being in the meat inspection business, that USDA finally decided to embrace traceback protocol in 2011? &nbsp;Yes. &nbsp;Well, what happened at the end of 90 days? No official USDA press releases. But on Dec. 29, 2011, a full 148 days later, USDA sent its traceback suggestions to OMB for approval.</div><div><br /></div><div>Part of the USDA submission was requesting OMB permission to conduct tracebacks when verification sampling revealed the presence of E. coli O157:H7. This awkward revelation shows that USDA perceives it doesn't have the authority to do tracebacks to the source, even when the source has already been clearly identified to be one individual slaughter plant! &nbsp;Yet USDA claims to act with an "abundance of caution" when protecting consumers from foodborne outbreaks.</div><div>&nbsp;&nbsp;</div><div>It is true that USDA referred to "high-risk practices" at Hannaford, but did not state that such practices likely led to the Salmonella outbreak. I am pleased to make this correction. It is only appropriate now that USDA officials publicly state if they believe that Hannaford's practices had ANY connection whatsoever to the introduction of Salmonella into the meat chain. Don't hold your breath. USDA is much more comfortable criticizing Hannaford's allegedly high-risk practices and lack of grinding logs than in admitting that the lack of grinding logs and grinding practices did NOT introduce Salmonella into the meat chain. &nbsp;Hannaford, and its customers, were innocent victims of purchasing and consuming meat which was already laced with Salmonella when the meat arrived at Hannaford receiving departments.</div><div><br /></div><div>The real issue here is USDA's ultra-risky policy of allowing slaughter plants to ship intact meat into commerce which is laced with Salmonella and E. coli O157:H7, and subsequently refusing to do tracebacks to the source.</div><div><br /></div><div>Comparatively speaking, USDA's PR image would have more benefitted by stating that Hannaford's practices likely led to the Salmonella outbreak, than to publicly refer to "high risk" practices. &nbsp;An in-depth discussion of "high risk" provides us the opportunity to reveal that USDA's policies at the source originating slaughter plants constitute the ultimate cause of high risk meat. &nbsp;</div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/does-high-risk-meat-get-usda-endorsement/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/does-high-risk-meat-get-usda-endorsement/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Tue, 07 Feb 2012 01:59:05 -0800</pubDate>
         <author>pdoggy@midrivers.com (John Munsell)</author>
      
      </item>
      
      <item>
         <title>The Cost of Cutting Food Safety</title>
         <description><![CDATA[<div>"There's no money for . . ." well you name it. At a time when all manner of government services are being cut, trillions in bailouts to the financial services industry aside, why should food safety be spared? In fact, food safety protections are being systematically slashed across the board--and while this might achieve some short-term savings, the long-term costs could be catastrophic.</div><div><br /></div><img alt="cutting-budgets-350.jpg" src="http://www.foodsafetynews.com/cutting-budgets-350.jpg" width="350" height="250" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><div>On January 9, the U.S. Department of Agriculture announced it would close 259 offices, laboratories and other facilities to save $60 million in its $145 billion budget. These closings include five of the 15 Food Safety Inspection Service (FSIS) offices. FSIS is responsible for ensuring meat, poultry and egg safety. USDA undersecretary Dr. Elisabeth Hagen said, "There will be no reduction in inspection presence in slaughter and processing facilities and no risk for consumers." Unfortunately, previous inspector cutbacks and FSIS rules to limit the number and detail of inspector reports on industry non-compliance do put consumers at risk, as a recent 36-million pound meat recall attests.</div><div><br /></div><div>Aside from closing offices, the budget cutting axe has weakened agencies in charge of protecting public health. In November, the U.S. Food and Drug Administration stated it cannot afford to withdraw the many animal drugs used non-therapeutically in livestock feed to promote growth and prevent disease. &nbsp;Non-therapeutic use, resulting in meat laced with antibiotic residues, is a factor in increasing human antibiotic resistance. FDA, responding to petitions by medical associations and non-governmental organizations, the first of which were filed in 1999, alleged that the withdrawal of just one drug used in poultry production took five years and $3.3 million, due to industry legal resistance. &nbsp;Instead, FDA proposes to begin a program with animal drug manufacturers to phase-out some drugs voluntarily. Keep Antibiotics Working (KAW), a coalition to which IATP belongs, wrote to FDA protest that the decision violated FDA's public health mandate.&nbsp;</div><div><br /></div><div>In September, USDA announced that budget cuts would curtail or end data collection and reporting on pesticide use on fruits, vegetables and in livestock pens by the National Agricultural Statistics Service (NASS). NASS surveys are used to help formulate food and farm worker safety policy. In November, NASS announced cutbacks to its survey of pesticide and fertilizer use on field crops. Non-governmental organizations protested the cutbacks, saying that the public would be forced to rely on pesticide and fertilizer companies for unverified reporting about agricultural chemical use.&nbsp;</div><div><br /></div><div>Our thin budgetary margin for error in curtailing the spread of foodborne illness was brought home forcefully by the U.S. Centers for Disease Control and Prevention (CDC). The CDC (and its state partners, especially in Colorado) took justifiable pride in tracing back a Listeria monocytogenes infection to the packing facility of a melon farm in Colorado just 10 days after the initial hospital report of listeriosis, which had led to 29 deaths by the end of November.</div><div><br /></div><div>Thomas Frieden, the CDC director, noted in a recent speech that his agency had absorbed the biggest budget cuts in its history in 2010 and 2011. (The U.S. House of Representatives is promising further cuts to the 2012 budget.) Furthermore, "there are 44,000 fewer people working at the state and local level because of the fiscal crisis" in the public health professions. &nbsp;As a result, in Colorado, college students used their own cell phones and a CDC questionnaire to interview those afflicted with listeriosis. The students helped to trace back to a single farm the source of the Listeria, doing work that had previously been done by public health officials.</div><div>&nbsp;&nbsp;</div><div>"How many more cuts to food safety?" -- before students equipped with cell phones and a CDC questionnaire cannot trace back the source of foodborne illness before many more than 29 people die?</div><div>&nbsp;&nbsp;</div><div>It should not take a spike in death or illness from foodborne disease to shock us into recognition that food safety is not cheap, nor can food safety be self-regulated among competing companies. &nbsp;Systematic failure to regulate the financial services industry resulted in ongoing bailouts that have forced FDA and other agencies to claim that rules to protect public health are too expensive, despite plenty of evidence to show the economic and human suffering costs of food safety failures.</div><div><br /></div><div>--------------------------</div><div><br /></div><div><i>Dr. Steve Suppan has been a policy analyst at the Institute for Agriculture and Trade Policy (IATP) since 1994.</i></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/the-cost-of-cutting-food-safety/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/the-cost-of-cutting-food-safety/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Mon, 06 Feb 2012 01:59:07 -0800</pubDate>
         <author>info@foodsafetynews.com (Steve Suppan)</author>
      
      </item>
      
      <item>
         <title>Letter From The Editor: Public Trust</title>
         <description><![CDATA[<div>John Perkins, the long-time police chief of Pocatello, ID, taught me all I needed about the public's right to know.</div><div><br /></div><img alt="wetrust-350.jpg" src="http://www.foodsafetynews.com/wetrust-350.jpg" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" height="200" width="350" /><div>When hired on after college at the Idaho State Journal, I inherited the police beat. It was usually the first beat assignment daily newspapers gave to rookie reporters who did not know anything. I knew a lot less than that.</div><div><br /></div><div>For many months, I wrote for the ISJ, but I worked at the Pocatello Police Department. &nbsp;When I learned I had access to incident reports, arrest reports, jail logs and the like without any restriction, I remember asking Chief Perkins why this daily gold mine of information was freely made available to me. He replied, " 'Cause we are the good guys and if you do your job, the public will trust we are doing ours."</div><div><br /></div><div>Chief Perkins knew more about public trust than all of Washington D.C. and Atlanta GA agency heads with their "transparency" budgets running into the millions. These days we know Americans don't much trust government, especially the one in Washington D.C.</div><div><br /></div><div>Why top federal officials do not try harder to earn that trust is the only mystery.</div><div><br /></div><div>Sadly, in the past six months, we've had performances from two such officials involved in food safety that did not restore trust, but only further opened that gap between the people and their government.</div><div><br /></div><div>I am speaking of Margaret Hamburg, the Food and Drug Administration (FDA) Commissioner, and Robert Tauxe, the Centers for Disease Control and Prevention's (CDC's) deputy director of foodborne, waterborne and environmental diseases.</div><div><br /></div><div>After cantaloupe contamination led to last year's deadly Listeria outbreak, Hamburg defended FDA's lame "ask your retailers" policy for consumers who wanted to find out where those Jensen Farms melons were being sold.&nbsp;</div><div><br /></div><div>As food safety author and microbiologist Phyllis Entis observed, "Consumers should not have to play detective in order to find out whether or not they have been exposed to the risk of infection from a recalled food." That would appear to be especially true for an outbreak where the product being sold at the retail level far outran the distribution area.</div><div><br /></div><div>Then we had this pitiful set of excuses from Tauxe for the reason CDC withheld Taco Bell's name from its report on a 10-state, 70 sickened Salmonella outbreak, where the food source responsible for the illnesses also could not be determined.&nbsp;</div><div><br /></div><div>Lots of other people have commented on this, and I don't mean to pile on. &nbsp;By contacting the state public health departments, and finding one more interested in following its own state law than in currying favor with Atlanta, we were able to report that the CDC's "Restaurant Chain A" was Taco Bell.</div><div>&nbsp;</div><div>Tauxe's rationale that he is the J. Edgar Hoover of public health, able to keep secrets and reel out information to the public when he sees fit, is very dangerous and must be challenged.&nbsp; <br /><br />For goodness sake, many in the public think - presumably incorrectly - that Dr. Tauxe is covering for Taco Bell.<br /></div><div><br /></div><div>Since we outed Taco Bell as "'Restaurant Chain A" and Taco Bell confirmed it, we are wondering how long it will be before CDC updates its Jan. 19 final report on the SE outbreak to include, for the sake of history and researchers, the real name?</div><div><br /></div><div>Or better yet, when might we expect CDC to update its Dec. 8 final report on the cantaloupe Listeria outbreak to include two more of those confirmed infected in the death toll? &nbsp;As the keeper of the final record, CDC should honor the dead by including them and accurately marking both their passing and the lethality of the epidemic.</div><div><br /></div><div>We are not going to hold our breath.</div><div><br /></div><div>But acknowledging public information publicly would be good for CDC. Issuing retail distribution lists for recalled products to assist the public during outbreaks would be good for FDA.</div><div><br /></div><div>Lately, however, neither public agency is doing much to restore the public trust the late Chief Perkins knew should never be lost in the first place.<br /><br />Is there any question why the people are questioning their government?<br /></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/letter-from-the-editor-trust/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/letter-from-the-editor-trust/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Sun, 05 Feb 2012 01:59:03 -0800</pubDate>
         <author>dflynn@foodsafetynews.com (Dan Flynn)</author>
      
      </item>
      
      <item>
         <title>Publisher&apos;s Platform:  How Food Safety Has Changed Since 1993</title>
         <description><![CDATA[I recently participated in "The Conversation", which aired on the local Seattle public television station, KCTS.&nbsp; Enrique Cerna and I talked about how food safety -- and the laws that govern food safety -- have changed since I represented victims of the 1993 Jack in the Box E. coli outbreak.&nbsp; I think it airs opposite of the Superbowl this Sunday.<br /><br /><iframe src="http://www.youtube.com/embed/QRX-Voxkx9s" allowfullscreen="" frameborder="0" height="315" width="560"></iframe>]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/publishers-platform-how-food-safety-has-changed-since-1993/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/publishers-platform-how-food-safety-has-changed-since-1993/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Sun, 05 Feb 2012 01:59:01 -0800</pubDate>
         <author>bmarler@marlerclark.com (Bill Marler)</author>
      
      </item>
      
      <item>
         <title>USDA Inspected and Approved High-Risk Meat</title>
         <description><![CDATA[<div>The Hannaford chain of grocery stores in the Northeast recently recalled ground beef products which were laced with an antibiotic-resistant strain of Salmonella. Like most other retail chains, Hannafords purchases all its meat from outside source slaughter plants.&nbsp;</div><div><br /></div><div>Salmonella and E. coli are &nbsp;"enteric" bacterium, which is defined as originating from within animals' intestines, and is thus present in manure. &nbsp;Live beef arriving at slaughter plants frequently carry a sizeable amount of manure on their hides, creating an obvious risk during hide removal on the kill floor, where airborne enteric bacteria can easily become attached to beef carcasses. &nbsp;And, when hides touch an exposed carcass, bacteria are directly deposited onto carcasses. &nbsp;Retail chains, Hannaford being but one example, do not have intestines or manure-covered hides on their premises. &nbsp;Therefore, we can conclude that Salmonella found in meat at retail meat markets was in all likelihood deposited onto carcasses on the kill floor, and the contamination did not occur at the retail meat market.&nbsp;</div><div><br /></div><div>Furthermore, the current recall of Hannaford meat covers seven states, with 20 reported illnesses. &nbsp;The meat was processed at various Hannaford locations, in several states. &nbsp;What is the probability that each of these Hannaford stores simultaneously introduced this one specific strain of Salmonella into their products, causing the outbreak? &nbsp;Answer: &nbsp;ZERO. &nbsp;However, it does reveal that one of Hannaford suppliers suffered from a monumental breakdown in sanitary dressing procedures on its kill floor on one or more days, producing unsafe meat which was sent to the various Hannaford stores during this brief moment in time.</div><div><br /></div><div>How does USDA view this public health dilemma? &nbsp;USDA has concluded that Hannaford's high risk practices likely lead to this outbreak. &nbsp;Admittedly, Hannaford didn't maintain grinding logs, which if used could have delineated the one source of contaminated meat. &nbsp;Also, when the Hannaford meat cutters processed incoming meat, such as chucks and rounds, Hannaford kept the trimmings and put it into ground beef. &nbsp;Totally legal, as the industry has done this since time immemorial. &nbsp;My plant produced ground beef from trimmings for 59 years, under the watchful eye of USDA inspectors and their supervisors, none of whom objected. &nbsp;Can you imagine buying a half of beef for your home freezer, only to be told that you cannot get any ground beef off that half, because USDA piously proclaims that ground beef produced from trimmings are "high risk" for bacteria?</div><div><br /></div><div>The fact remains that if Hannaford has maintained perfect grinding logs, the outbreak would still have occurred. &nbsp;The outbreak was NOT the result of a lack of grinding logs, but the presence of Salmonella in meat which Hannaford had purchased from a source slaughter provider. &nbsp;And, even if Hannaford had tested the trimmings, and the lab result was negative for Salmonella, no guarantee for safe meat could be issued because labs frequently do not detect the Salmonella. &nbsp;Even the largest beef slaughter plants issue disclaimers that even though their meat is tested, and tested negative, that the plants cannot issue a guarantee of safe meat because a silver bullet has not been developed to develop pathogen-free meat. &nbsp;And, does USDA expect every retail meat market to conduct expensive microbial testing on every batch of ground beef produced? &nbsp;Consider this fact: &nbsp;the largest packers test every 10,000-lb. batch of trimmings by collecting 1 - 2 lbs. of trim for lab analysis. &nbsp;It would only be equitable if every retail market tested 1 - 2 lbs. of ground beef every 10,000 lbs. &nbsp;Would be quite infrequent. &nbsp;What's good for the goose (the source slaughter plant), is good for the gander (the retail meat market).</div><div><br /></div><div>Please also note that when USDA inspectors collect ground beef samples at USDA-inspected establishments for Salmonella analysis, the agency allows up to a 7.5 percent incidence of positives before the agency will commence enforcement actions at the plant. &nbsp;USDA's aloof stance is that if only 7.5 percent of your ground beef is laced with Salmonella, consumers won't be endangered. &nbsp;However, if 8 percent or more of your ground beef has Salmonella, then, only then, will public health be imperiled.</div><div><br /></div><div>CDC statistics show that 10 times as many Americans die from Salmonella as from E. coli. &nbsp;USDA's response to such lethal statistics? &nbsp;First of all, 7.5 percent Salmonella won't hurt anyone. &nbsp;Secondly, the agency assesses all liability for Salmonella- and E.coli-laced meat to the downstream further processor, such as Hannaford. &nbsp;USDA also issues a pass card to the large, source originating slaughter plants. &nbsp;Only when this travesty of food safety justice is aggressively resolved will we Americans experience a lower incidence of foodborne outbreaks.</div><div><br /></div><div>Bottom Line: &nbsp;Hannaford's processing of trim, and lack of grinding logs, did NOT introduce Salmonella into its ground beef. &nbsp;Nevertheless, USDA now accuses Hannaford's allegedly "high risk" practices to be the cause of the current outbreak. &nbsp;This is but the latest in countless examples of USDA's refusal to conduct tracebacks to the SOURCE, that is, to the large slaughter plants. &nbsp;USDA's insistence on assigning all pathogen liability to the downstream further processor virtually guarantees American consumers of future recurring outbreaks.</div><div><br /></div><div>The link below will take you to a blog by Bill Marler, which reveals how USDA blithely blames Hannaford for this outbreak.</div><div><br /></div><div><a href="http://www.marlerblog.com/legal-cases/hannafords-high-risk-practices-likely-lead-to-salmonella-outbreak/">http://www.marlerblog.com/legal-cases/hannafords-high-risk-practices-likely-lead-to-salmonella-outbreak/</a></div><div><br /></div><div>---------------------</div><div><br /></div><div><i>John Munsell oversees the Foundation for Accountability in Regulatory Enforcement, FARE. A version of&nbsp;"USDA Inspected &amp; Passed HIGH RISK Meat" was first posted on Munsell's <a href="http://johnmunsell.com/blog/?p=91">website</a>&nbsp;on Feb. 1, 2012. Reposted with permission.</i></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/usda-inspected-and-passed-high-risk-meat/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/usda-inspected-and-passed-high-risk-meat/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Thu, 02 Feb 2012 01:59:06 -0800</pubDate>
         <author>pdoggy@midrivers.com (John Munsell)</author>
      
      </item>
      
      <item>
         <title>Food Safety: The Industry Must Take Ownership</title>
         <description><![CDATA[<div>With the ongoing economic crisis there has been a need for governments across the globe to cut budgets. Food safety lacks the tangible benefits of, say, health care and it&nbsp;was somewhat inevitable that food inspection agencies would experience the brunt of such cutbacks.</div><div><br /></div><div>In the United Kingdom, the Food Safety Agency that was established in the wake of the "mad cow" disease outbreak, amongst other food safety scares, was essentially dismantled with its portfolio being returned to Ministry of Agriculture (DEFRA).</div><div><br /></div><div>In Canada, the number of CFIA inspectors was increased following the listeriosis outbreak of 2008 in which contaminated deli meats resulted in 20 deaths. However, the Canadian government is now cutting over 200 inspectors in a bid to save $25 million from the federal budget.</div><div><br /></div><div>In the United States, the cutbacks have been deeper, with over 260 USDA offices being closed for a savings of $150 million per year.</div><div><br /></div><div>In reaction, many consumer groups, the press and unions have pronounced the cutbacks as placing the public in danger through the governments neglecting their responsibilities.</div><div><br /></div><div>The old question is thus posed: Does more government involvement, specifically in relation to inspector numbers, lead to a more effective food safety system?</div><div><br /></div><div>A similar question is posed by criminologists in relation to police numbers and crime rates. Those on one side of the argument use statistics to show that an increase in police numbers results in decreased crime rates. However, what is missed is that an increase in policing is commonly preceded by a major event, such as 9/11 or when pre-existing crime levels are high.</div><div><br /></div><div>In other studies, where no major event has occurred, it has been found that there is no correlation between police on the ground and crime rates.</div><div><br /></div><div>The theory goes that high numbers of police on the ground lead to an increased level of crime detection but do little to prevent crime from occurring. As sociologists will indicate, crime rates are mostly affected by the environment, such as socio-economic factors and community cohesion - in effect the existing culture.&nbsp;To take the argument further, it is thought that increasing the level of policing can bring a siege-like atmosphere to a community and negatively affect the community cohesion.</div><div><br /></div><div>Returning to food safety, we can make parallels between the effect of policing on crime rates and superimpose on the number of food inspectors and foodborne illness outbreaks.&nbsp;</div><div>Specifically, inspector numbers increase or reorganization of agencies occurs following a major foodborne illness outbreak.</div><div><br /></div><div>Yet, what is missed is that in the event of an outbreak, it is the industry response that is primarily responsible for enhancing food safety and not visits by an army of food inspectors. Nevertheless, food inspection does play a major role in containing outbreaks and follow-up investigations, although this is different from prevention. &nbsp; &nbsp;</div><div><br /></div><div>Industry-led initiatives are the only way to enhance food safety</div><div><br /></div><div>In the 1980s, there was a diverse range of food safety issues of concern. Foodborne illness rates were increasing, virulent pathogens such as E. coli O157 were taking hold, not to mention the BSE and problems with the emergence of drug-resistant microbes.</div><div><br /></div><div>In response, a directive from President Clinton's administration set to prioritize food safety risks, reduce red tape and bureaucracy. The directive essentially empowered the industry to take responsibility for food safety by introducing HACCP, amongst other initiatives.</div><div><br /></div><div>There is little debate that the initiatives were highly successful in reducing the incidence of foodborne illness with a progressive decrease in numbers since implementation.</div><div><br /></div><div>A more recent example of industry-led initiatives is in relation to the use of antibiotics in animal production. Antibiotics have been commonly used in animal production to prevent infections, thereby leading to high growth rates. However, a negative effect of antibiotics has been the emergence of lethal antibiotic strains of pathogens such as Salmonella, amongst others.</div><div><br /></div><div>The FDA has debated the banning of antibiotics for promoting animal growth for over 30 years. In late 2011, the FDA somewhat unexpectedly stepped back from banning antibiotics in animal production, which is counter to the actions taken over in the EU.</div><div><br /></div><div>Many commentators saw this as a capitulation of the FDA to the lobbying pressure from the meat industry. However, the reality is that the meat industry has been proactive in reducing the use of antibiotics in animal production on the understanding that a staged reduction is required. Of course, this is not well-publicized but illustrates that only a successful antibiotic reduction program can be achieved if led by industry and not by government.&nbsp;</div><div><br /></div><div><b>Empowerment of food safety is the key</b></div><div><br /></div><div>The empowerment of industry to self-regulate always comes under criticism in the event of a foodborne illness outbreak. The knee-jerk reaction always appears to be more testing, more inspectors, more agencies etc.</div><div><br /></div><div>In many ways, "tinkering" with the food safety system by government hinders the progress that has been made since 1995. Ultimately, industry-led initiatives will always be the most effective approach to improve food safety. Consequently, rather than increasing government inspection a more productive strategy is how to remove the weak links in the chain to prevent outbreaks from occurring in the first place.</div><div><br /></div><div>Such a strategy is far from straightforward, as there is a need to understand the underlying basis for decisions made that ultimately led to critical errors of judgment in foodborne illness outbreaks.</div><div><br /></div><div>For example, why do processors send out product known to be contaminated or perform practices that represent obvious food safety risks? In a broad sense, it can be proposed that the actions are through ignorance (lack of knowledge is perhaps a better term) of the risk, economic factors or, in a relatively low number of instances, bioterrorism or criminal intent.</div><div><br /></div><div>Ironically, it is the latter group who have the greatest perception of empowerment given they are controlling events. &nbsp;In contrast, those that lack knowledge may have good intentions in producing high quality products, although fail to see the consequences. It is almost akin to a thought pattern of "nobody told me not to do it."</div><div><br /></div><div>The current trend of clean labels, along with producers of organic products, can be classed in this group, where attempts to produce additive-free foods leads to food safety risks (for example, omitting nitrites to control Clostridium botulinum). &nbsp;Also included in this group are food handlers, quality assurance personnel and management whose main focus is to produce product as fast as possible with little thought of ownership or empowerment.</div><div><br /></div><div>Workers have a tendency to lack empowerment, as they are told what to do and when to do it. This ultimately leads to a disconnect between the product and food safety. In the processing environment, workers are judged on how quickly the product can be processed regardless if the production line is producing ready-to-eat deli meat, cars or paper-clips.</div><div><br /></div><div>Even if food violations occur, there is little incentive for the worker to raise concerns or to be empowered to make suggestions. When visiting processing plants, I sometimes ask the workers if they consume the products produced in the facility. In the majority of cases, the answer is no, due to their prior knowledge of the history of the product.&nbsp;Clearly those workers have a disconnect or lack of ownership with the product.</div><div><br /></div><div>Akin to when the industry is highly regulated by government, the lack of empowerment by food workers throughout an organization ultimately leads to essentially passing-the-buck when it comes to food safety - an "it is not my problem" attitude.</div><div><br /></div><div>It could be argued that empowerment is encompassed in the concept of a food safety culture. Yet "food safety culture" remains a relatively woolly term that lacks the nuts-and-bolts on how to change the behavior of those working in the food industry. There is frequent reference to increasing knowledge by training. However, knowledge and empowerment are very different.&nbsp;</div><div><br /></div><div>Frank Yiannas introduced the term food safety culture, and noted the major challenges in changing worker behavior - after all, it does take a generation. Still every road starts with a first step and rather than look at the loss of government inspectors as entering the Dark Age we should look at this as an opportunity for industry to be empowered to take food safety initiatives to the next level.</div><div><br /></div><div>------------------------ &nbsp;</div><div><br /></div><div><i>Dr. Keith Warriner is an Associate Professor within the Department of Food Science at University of Guelph, Canada.</i></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/02/food-safety-all-a-matter-of-ownership/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/02/food-safety-all-a-matter-of-ownership/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Wed, 01 Feb 2012 01:59:07 -0800</pubDate>
         <author>kwarrine@gmail.com (Keith Warriner)</author>
      
      </item>
      
      <item>
         <title>Why Aren&apos;t We Using Vaccines for E. Coli O157:H7?</title>
         <description><![CDATA[<div>For those who have been working on food safety for years -- even decades -- the promise of a quick-fix holds no allure. &nbsp;Experts know that food safety is multi-faceted, and no silver bullet exists to wipe the scourge of E. coli 0157:H7 from existence. &nbsp;But where promising new technologies could -- in combination with common-sense approaches -- make serious contributions to public health, they should be advanced. &nbsp;Pre-harvest vaccines for E. coli O157:H7 could very well be one of them. &nbsp;So why aren't we using them?</div><div><br /></div><div>At least two promising vaccines for E. coli O157:H7 are awaiting licensing approval from the Center for Veterinary Biologics (CVB) at APHIS. &nbsp;CVB has a long history with animal vaccines, but has primarily focused on those that improve animal health -- not human health. &nbsp;The E. coli vaccines under consideration are not designed to prevent illness in the animal, but could significantly decrease the amount of the pathogen present in the pre-harvest environment, and presumably in the meat that winds up on consumers' plates. &nbsp;Vaccines focusing on public, rather than animal, health represent fairly new ground for the agency. &nbsp;Given the delays in their approval, CVB may be having trouble adjusting its vision.</div><div>&nbsp;&nbsp;</div><div>In a series of conversations with many of the players involved -- representatives from CVB and the pharmaceutical companies awaiting licensure -- CVB's approach has been striking. &nbsp;Far from being enthusiastic about the public health possibilities of pre-harvest vaccines for E. coli, the agency instead seems beleaguered and adrift on the issue, even admitting in one conversation that although there's no scientific downside to the vaccines, there are some economic and practical issues to consider. &nbsp;Perhaps there are economic and practical issues to consider -- but that's not CVB's mission. The fiscal implications and logistical applications to these vaccines are issues for the free market to deal with, and not reasons to delay licensing of promising new technologies that could make a significant public health impact.</div><div>&nbsp;&nbsp;</div><div>The key issue for CVB -- indeed, the only issue the agency has authority to consider -- is whether the vaccines are pure, safe, potent, and effective. &nbsp;In meetings with CVB officials, the agency acknowledges that the vaccines under consideration have cleared the first three hurdles. &nbsp;It's the efficacy that appears to be tripping them up. &nbsp;CVB says that the industry wants an expectation of efficacy that would decrease summer E. coli shedding rates in cattle to approximate winter shedding rates, an efficacy of between 55 and 65 percent. &nbsp;This is a laudable goal, and it's useful to know what the industry would like to see from a new pre-harvest tool to combat contamination. &nbsp;But surely the Food Safety and Inspection Service (FSIS), the agency whose mission is to ensure the safety of meat for consumers, has an opinion on whether that expectation of efficacy is too high, too low, or just right? &nbsp;Unfortunately, CVB doesn't know it. &nbsp;From what we can tell, CVB has a bold new responsibility to consider vaccines with a possibly significant public health impact, but they haven't taken steps toward a meaningful collaboration with the relevant public health agency that sits in the same building to decide how best to exercise that power.</div><div>&nbsp;&nbsp;</div><div>How CVB came into its responsibility for vaccines that have a public health focus (rather than the traditional animal health focus) is somewhat mysterious. &nbsp;Perhaps it was simply that the agency was left without a chair when, in the early 2000s, the music stopped on a debate about where to house these types of animal vaccine approvals. &nbsp;True or not, the agency has entered a new era -- one where their focus on animal health must share the spotlight with a commensurate consideration for public health.</div><div>&nbsp;&nbsp;</div><div>It's time for CVB to embrace that new responsibility, first by re-focusing on its actual statutory mission and away from tangential issues of practicality and economy. &nbsp;Second, the agency must consult with FSIS and gather the relevant stakeholders to discuss how vaccines can make a contribution to public health. &nbsp;Third, CVB should streamline and make more transparent the entire process of vaccine approval, so that interested parties can follow the progress -- or lack thereof -- of promising technologies under consideration.</div><div><br /></div><div>There's no guarantee about these vaccines, but even without a silver bullet, it is possible much progress can still be made. &nbsp;CVB has the authority and the responsibility to put yet another tool in the box to fight the scourge of E. coli. &nbsp;Now the agency must rise to meet its new public health role, by streamlining, prioritizing, and publicizing the vaccine approval process for those technologies that could have a significant impact on public health.</div><div><br /></div><div><br /></div><div>Here's a&nbsp;<a href="http://www.foodsafetynews.com/CSPI%20Letter%20to%20Vilsack%20re%20CVB%20Vaccine%20Approvals-1.pdf">letter</a>&nbsp;written by the Center for Science in the Public Interest to USDA Secretary Tom Vilsack about the delay in vaccine approvals.</div><div><br /></div><div>--------------</div><div><br /></div><div><div><i>Sarah A. Klein, J.D., M.A. is Staff Attorney, Food Safety Program, at the</i></div><div><i>Center for Science in the Public Interest</i></div></div><div><br /></div><div><br /></div><div><br /></div><div><br /></div><div><br /></div><div><br /></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/musical-chairs-did-the-wrong-agency-get-picked-to-protect-public-health/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/musical-chairs-did-the-wrong-agency-get-picked-to-protect-public-health/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Mon, 30 Jan 2012 01:59:01 -0800</pubDate>
         <author>sklein@cspinet.org (Sarah Klein)</author>
      
      </item>
      
      <item>
         <title>Publisher&apos;s Platform: What Are Utah, New Hampshire Afraid Of?</title>
         <description><![CDATA[<div>This past week, I read Utah's S.B. 34 titled "Production and Sale of Food in Utah Revisions," along with its New Hampshire counterpart, H.B. 1650-FN, called "Commerce in Food in New Hampshire." &nbsp;As any lawyer would, I immediately asked myself, "what are these pieces of legislation really trying to do?," and, of course, "are they constitutional?" &nbsp;I'll get to those questions in a moment. &nbsp;Here are the two bills:</div><div><br /></div><img alt="constitution_quill_pen-370.jpg" src="http://www.foodsafetynews.com/constitution_quill_pen-370.jpg" width="362" height="238" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><div><b>The Utah bill</b>, <a href="http://le.utah.gov/~2012/bills/sbillint/sb0034.pdf">S.B. 34</a>:</div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre">	</span>Prohibits federal regulation of an agricultural product that remains in Utah after it is made, grown, or produced in Utah;</div><div>•<span class="Apple-tab-span" style="white-space:pre">	</span>Allows a person to identify certain agricultural products by indicating that the products are "Made in Utah," "Grown in Utah," or "Produced in Utah;"</div><div>•<span class="Apple-tab-span" style="white-space:pre">	</span>Prohibits a person from claiming that an agricultural product was made, grown, or produced in Utah if the product is not a Utah agricultural product; and</div><div>•<span class="Apple-tab-span" style="white-space:pre">	</span>Makes it a class A misdemeanor for a person to enforce federal regulation of a Utah agricultural product that remains in Utah.</div><div><br /></div><div>Under the bill, the definition of "Utah agricultural product" is an agricultural product that is entirely, (i) made in Utah, (ii) grown in Utah, (iii) produced in Utah or produced with an insignificant part of a basic or generic material that is acquired from outside of Utah.</div><div><br /></div><div>I guess that could mean made/grown/produced in Utah and a little bit in China?</div><div>&nbsp;&nbsp;</div><div>Perhaps even more problematic than SB 34's possible conflict with Congress's power under the Commerce Clause, is that SB 34 creates criminal liability for state or local officers trying to enforce federal law. This is a conflict with federal law if ever there was one, presuming, of course, that Congress (and its statutorily created agencies, the FDA and USDA) had the constitutional power to regulate the conduct in the first place.</div><div><br /></div><div><b>The New Hampshire bill</b>, <a href="http://www.gencourt.state.nh.us/legislation/2012/HB1650.html">HB 1650-FN</a>:</div><div><br /></div><div>Like Utah's bill, this bill seeks to&nbsp;</div><div><br /></div><div>•<span class="Apple-tab-span" style="white-space:pre">	</span>Exempt foodstuffs grown or produced, and then sold, in New Hampshire from federal regulation if the product is labeled "Made in New Hampshire;" and,</div><div>•<span class="Apple-tab-span" style="white-space:pre">	</span>Provides penalties for both agents attempting to enforce federal regulations and for producers and processors who label their food as "Made in New Hampshire" when it does not meet "Made in New Hampshire" requirements.</div><div><br /></div><div>According to the preamble, the purpose of the New Hampshire bill is to allow for locally produced food products to be sold and consumed within New Hampshire and to encourage the expansion and accessibility of farmers' markets, roadside stands, farm and home-based sales, and producer-to-end-consumer agricultural sales.</div><div><br /></div><div>First, these bills seem to lack any clear point. &nbsp;The sale of local food certainly is not improperly impeded by the fact that there are federal laws that bear on the production of that food. And clearly, these bills are not motivated by a concern for the public's safety. Instead, these bills are just a effort to piecemeal these states out of an entirely constitutional regulatory scheme that, like it or not (and pretty clearly, they don't like it) allows for federal regulation and oversight over a broad range of food producers and food producing activities. &nbsp;Even New Hampshire's slogan "Live Free or Die" must recognize the federal government's constitutional role in our society.</div><div>&nbsp;</div><div>On that point, exactly what is the federal government's power to control the methods and manners by which our food is produced and sold? &nbsp;Most will immediately jump to the Commerce Clause of the U.S. Constitution. Undoubtedly, this powerful set of words is a part of the equation, but it is only a part. The federal government not only has plenary (meaning complete and all encompassing) power over interstate commerce -- i.e. commerce between the states -- but also can constitutionally undertake any act, so long as it does not infringe on some individual right guaranteed by the bill of rights or some power granted to another branch of government, that is "necessary and proper" to the furtherance of its enumerated power over interstate commerce.</div><div>&nbsp;&nbsp;</div><div>Just words? Think again. A little more history: &nbsp;The federal government is one of enumerated powers, meaning that it can act only where it has the constitutional authority to do so. &nbsp;As James Madison wrote:</div><div><br /></div><div><i>[t]he powers delegated by the proposed Constitution to the federal government are few and defined. &nbsp;Those which are to remain in the State governments are numerous and indefinite.</i></div><div><br /></div><div>The Federalist No. 45, pp. 292-293 (C. Rossiter ed. 1961). &nbsp;Among the powers specifically delegated to the federal government is the power "[t]o regulate Commerce with foreign Nations, and among the several States, and with the Indian Tribes." &nbsp;U.S. CONST. art. I, § 8, cl. 3. &nbsp;The "commerce clause" has, of course, become a particularly potent regulatory enabler that, as a result, has spawned a notoriously complex body of case law. <i>See generally United States v. Lopez</i>, 514 U.S. 549 (1994) (Kennedy, J., concurring). For present purposes, however, it suffices to say that the Commerce Clause has provided the constitutional authority for a great many landmark legislative and regulatory measures.</div><div><br /></div><div>The Supreme Court's interpretation of these powers has produced a complex line of case law that contemplates the rightful regulation of things that appear to be even <i>intrastate</i> matters--i.e. local actions that do not involve the sales of goods and services across state lines--as long as those matters have a "substantial economic effect on <i>interstate commerce</i>." &nbsp;<i>See Wickard v. Filburn,</i> 317 U.S. 111, 125 (1942) (emphasis added). &nbsp; "[E]ven if appellee's activity be local and though it may not be regarded as commerce, it may still, whatever its nature, be reached by Congress if it exerts a substantial economic effect on interstate commerce." &nbsp;Id.</div><div><br /></div><div>This is mere food for thought, as it remains to be seen how the actions that are seemingly insulated from federal reach by the Utah and New Hampshire bills actually affect interstate commerce. &nbsp;The crafting of the Utah and New Hampshire legislation to require the production (well, maybe not all of it) of the food in state and that it be consumed or remain in state (hmm, what about Internet sales and roadside stands or farmer's markets near state borders?), at most allows these states to walk a fine line around the Commerce Clause.</div><div><br /></div><div>And then, again, there are the provisions in these bills that seek to criminalize any action taken to enforce a federal law that is in conflict with the dictates of these bills. &nbsp;Even the bills themselves acknowledge the potential tension with the Supremacy Clause of the U.S. Constitution (Article VI, Section 2): &nbsp;"This Constitution, and the Laws of the United States . . . shall be the supreme Law of the Land; and the Judges in every State shall be bound thereby, any Thing in the Constitution or Laws of any State to the Contrary notwithstanding."</div><div><br /></div><div>The Utah bill's legislative analysis acknowledges that the United States Supreme Court has "long recognized that state laws that conflict with federal law are 'without effect,' " <i>Altria Group, Inc. v. Good,</i> 555 U.S. 70, 76 (2008), quoting <i>Maryland v. Louisiana</i>, 451 U.S. 725, 746 (1981), and has further held that an individual cannot be guilty of a state crime if the individual was acting necessarily and properly under the authority of the laws of the United States. <i>Cunningham v. Neagle</i>, 135 U.S. 1, 75 (1890).</div><div><br /></div><div>The only relevant question is whether Congress, again through its statutorily created agencies FDA and USDA, has the power to regulate, or create the law that is in conflict with the Utah or New Hampshire law, in the first place. &nbsp;If so, there is an unconstitutional conflict with the Supremacy Clause, and these states laws are of no force and effect.</div><div><br /></div><div>Again, on this question the Necessary and Proper Clause speaks loudly. Properly created federal agencies like the FDA and USDA have the constitutional power to make any regulation that is both necessary and proper to the effectuation of its constitutional authority over interstate commerce. &nbsp;And this, as the Supreme Court said in <i>Wickard v. Filburn</i>, potentially reaches even activities that appear purely local in character.</div><div>&nbsp;&nbsp;</div><div>At best, the Utah and New Hampshire bills raise a number of Constitutional concerns. &nbsp;At worst, we should all just view these bills for what they really are: &nbsp;likely misguided attempts to address the concerns of just a few about feared governmental intrusion into our private lives. &nbsp;I'm all for freedom, but not every guy who espouses the power of his constitutional rights and liberties is correct in his analysis of constitutional jurisprudence. &nbsp;I would say that the supporters of these bills have conscientiously walked a fine line between constitutional right and wrong, and have done so in a basically empty manner.</div><div>&nbsp;&nbsp;</div><div>What do these bills really accomplish?</div><div><br /></div><div>More to the point, what are Utah and New Hampshire farmers and food producers afraid of? &nbsp;Are they really afraid of the FDA and FSIS regulating food safety within the state, especially when it is likely that the food may cross state boundaries? &nbsp;And, why would the legislatures even consider laws that are likely unconstitutional? &nbsp;Is it to curry favor with constituents, or stick a thumb in Uncle Sam's eye?</div><div><br /></div><div>The point should be to produce safe food, not to push legislation that essentially meaningless.</div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/publishers-platform-what-does-utah-new-hampshire-agriculture-fear/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/publishers-platform-what-does-utah-new-hampshire-agriculture-fear/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Sun, 29 Jan 2012 01:59:01 -0800</pubDate>
         <author>bmarler@marlerclark.com (Bill Marler)</author>
      
      </item>
      
      <item>
         <title>Beer Wholesalers Join Public Health to Oppose Four Loko Settlement</title>
         <description><![CDATA[<div>Last month, the Federal Trade Commission took public comments on a <a href="http://www.ftc.gov/opa/2011/10/fourloko.shtm">proposed settlement</a> with the alcohol company Phusion Projects, which makes a beverage line called <a href="http://www.drinkfour.com/">Four Loko</a>.&nbsp;</div><img alt="fourloko4.png" src="http://www.foodsafetynews.com/fourloko4.png" width="320" height="210" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><div>You might recall in 2010 how that product gained much notoriety for sending <a href="http://articles.latimes.com/2010/oct/27/nation/la-na-blackout-in-a-can-20101027">scores of college students</a> to the emergency room as a result of its dangerous combination of alcohol with caffeine. In a rare victory of government action in favor of public safety, in November 2010, the <a href="http://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm234109.htm">Food and Drug Administration</a> forced Phusion and other companies to remove the caffeine. (Read my case study <a href="http://alcoholjustice.org/images/stories/AEDreportFINAL_1.pdf">here</a>.) But of course, the story doesn't end there, as these companies always have another trick up their sleeve to get youth hooked.</div><div><br /></div><div>Now, the "caffeine-free" versions of these <a href="http://www.drugfree.org/join-together/alcohol/alcohol-watchdogs-target-supersized-alcopops-as-urgent-issue">highly sweet, soda-like concoctions known as alcopops</a> have grown to high-octane super-size cans, containing as much as 4-5 servings of alcohol, and all for the price of a cheap beer. Public health advocates, policymakers, and state attorneys general have been trying to bring these products down to size through a variety of legal measures. Now comes the Federal Trade Commission with its proposed <a href="http://www.ftc.gov/os/caselist/1123084/111003phusionagree.pdf">agreement</a> with Phusion Projects, not to actually reduce the container size or amount of alcohol. But rather, to require better <a href="http://www.ftc.gov/os/caselist/1123084/111003phusionexhibitb.pdf">labeling</a>, which will serve as a great advertisement.</div><div><br /></div><div>That's why I asked colleagues and groups to sign on my <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00010-80865.pdf">letter</a> in opposition to the proposal. Numerous <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/index.shtm">others</a> submitted similar comments raising many objections, including the <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00249-81753.pdf">American Medical Association</a>, the <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00262-81844.pdf">New York City health department</a>, and <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00261-81832.pdf">Public Health Law and Policy</a>. Most importantly, a strong group of state attorneys general who have been working on this issue for years raised five pages worth of objections in their impressive <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00241-81707.pdf">letter</a>. (It was thanks to these state officials that FDA acted on the caffeine.)</div><div><br /></div><div>In addition, several industry members took the side of public health, and not just for the usual self-serving reasons. For several years, I called upon beer wholesalers to speak out against dangerous products such as caffeinated alcoholic beverages. While several business owners expressed to me privately that they hated these youth-oriented beverages, (and the bad publicity that accompanies them) none took a public stand against them. I am therefore happy to report that the National Beer Wholesalers Association, a powerful lobbying group, wrote a pretty strong letter to oppose the agreement. From their <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00260-81831.pdf">comments</a>:</div><div><br /></div><div><i>The label contemplated by the proposed settlement could actually serve to entice consumers, especially younger ones seeking high-alcohol, low-priced products, to possibly over consume these products</i>.</div><div><br /></div><div>This important point made by myself and others is not the sort of rhetoric we are used to hearing from the likes of beer lobbyists. In addition to this large trade group being on the right side of the issue, several individual beer distributors also opposed the settlement. For example, John Dickerson, a distributor based in Ohio signed on to my letter. Also, Robert Archer, president of Blue Ridge Beverage, wrote his own very strong <a href="http://www.ftc.gov/os/comments/phusionprojectsconsent/00240-81702.pdf">letter</a>, saying that "the issues surrounding large containers and high alcohol content are not effectively addressed simply by putting a 'message' on the container." His comments are especially significant because Archer is next in line to become chair of the National Beer Wholesalers Association.</div><div><br /></div><div>As someone whose work is centered around criticizing industry for its misdeeds and disingenuous pro-health positions, it's rare for me to give praise. But this show of support for public health from beer wholesalers and their lobbyists is genuine, and should be applauded as a true sign of progress.</div><div><br /></div><div>Let's hope the Federal Trade Commission hears our collective concerns and either proposes a more effective solution or allows states to assert their legal authority to do a better job.</div><div><br /></div><div>----------------------------</div><div><br /></div><div><i>Michele Simon is a public health lawyer specializing in industry marketing and lobbying tactics. She is the author of "Appetite for Profit: How the Food Industry Undermines Our Health and How to Fight Back" and president of Eat Drink Politics, a consulting firm. <a href="http://www.appetiteforprofit.com/2012/01/15/beer-wholesalers-join-public-health-to-oppose-four-loko-settlement/">"Beer Wholesalers Join Public Health to Oppose Four Loko Settlement"</a> was first posted on her website, Appetite for Profit, on Jan. 17, 2012.</i></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/beer-wholesalers-join-public-health-to-oppose-four-loko-settlement/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/beer-wholesalers-join-public-health-to-oppose-four-loko-settlement/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Thu, 26 Jan 2012 01:59:07 -0800</pubDate>
         <author>michele@informedeating.org (Michele Simon)</author>
      
      </item>
      
      <item>
         <title>Serious Questions About Third-Party Audits</title>
         <description><![CDATA[<div>On Jan. 10, 2012, a Congressional House <a href="http://democrats.energycommerce.house.gov/sites/default/files/documents/Report_Listeria_01.10.11.pdf">report was issued on the government's investigation into the cantaloupe Listeria outbreak</a>. The report provided some very interesting findings and lessons not only for and about Jensen Farms but for and about the industry as a whole.</div><div><br /></div><img alt="thirdpartyaudits-featured.jpg" src="http://www.foodsafetynews.com/thirdpartyaudits-featured.jpg" width="308" height="200" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><div>Conducted by the Congressional Committee on Energy and Commerce, the investigation included a review of documents from and interviews with FDA; Jensen Farms; its distributor, Frontera Produce; and its third-party auditor, Primus Labs. And it was the information obtained from and about the audits that was highlighted as of most significant issue - and concern - in the report. The report was accompanied by a <a href="http://democrats.energycommerce.house.gov/sites/default/files/documents/Letter_Hamburg_01.10.11.pdf">Letter from the Committee to FDA Commissioner Margaret Hamburg </a>that further emphasized concern around the use of third-party auditors. The letter to Commissioner Hamburg stated:</div><div><br /></div><div>"We urge you to review closely the information uncovered during our investigation. In particular, the investigation identified significant problems with the third-party inspection system used by growers and distributors ... FDA officials identified "serious design flaws" in the processing technique used at Jensen Farms and "poor sanitary design of the facility itself" as the causes of the contamination, and they indicated that "everything that was found wrong was addressed in FDA guidance" published in 2009. Yet these flawed facility designs and processing techniques were both recommended by and rated as "superior" by the third-party auditor of Jensen Farms.</div><div><br /></div><div>This finding revealed two major industry problem areas:</div><div>&nbsp;</div><div><b>1. Failures in the industry's auditing system</b></div><div><br /></div><div>As the letter states "The auditing failed in the case of the recent Listeria outbreak." These failures are itemized as the auditors:</div><div><br /></div><div>- missing or failing to prioritize important food safety deficiencies</div><div><br /></div><div>- lacking any regulatory authority and not reporting identified problems to any regulatory authority</div><div><br /></div><div>- not ensuring that identified problems were resolved</div><div><br /></div><div>- providing advance notice of site visits</div><div><br /></div><div>- spending only a short period of time on-site</div><div><br /></div><div>- multiple conflicts of interest</div><div><br /></div><div>In defense, Jerry Walzel, the president of Bio Food Safety, Inc., the subcontractor hired by Primus Labs to conduct the Jensen Farms audit, stated that consistent with Primus Labs policy - the audits only deducted from the score if a method or technique was inconsistent with FDA regulations; they did not deduct from the score if FDA guidance was not being followed - which brings up the second major issue.</div><div><br /></div><div><b>2. The perception of guidance vs. regulation</b></div><div><br /></div><div>The auditors' findings were not based on the practices of the best farms and failed to ensure that the producer met FDA guidance.</div><div><br /></div><div>I don't believe that Walzel's additional statement that "guidelines are opinions ... regulations are law" is indicative of the perception and practices followed by the industry and/or its auditors. But if that is a view, the consequence will herald the end of self-policing and ensure that all GMPs and guidance documents become regulation.</div><div><br /></div><div>The issue of what to do about FDA guidance vs. regulations is not new. The fact that "one does not have to follow guidance" is true in a literal sense. But from a practical perspective, any company that does not follow FDA guidance is, quite frankly, looking for trouble. In fact, whether or not this is indicative of majority perception, the fact remains that it was unfortunately stated as defense in an outbreak that sickened 146 people in 28 states, killed 30, and caused a miscarriage; that an official of a leading auditing agency told the committee that his company "did not consider FDA guidance when conducting audits;" and that a processor with "serious design flaws" passed its audit with a 96 percent and no deficiencies noted or corrective action stated. Aside from the human tragedy associated with this outbreak, this report and the accompanying letter are another black eye for third-party audit systems. This is a sad reflection of a system that has much to add to food safety and public health. If not to assure food safety, what is the purpose of third-party audits on which so much of the industry depends?</div><div><br /></div><div>Additionally, each of the Jensen Farm or third-party audit failures noted by the committee raises further question, the answers of which will impact the entire industry. For example, in noting the auditors' failure to report problems to regulatory authorities, the question to be asked is - If you are in a food plant and see an obvious Class I hazard, do you have an obligation to report it? Although <a href="http://www.fda.gov/Food/FoodSafety/FSMA/ucm247548.htm#SEC307">FSMA Section 307, Accreditation of Third-Party Auditors</a>, states that the results of a regulatory third-party audit are to determine if the facility can be certified, while the results of a consultative audit "are for internal purposes only," does the consultative auditor still hold a legal responsibility to report Class I hazards to FDA? This is a question to which there does not yet appear to be a clear answer, but has wide ranging implications if the answer is "yes."</div><div><br /></div><div>It is through FSMA that Congress expects FDA to fix these failures. As the letter explains, FSMA requires that FDA establish an accreditation system and model auditing standards for third-party audits of imported foods. However, the standards are expected to influence domestic audits as well, and the committee suggested that "FDA consider developing a voluntary model program for domestic auditors that could become the standard of care for third-party auditing programs in the United States."</div><div><br /></div><div>We have to hope that the details will be clearly and comprehensively specified when the regulatory language of the section is published. And we should all hope that, for the sake of the food industry and the consumer, that the setting of robust standards for these foreign audits - and auditors, will put third-party audits in a good light and not become a source of constant criticism and doubt. There are already some robust third-party audit programs, but those who are looking for problems don't differentiate the good from the bad, and thus Congressional focus, such as happened recently, is nothing but damaging to a system that has great capacity to protect both brands and public health.&nbsp;</div><div><br /></div><div>-----------------</div><div><br /></div><div><i>Dr. David Acheson, former FDA Associate Commission for Foods, is Managing Director for Food and Import Safety at &nbsp;Leavitt Partners LLC. " Investigation of Cantaloupe Listeria Outbreak Has Congress Asking Serious Questions Around Third Party Audits" &nbsp;first appeared on the <a href="http://leavittpartnersblog.com/2012/01/investigation-of-cantaloupe-listeria-outbreak-has-congress-asking-serious-questions-around-third-party-audits/">Leavitt Partners blog</a> Jan. 19, 2012.</i></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/serious-questions-about-third-party-audits/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/serious-questions-about-third-party-audits/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Wed, 25 Jan 2012 01:59:01 -0800</pubDate>
         <author>david@leavittpartners.com (Dr. David W. K. Acheson)</author>
      
      </item>
      
      <item>
         <title>Is Honesty the Best Policy in Foodborne Illness Investigations?</title>
         <description><![CDATA[One of the most important protections we have against foodborne illness is our disease-surveillance systems. These systems field reports from widespread sources and may include disease-reporting registries, local and state health departments, the Centers for Disease Control and Prevention (CDC), and utilize active outreach to clinicians and hospitals.<br /><br /><img alt="truth-epidemiology406.jpg" src="http://www.foodsafetynews.com/truth-epidemiology406.jpg" class="mt-image-left" style="float: left; margin: 0pt 20px 20px 0pt;" height="250" width="406" />The data collected often reveal associations in time, place, person, and illness in the population. Such can lead an investigator to valuable information to stop outbreaks from continuing, but only if the data is accurate, properly understood, and acted upon.<br /><br />Outbreaks usually have a defined course and chain of events, and when data are plotted, they will reveal onset dates, peaks and the tailing away of cases. The data may also reveal the immediate source of a contaminated food, allowing consumers to protect themselves if the information is made public. The epidemiologist is in a critical situation when they have data that supports a hypothesis that an outbreak of disease is occurring. <br /><br />As surveillance improves, thanks to better diagnostics and more effective reporting, we now see a marked increase in foodborne illness outbreaks that come to light through an epidemiological approach. <br /><br />Historically, the most fundamental finding in a foodborne outbreak investigation is the isolation of the causative organism from both victims and foods. When this detail is at hand, they provide strong associations between victims and likely causes. In such cases, the epidemiologist has traditionally made that information public. This allows the public to make a choice, helps in further case finding, and allows the removal of affected products.<br /><br />But the gold standard is difficult to obtain, and only a fraction of the actual foodborne outbreaks known to occur have a confirmed cause; this success being dependent on the shelf life of the food items, the ability to isolate the pathogens from food, and other factors.<br /><br />The Peanut Corporation of America (PCA) caused a deadly and long-lasting outbreak with its peanut butter products in 2007-2008. Cases continued over several weeks before the CDC -- in tandem with Team Diarrhea -- made the associations with King Nut, and eventually PCA.&nbsp; The question was repeatedly asked, "Why did it take so long for the outbreak to be recognized?" The delay drew the attention of some notables in epidemiology and led to criticism in CDC's epidemiological approach. <br /><br />On the other hand, recently a state health investigator pointed to a Salmonella outbreak in Cantaloupe without the causative agent being isolated. A detailed trace-back of cases led to strong associations between the importer and those made ill. The importer, who was named in the press, <a href="http://www.foodsafetynews.com/2011/08/del-monte-goes-after-oregon-for-cantaloupe-recall/">sued the epidemiologist</a>, but <a href="http://www.foodsafetynews.com/2011/09/oregon-dismisses-complaint-against-epidemiologist/">later dropped the suit</a>.<br /><br />These shots across the bow of epidemiology are still apparently resounding. <br /><br />Now we learn CDC and health departments in 10 states investigated an outbreak of 70 cases of Salmonella, but kept the process secret, and <a href="http://www.foodsafetynews.com/2012/01/who-is-restaurant-chain-a-maybe-its-not-taco-bell/">now will not reveal the name of the implicated restaurant</a>. While it is clear that epidemiology as a science has limitations, the data can also be convincing, especially when there are clusters of cases that point to a common immediate source. Withholding the name of the immediate source, even when specific foods cannot be identified, does little to protect the public from immediate hazards or to find solutions to future occurrences.<br /><br />While epidemiology is a powerful tool, it is one that can also backfire. In the international outbreak of E coli in sprouts last year, we saw the quandary epidemiologists faced. European officials jumped the gun several times. In good faith, they <a href="http://www.foodsafetynews.com/2011/10/profile-of-germanys-catastrophic-sproutbreak/">implicated a wide variety of possible vehicles and sources before finally identifying the source</a> of contamination in a totally different country, and in a totally different product than was first thought (sprouts not cucumbers).<br /><br />In the nationwide US outbreak of peppers/tomatoes in 2008, associations between tomatoes and cases became less and less likely as more cases of salmonellosis in persons eating peppers came to light. The effect on the tomato industry was dramatic, with losses in the untold millions.<br /><br />When public health officials make mistakes in foodborne outbreaks, the industry suffers and the political fallout is extreme. To the extent that they do not act to protect the public, they fail their mission. We should not forget that local officials are closely tied to their communities in many ways. Local health departments rely on revenue generated from the local food service industry. After many years, bonds form between local public health agencies and industry, naturally, and out of necessity. When a regulator is compelled by the evidence and must take on the health protection role, he can find it painful. The wrong word -- "strawberries instead of blueberries" can cost one their position. Therefore, it is not unreasonable for the regulator to be stuck in a "damned if you do, and damned if you don't" situation, especially if he is a local.<br /><br />In the end, honesty is the best policy during any outbreak of disease. When the investigator is guided by a careful analysis of data, an honest presentation of the facts and truthful explanation is all we can ask for.&nbsp; Consumers demand no less from CDC.&nbsp; Perhaps there needs to be "whistleblower protections" for CDC from lawsuits (ironically, this protection is afforded now by the FSMA-but only to workers in FDA-regulated facilities).<br /><br />It's in the best interest of everyone to work together in crisis times like these in food safety. The public understands and forgives a mistake when it occurs out an abundance of caution to protect them, but there is no forgiveness for a failure to inform them and they suffer as a result. The failure of CDC to name names is preventing the redress that victims rightfully have for damages and also reflects the power industry has to keep our investigators silent.<br /><br />___<br />Roy Costa is the founder and owner of the consulting firm Environ Health Associates, Inc. Mr. Costa is a registered professional sanitarian with 30 years of environmental heath practice in the academic, government and private sectors. Mr. Costa is an educator and food safety trainer with International experience in a number of countries.<br /> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/is-honesty-the-best-policy-in-foodborne-illness-investigations/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/is-honesty-the-best-policy-in-foodborne-illness-investigations/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Tue, 24 Jan 2012 01:59:04 -0800</pubDate>
         <author>rcosta1@cfl.rr.com (Roy Costa, RS, MS, (MBA))</author>
      
      </item>
      
      <item>
         <title>An Open Letter to the U.S. CDC</title>
         <description><![CDATA[<div>Last week, CDC released two "Final Update" reports on Salmonella outbreak investigations within a 48-hour period.</div><div><br /></div><div>The first report, released on January 17th, summarized the results of an investigation into a 10-month long <a href="http://www.foodsafetynews.com/2012/01/salmonella-linked-to-laboratories-infected-109-over-11-months/">outbreak of Salmonella Typhimurium associated with exposure to clinical and teaching microbiology laboratories</a>. The second report, released on January 19th, presented the results of an investigation into a 2-month long <a href="http://www.foodsafetynews.com/2012/01/cdc-mum-about-fast-food-mexican-chain-in-salmonella-outbreak/">multi-state outbreak of Salmonella Enteritidis infections linked to a restaurant chain</a>.</div><div><br /></div><div>These two outbreaks had very little in common with each other; the outbreak settings were different, the scope and duration of the outbreaks were different, and the source of the infections was different. Nevertheless, the two outbreaks have one very important thing in common.</div><div><br /></div><div>CDC, in conjunction with at least some of its public health partners at the state and local level, has chosen to withhold important information from the public.</div><div><br /></div><div>What information has CDC withheld, and why should this information be released? Here is a list of questions that I sent to my media contact at CDC on January 18th, the day after the Salmonella Typhimurium outbreak report was released.</div><div><br /></div><div>Is there a specific reason why CDC is not specifying the identity of the commercial strain of Salmonella Typhimurium that is associated with this outbreak (by the ATCC or NCTC strain number - not the commercial supplier)? Can you provide me with the strain number ID?</div><div><br />Does CDC have any hypothesis as to the trigger for this outbreak? Most of the commercial strains have been in use in various labs for many years. What may have happened to initiate the increase in cases? What determined the start date? With a baseline rate for the outbreak strain of 0 to 4 reports/week, how were the start and ending date established for this outbreak?</div><div><br /></div><div>Were the outbreak cases all tied to the same commercial source of the S. Typhimurium "Strain X"?</div><div><br /></div><div>Were the outbreak cases tied to the use of a specific format of the commercial source (for example, Bacti-discs or pre-filled inoculation loops)?</div><div><br /></div><div>Have any cases involving this same strain been reported to CDC since the last "outbreak" case on June 29, 2011? If so, how has CDC differentiated those cases from the outbreak cases (keeping in mind the baseline of 0-4 cases per week mentioned in the CDC report).</div><div><br />Were the bulk of the cases linked to student labs or to clinical labs?</div><div><br /></div><div>To these questions, I would now add, "Were the clinical lab cases tied mainly to in-hospital labs, or to free-standing commercial clinical labs? If the latter, was any single commercial lab chain disproportionately involved?"</div><div><br /></div><div>When the Salmonella Enteritidis restaurant chain outbreak report hit the internet, I again contacted my CDC media liaison and asked, "Can you please explain why CDC has not revealed the name of the restaurant chain implicated in the above-mentioned outbreak? Even better, can you identify the chain by name?"</div><div><br /></div><div>I realize that both outbreaks are "over" and that at least some of this information now is academic. Nevertheless, I question CDC's actions in withholding information that could influence purchasing decisions on the part of consumers and of medical and lab professionals.</div><div><br /></div><div>CDC reported on January 19th that Restaurant Chain A's handling and cooking processes likely ruled out ground beef as a source of the Salmonella Enteritidis outbreak. This is favorable to the restaurant chain, and would give consumers comfort that the restaurants belonging to this fast food chain are following appropriate food-handling procedures--if only CDC had released the name of the chain.</div><div><br /></div><div>As for the lab-related outbreak, if I was still running a microbiology lab, I would certainly want to know whether a specific packaging or format of commercially available control culture was more prone to contaminating the lab surroundings than others. I would opt to avoid this format, if I had the information and the choice. Likewise, as a medical doctor, I would opt to avoid a commercial clinical lab chain that was prone to in-lab contamination.</div><div><br /></div><div>If either of these outbreaks had been traced to a specific packaged food, the offending food would have been named. There is no logical reason for restaurant-linked outbreaks to be handled differently. There is no logical reason for a lab-related outbreak to be handled differently.</div><div><br /></div><div>I would appreciate receiving substantive answers to my questions.</div><div><br /></div><div>Sincerely yours,</div><div><br /></div><div>Phyllis Entis, MSc., SM(NRCM)</div><div><a href="http://efoodalert.net/2012/01/21/an-open-letter-to-the-u-s-cdc/">eFoodAlert</a></div><div><br /></div><div>---------------</div><div><i>Reposted, with permission, from eFoodAlert</i></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/an-open-letter-to-the-us-cdc/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/an-open-letter-to-the-us-cdc/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Mon, 23 Jan 2012 01:59:07 -0800</pubDate>
         <author>phyllisentis@gmail.com (Phyllis Entis)</author>
      
      </item>
      
      <item>
         <title>Publisher&apos;s Platform:  Safe Employees = Safe Food</title>
         <description><![CDATA[When the Associated Press reported this week that an owner of Jensen Farms was being fined by the U.S. Department of Labor for failing to provide safe migrant worker housing, I must admit even I was a bit shocked.&nbsp; Could it be that an owner of a business that allowed a deadly fecal bacterium, <a href="http://www.about-listeria.com/">Listeria</a>, to coat its product would treat its employees like crap, too? &nbsp;<br /><br />Well, apparently yes.&nbsp; It seems that Eric Jensen, the Colorado Cantaloupe grower whose product caused an outbreak that sickened 146 people and killed 30 (by my count 32), rented migrant workers unsanitary, overcrowded rooms at a motel he owns. Inspectors said many rooms lacked beds, laundry facilities and smoke detectors. Jensen now faces a whopping $4,250 in civil penalties.&nbsp; As the Labor Department's Denver director said:<br /><br /><div align="center"><i>"Profiting at the expense of vulnerable workers is not just inhumane, it's illegal."</i><br /></div><br />I would add immoral and really, really stupid--especially when it comes to producing safe food.<br /><br />Lest we forget, the FDA and the staff of the House Energy and Commerce Subcommittee found a number of safety lapses at Jensen Farms that likely led to the outbreak:<br /><br /><img alt="safety-first-406x250.jpg" src="http://www.foodsafetynews.com/safety-first-406x250.jpg" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" height="250" width="406" />-&nbsp; Condensation from cooling systems draining directly onto the floor,<br /><br />-&nbsp; Poor drainage resulting in water pooling around the food processing equipment,<br /><br />-&nbsp; Inappropriate food processing equipment which was difficult to clean (i.e., Listeria found on the felt roller brushes),<br /><br />-&nbsp; No antimicrobial solution, such as chlorine, in the water used to wash the cantaloupes,<br /><br />-&nbsp; No equipment to remove field heat from the cantaloupes before they were placed into  cold storage, and<br /><br />-&nbsp; FDA officials were highly critical of the processing methods used at Jensen Farms. According to these FDA officials, the probable causes of the melon contamination at Jensen Farms included "serious design flaws" in the processing technique used at Jensen Farms, "poor sanitary design of the facility itself," and "lack of awareness of food safety standards by Jensen Farms." In particular, FDA emphasized to Committee staff that the processing equipment and the decision not to chlorinate the water used to wash the cantaloupes were two probable causes of the contamination.<br /><br />Hmm, does this sound familiar to you?&nbsp; Remember the sickening of 1939 people with <a href="http://www.about-salmonella.com/">Salmonella</a> and the recall of 500,000,000 eggs in 2010 linked to Iowa's Wright County Egg?&nbsp; Who could forget the FDA inspection report highlights of some of its findings at Wright County:<br /><br />-&nbsp; Chicken manure located in the manure pits below the egg laying operations was observed to be approximately 4 feet high to 8 feet high at the following locations: Layer 1 - House 1; Layer 3 - Houses 2, 7, 17, and 18. The outside access doors to the manure pits at these locations had been pushed out by the weight of the manure, leaving open access to wildlife or domesticated animals,<br /><br />-&nbsp; Un-baited, unsealed holes appearing to be rodent burrows located along the second floor baseboards were observed inside Layer 1 - Houses 1-9 and 11-13; Layer 2 - Houses 7 and 11; Layer 3 - Houses 1, 3, 4, 5, and 6; Layer 4 - House 3,<br /><br />-&nbsp; Dark liquid which appeared to be manure was observed seeping through the concrete foundation to the outside of the laying houses at the following locations: Layer 1 - Houses 1, 2, 3, 4, 5, 8, 11, 12, and 14; and Layer 3 - Houses 1, 8, 13, and 17,<br /><br />-&nbsp; Standing water approximately 3 inches deep was observed at the southeast corner of the manure pit located inside Layer 1 - House 13,<br /><br />-&nbsp; Un-caged birds (chickens having escaped) were observed in the egg laying operations in contact with the egg laying birds at Layer 3 - Houses 9 and 16. The un-caged birds were using the manure, which was approximately 8 feet high, to access the egg laying area,<br /><br />-&nbsp; Layer 3 - House 11, the house entrance door to access both House 11 and 12 was blocked with excessive amounts of manure in the manure pits,<br /><br />-&nbsp; There were between 2 to 5 live mice observed inside the egg laying Houses 1, 2, 3, 5, 7, 9, 10, 11, and 14, and<br /><br />-&nbsp; Live and dead flies too numerous to count were observed at the following locations inside the egg laying houses: Layer 1 - Houses 3, 4, 6, 8, 9, 11, and 12; Layer 2 - Houses 7 and 11; Layer 3 - Houses 3, 4, 4, 5, 7, 8, 15, 16, 17, and 18. The live flies were on and around egg belts, feed, shell eggs and walkways in the different sections of each egg laying area. In addition, live and dead maggots too numerous to count were observed on the manure pit floor located in Layer 2 - House 7.<br /><br />And, guess what else - the owner of Wright County, Jack DeCoster, cared little for his employees, too.&nbsp; A few examples:<br /><br />- In 1997, DeCoster Egg Farms agreed to pay $2 million in fines to settle citations brought in 1996 for health and safety violations at DeCoster's farm in Turner, Maine. Then-Labor Secretary Robert Reich said conditions were:<br /><br /><div align="center"><i>"As dangerous and oppressive as any sweatshop." <br /></i></div><br />- In 2002, the federal Equal Employment Opportunity Commission announced a more than $1.5 million settlement of an employment discrimination lawsuit against DeCoster Farms on behalf of Mexican women who reported they were subjected to sexual harassment, including rape, abuse and retaliation by some supervisory workers at DeCoster's Wright County plants.<br /><br />And, who can forget Stewart Parnell and the Peanut Corporation of America Salmonella outbreak of 2009 that sickened 714 persons in 46 states, killing nine.&nbsp; The FDA reported that the company shipped tainted products under three conditions: (1) without retesting, (2) before the re-test results came back from an outside company, and (3) after a second test showed no bacterial contamination.<br /><br />One PCA employee was quoted:<br /><br /><div align="center"><i>"I never ate the peanut butter, and I wouldn't allow my kids to eat it."<br /></i></div><br />My strong suspicion is that Jensen Farms workers were not eating Jensen Farms cantaloupes as they sat in their overcrowded hotel rooms.&nbsp; And, I would be willing to bet that Wright County employees were not taking a dozen eggs home to the family from work.<br /><br />Perhaps there is a lesson here.&nbsp; Perhaps how you treat your employees and how the employees feel about your product together say volumes about the quality and safety of the product.&nbsp; If the employees will not eat the product, perhaps the product should simply not be sold.<br /><br /> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/publishers-platform-safe-employees-safe-food/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/publishers-platform-safe-employees-safe-food/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Sun, 22 Jan 2012 01:59:01 -0800</pubDate>
         <author>bmarler@marlerclark.com (Bill Marler)</author>
      
      </item>
      
      <item>
         <title>A Budget Neutral, Better Way to Boost Food Safety</title>
         <description><![CDATA[<div>Food Safety News, citing the <a href="http://www.hagstromreport.com/">Hagstrom Report</a>&nbsp;newsletter, said <a href="http://www.foodsafetynews.com/2012/01/omb-says-food-agency-consolidation-is-next/">on Jan. 14</a> that the Obama Administration may be considering a plan to merge the functions of food safety as currently performed at the U.S. Department of Agriculture's Food Safety and Inspection Service (FSIS) and the Department of Health and Human Services Food and Drug Administration (FDA) into one large single food safety agency, located within FDA.</div><div>&nbsp;</div><div>The General Accountability Office (GAO) released <a href="http://www.foodsafetynews.com/2011/03/call-for-one-food-safety-agency-leads-historic-gao-report/">a 345-page report</a> to Congress in March, 2011, that proposed changes in efficiencies in federal programs that would save us tax payers $200,000,000,000. I will confess I have not and will not read the entire report. My interests are limited to the 4-5 pages in the report on food safety.</div><div><br /></div><div>In those few pages, the GAO calls for a single food safety agency at the federal level, but the $200 billion in savings is not impacted by this suggestion. Their proposal for a single food safety system is budget neutral.</div><div><br /></div><div>And herein lies the rub. Meat and poultry plants must have daily, continuous inspection to operate. It is the law. If a single food safety agency combines employees, duties and dollars, FDA can do nothing more than it is currently doing. Nothing will change.</div><div><br /></div><div>Food Safety News posted <a href="http://www.foodsafetynews.com/2012/01/single-food-agency-a-recipe-for-singular-disaster/">an op-ed by me</a> on Monday, Jan. 16, that was in opposition to a single food safety agency. Since I have publicly professed to detest complainers who bring nothing to the table to solve problems, here are my thoughts on what real change could look like and still be budget neutral:&nbsp;</div><div><br /></div><div>The GAO report cites the massive <a href="http://www.cdc.gov/salmonella/enteritidis/">Iowa-based Salmonella egg recall</a> and outbreak as a perfect example of the fragmented food safety inspection system, and it is a great example.</div><div><br /></div><div>But it does not take a single food safety system to place all eggs under the USDA. Congress "scrambled" the egg inspection system back in 1970 when it passed the Egg Products Inspection Act that gave egg products to the USDA and shell eggs to the FDA. They can unscramble this situation by putting all eggs under the USDA. Simple move, no mess, and it would address a problem that became elevated in the public's eye in 2010.</div><div><br /></div><div>They can also put all animals, including bison, fish and seafood, under the USDA and add all products from animals to the USDA list. That would bring all dairy products, eggs and even casings under USDA/FSIS daily continuous inspection.</div><div><br /></div><div>Currently casings (animal intestines), all fish except catfish, and bison, unless they pay for FSIS inspection, are under FDA's regulatory authority. Yes, by law FSIS has catfish but not bison. See, we don't need a massive single food safety agency to correct these silly deficiencies. We just need some common sense.</div><div><br /></div><div>Congress could also say that any meat or poultry product that has been inspected at least twice and cooked as a final kill step under FSIS inspection does not need to be inspected again when used to make soup, flavorings, baby food, packaged sandwiches, pizzas etc.</div><div>&nbsp;</div><div>There is currently a system called dual jurisdiction at work in many facilities. Let's look at pizza as just one example.</div><div><br /></div><div>A company makes frozen vegetarian pizza and gets no inspection by FDA. Add shrimp and still no inspection. The tomatoes may come from Mexico, the peppers from Chile, the onions from Guatemala and the shrimp from Thailand.</div><div>&nbsp;</div><div>Add a little pepperoni from an American plant, pepperoni with the USDA mark of inspection on it, and you add the need for daily, continuous FSIS inspection -- but just for the conveyor belt carrying the pepperoni pizza.</div><div><br /></div><div>Same goes for canned soup, baby food, etc. It is gross overkill to require inspection for chicken noodle soup but not for tomato soup, and it has nothing to do with protecting the public's health.</div><div><br /></div><div>The inspection system is totally arbitrary when it comes to corn dogs and bagel dogs, open-face and closed-face sandwiches. Exactly the same product, just different packaging, resulting in either no inspection or daily inspection.</div><div><br /></div><div>I don't know for certain, but I believe that if USDA removed all the inspectors at the dual jurisdiction plants and put them to work on fish and seafood, eggs and dairy products inspection, it would not only make those products safer, but would probably not increase the cost of food safety.</div><div>&nbsp;</div><div>Nearly 80 percent of all the fish and seafood we consume is imported. Almost none is inspected as it arrives in this country, and certainly the number of countries exporting these products is not limited in any way.</div><div><br /></div><div>If under USDA authority, these countries would first have to have an equivalent food safety system, including daily, continuous federal inspection. Then they would be subjected to annual audits, and the products they export to the U.S. would be re-inspected at an FSIS import house. Just like meat and poultry are today. Food safety would be improved, and the cost is covered by not having vegetable beef soup receive a level of inspection that is simply not needed.</div><div><br /></div><div>Laws mandating daily, continuous inspection for meat and poultry were passed many decades ago, long before PulseNet (the national surveillance system for foodborne outbreaks) and improved epidemiology revealed that many foodborne illnesses are from produce and other sources, and that meat and poultry are not necessarily the most important carriers of pathogens that can kill us.</div><div><br /></div><div>We need change, with this I agree, but we do not need change that substantially increases cost and does not increase efficiencies and effectiveness in the federal food safety system.&nbsp;</div><div><br /></div><div>We should not waste time and effort on a single food safety agency that Congress and many food safety experts simply will not support, but instead we should focus on who should do what and why and, as another Nebraskan is famous for saying, &nbsp;just "git 'er done."</div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/a-budget-neutral-better-way-to-boost-food-safety/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/a-budget-neutral-better-way-to-boost-food-safety/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Thu, 19 Jan 2012 01:59:01 -0800</pubDate>
         <author>rainman2x11@gmail.com (Dr. Richard Raymond)</author>
      
      </item>
      
      <item>
         <title>Cuts in Public Health Preparedness Could Hurt Food Industry</title>
         <description><![CDATA[<div>Although preparedness for public health emergencies had been on an upward climb in the U.S. over the last decade, some of our most elementary capabilities are experiencing cuts in every state across the country. This includes the ability to identify and contain outbreaks, provide vaccines and medications during emergencies, and treat people during mass traumas.</div><div><br /></div><div>So says the ninth annual, <a href="http://www.healthyamericans.org/assets/files/TFAH2011ReadyorNot_09.pdf">"Ready or Not 2011: Protecting The Public's Health From Diseases, Disasters, and Bioterrorism,"</a> issued by Trust for America's Health, a non-profit, non-partisan organization dedicated to preventing epidemics to protect people, and Robert Wood Foundation, devoted to improving American's health and health care.</div><div><br /></div><div>While this may appear like less oversight and regulatory presence for the food industry and, thus, a blessing in disguise, the overall consequences for the industry are not good. The general finding of the report is that federal and state budget cuts have put public health preparedness at risk. Although the focus is on general health initiatives, the relevance to preparedness and response in potential foodborne outbreaks or bioterrorist threats to the food chain can't be ignored.</div><div><br /></div><div>In fact, every one of the report's key findings has such relevance:</div><div><br /></div><div>1. 51 cities -- in 40 states -- are at risk for elimination of Cities Readiness Initiative funds, which support the ability to rapidly distribute and administer vaccinations and medications during emergencies.</div><div><br /></div><div>2. All 10 state labs with "Level 1" chemical threat testing status are at risk for losing top level capabilities, which could leave the U.S. Centers for Disease Control (CDC) with the only public health lab in the country with full chemical testing capabilities.</div><div><br /></div><div><i><b>Food Industry Relevance:</b> If there were to be a deliberate attack on the food supply, these reductions could have a grave impact on response readiness, impacting the federal and state governments' abilities to assist the industry in its food defense efforts.</i></div><div><br /></div><div>3. 24 states are at risk of losing expert epidemiology support, which has supplemented state and local gaps in the past.</div><div><br /></div><div><i><b>Food Industry Relevance:</b> A loss of such support would also have an impact on the availability to investigate foodborne illness outbreaks, again reducing assistance and response capabilities.</i></div><div><br /></div><div>4. Academic preparedness research and training centers are at risk due to budget cuts.</div><div><br /></div><div><i><b>Food Industry Relevance:</b> Anything that erodes such research and training strains the preparedness for food-related issues as well.</i></div><div><br /></div><div>5. Potential cuts to the National Center for Environmental Health (NCEH) mean the ability for the U.S. Centers for Disease Control and Prevention (CDC) to mount a comprehensive response to nuclear detonation, radiological attacks, chemical attacks and natural disasters is at risk.</div><div><br /></div><div><i><b>Food Industry Relevance:</b> NCEH also plays an important role in retail food safety work. Such an impact on the end of the food supply chain has a direct impact on the consumer that food safety and defense are designed to protect. A quick look at the NCEH web site demonstrates their role in food safety.</i></div><div><br /></div><div>6. 40 states and Washington, D.C. cut their state public health budgets -- 29 states cut their budgets for a second year in a row, 15 for three years in a row.</div><div><br /></div><div>7. 41 states had cuts in state and local preparedness support through the Public Health Emergency and Preparedness (PHEP) grants from FY 2010 to FY 2011.</div><div><br /></div><div>8. All 50 states and Washington, D.C. had cuts in the Hospital Preparedness Program (HPP) from FY 2010 to FY 2011.</div><div><br /></div><div><i><b>Food Industry Relevance:</b> These general cuts directly affect the ability for the state response to any foodborne outbreak.</i></div><div><br /></div><div>As mentioned, some in the food industry may see such cuts as a good thing, reducing federal and state ability to conduct inspections and thus decreasing the chance of finding problems in a plant.</div><div><br /></div><div>However, when an outbreak starts, the earlier a potential foodborne illness problem can be found, the more likely it will be able to be contained, and the less potential impact it will have on the food company's brand and litigation risk.</div><div><br /></div><div>If we were to even focus only on the impact to the food company, it has to be said that while the illness or death of even one or two consumers is bad for business, an outbreak that sickens hundreds or kills tens of people will be many times worse. Focusing back on the consumer, not only are any deaths a horrible thing, but as discussed in a previous newsletter, <a href="http://leavittpartnersblog.com/2011/12/challenges-of-state-partnerships-reflect-needed-focus-for-food-safety-and-consumer-confidence/">"Challenges of State Partnerships Reflect Needed Focus for Food Safety and Consumer Confidence,"</a> consumer confidence in food safety is already at a low; any increase in outbreaks will only make it worse, and, regardless of budget cuts, serve to force an increase in federal and state focus.</div><div><br /></div><div>The inclination to drop one's guard when inspections are at a low can be related to the inclination to speed when one knows that budget cuts have reduced a city's ability to keep patrol officers on the highway. Everything is fine, until that high speed leads to a multi-car pile-up.</div><div><br /></div><div>From a public health perspective, the key findings of this report should be seen as a warning trend. Should such cuts and reduction continue and spread, it could have a significant impact on the entire food industry.</div><div><br /></div><div>---------------------------------</div><div><br /></div><div><i>Dr. David Acheson, former FDA Associate Commission for Foods, is Managing Director for Food and Import Safety at &nbsp;Leavitt Partners LLC. "Cuts in Funding for Public Health Preparedness Likely to Have Negative Impact on the Food Industry" first appeared on the <a href="http://leavittpartnersblog.com/2012/01/cuts-in-funding-for-public-health-preparedness-likely-to-have-negative-impact-on-the-food-industry-2/">Leavitt Partners blog</a> Jan. 11, 2012.</i></div><div><br /></div><div><br /></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/cuts-in-public-health-preparedness-likely-to-hurt-food-industry/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/cuts-in-public-health-preparedness-likely-to-hurt-food-industry/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Wed, 18 Jan 2012 01:59:01 -0800</pubDate>
         <author>david@leavittpartners.com (Dr. David W. K. Acheson)</author>
      
      </item>
      
      <item>
         <title>The Latest in Meat Safety: Another Form of Zapping? </title>
         <description><![CDATA[<div>Bacterial contamination of meat is an ongoing problem and everyone wishes for an easy fix--one that does not require meat producers and packers to prevent contamination.</div><div><br /></div><div>Irradiation works, but raises feasibility and other concerns.</div><div><br /></div><div>How about electrocution?</div><div><br /></div><div><a href="http://www.foodproductiondaily.com/content/view/print/603656">Food Production Daily</a> reports that hitting meat with electrical current reduces toxic E. coli O157:H7 on meat surfaces by 2 log units.</div><div><br /></div><div><a href="http://www.inderscience.com/search/index.php?action=record&amp;rec_id=44624&amp;prevQuery=&amp;ps=10&amp;m=or">The research report says researchers inoculated meat</a> with the bacteria and then applied electrical current. &nbsp;But by inoculation they must mean just on the surface, because they only counted surface bacteria.</div><div><br /></div><div>Surface bacteria, alas, are not the problem. &nbsp;Searing meat effectively kills surface bacteria. &nbsp; Bacteria in the interior (of hamburger, for example) survive unless the meat is well cooked.</div><div><br /></div><div>And 2 log units is unlikely to be good enough for bacteria that cause harm at low doses, as this kind does. &nbsp;The FDA requires a 5 log reduction for fresh juices, for example.</div><div><br /></div><div>I wish researchers would apply their talents to figuring out how to keep toxic bacteria from getting into and onto animals in the first place. &nbsp;Then we wouldn't have to worry about designing techno-fixes to deal with contaminated meat.</div><div><br /></div><div>-----------------------</div><div><a href="http://www.foodpolitics.com/2012/01/the-latest-in-meat-safety-another-form-of-zapping/">"The Latest in Meat Safety: Another Form of Zapping?"</a> first appeared on Marion Nestle's Food Politics blog Jan. 16, 2012. Reposted with permission.</div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/the-latest-in-meat-safety-another-form-of-zapping/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/the-latest-in-meat-safety-another-form-of-zapping/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Tue, 17 Jan 2012 01:59:07 -0800</pubDate>
         <author>marion.nestle@nyu.edu (Marion Nestle)</author>
      
      </item>
      
      <item>
         <title>Is Walmart&apos;s March into Cities Helping or Hurting?</title>
         <description><![CDATA[<div>Having saturated the rural landscape, shuttering local stores in small town America along the way, now, in the wake of stagnant sales and increased competition, Walmart desperately <a href="http://www.bloomberg.com/news/2010-11-18/wal-mart-stores-to-open-sites-in-washington-d-c-.html">needs to expand into urban markets</a>.&nbsp;</div><div><br /></div><img alt="lonelyshoppingcart-350.jpg" src="http://www.foodsafetynews.com/lonelyshoppingcart-350.jpg" width="350" height="200" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><div>And what better urban market than one full of eight million people? While the big box retailer is eager to enter the Big Apple, challenges loom large. Given the negative reputation Walmart has earned for being hostile to workers among other problems, many New Yorkers are <a href="http://walmartfreenyc.com/">skeptical</a>, to put it mildly.&nbsp;</div><div><br /></div><div>To counter the opposition, Walmart is positioning itself as the solution to urban food deserts - areas where finding real food is next to impossible. But as Anna Lappé has eloquently <a href="http://www.huffingtonpost.com/anna-lappe/walmart-pr-blitz_b_812380.html">argued</a>, the big box chain isn't the answer: "Let's be clear, expanding into so-called food deserts is an expansion strategy for Walmart. It's not a charitable move."</div><div><br /></div><div><b>Research Shows Walmart Kills Both Jobs and Food Access</b></div><div><br /></div><div>Now a <a href="http://www.libertycontrol.net/uploads/mbp/WALMARTREPORT.pdf">report</a> released last month by Manhattan Borough President Scott Stringer concludes that not only would bringing Walmart to Harlem spell disaster for labor, but it could also make an already <a href="http://www.nyc.gov/html/doh/downloads/pdf/dpho/dpho-harlem-report2007.pdf">dire food access problem</a> there even worse.&nbsp;</div><div><br /></div><div>Based on data from Chicago's negative experience, the report found that within two years of a Walmart store opening in New York:</div><div><br /></div><div>-&nbsp;Between 48 and 66 fresh food retailers could go out of business, representing a net loss of between 56,500 to 82,000 square feet of food retail within a one-mile radius;</div><div><br /></div><div>-&nbsp;Closure of these stores would represent a loss of 50 to 57 percent of the fresh food retail square footage added in recent years by New York City's incentive program;&nbsp;</div><div><br /></div><div>-&nbsp;All of this would negate more than $4 million in public finance investment and four years of effort to improve fresh food access in the area.</div><div><br /></div><div>As Stringer <a href="http://scottmstringer.tumblr.com/post/14270934207/examining-the-impact-of-a-potential-walmart-in">explained</a>, Walmart shouldn't be undermining city programs to improve fresh food availability: "Walmart would be a bane, not a boon, to the health food economy of Harlem - or any other New York City neighborhood."</div><div><br /></div><div>Moreover, previous economic analysis has shown that Walmart's promise of jobs doesn't pan out either. In a report from last summer called <a href="http://www.alignny.org/wp-content/uploads/2011/09/The-Walmartization-of-NYC-Sep-2011.pdf">"The Walmartization of New York City,"</a> researchers at the City University of New York concluded that, "despite Walmart's promises of jobs and lower prices for the community, the longer term impact is actually the opposite."&nbsp;</div><div><br /></div><div>Assuming Walmart opened the 159 stores needed to reach 21 percent grocery market share in New York City (the same proportion the company enjoys nationally), the impact would be a net loss of almost 4,000 jobs, and a loss of more than $453 million in wages per year for all remaining workers.&nbsp;</div><div><br /></div><div>What about the new Walmart jobs? According to the report, 4,279 new low-wage Walmart workers would have to "rely on social services to make ends meet, costing New York taxpayers over $4 million per year" in health care benefits alone. This, in a city where the mayor has asked for $2 billion in <a href="http://www.bloomberg.com/news/2011-10-04/bloomberg-seeks-2-billion-of-nyc-spending-cuts-hiring-freeze.html">budget cuts</a>.&nbsp;</div><div><br /></div><div><b>Current Walmart Locations Confirm Bleak Outlook</b></div><div><br /></div><div>Other areas of the country have already had real world experiences to back up these projected findings. According to New York's Food for Thought <a href="http://www.libertycontrol.net/uploads/mbp/WALMARTREPORT.pdf">report</a>, of all the employers in Ohio, Walmart has the greatest number of associates and dependents enrolled in Medicaid, which in 2009 cost taxpayers $44.8 million.&nbsp;</div><div><br /></div><div>Similarly, a 2004 study found that for each of California's whopping 44,000 Walmart employees, taxpayers had to spend $730 on health care and $1,222 on other forms of state and federal assistance such as (ironically) food stamps.&nbsp;</div><div><br /></div><div>In 2006, Walmart entered Chicago and recently convinced local officials to approve two additional locations, including (<a href="http://www.nytimes.com/2010/06/25/business/25walmart.html">after a long battle</a>) on the city's South Side. How have things fared so far in the original Chicago location? Not so well.</div><div><br /></div><div>A three-year <a href="http://www.luc.edu/umc/newsroom/releases/010710_walmart.shtml">study</a> released by Loyola University Chicago in 2010 revealed that Walmart had not enhanced retail activity or even employment opportunities. In fact, "the probability of a local retailer going out of business during the study period was significantly higher for establishments close to Walmart's location." Specifically, researchers found that a nearby business had about a 40 percent chance of closing over a two-year period - not very good odds.</div><div><br /></div><div><b>If You Can't Beat Them, Buy Them</b></div><div><br /></div><div>Of course Walmart paints an entirely different picture, and is spending a ton of money to hide these sobering facts in a massive PR campaign. According to the Walmartization <a href="http://www.alignny.org/wp-content/uploads/2011/09/The-Walmartization-of-NYC-Sep-2011.pdf">report</a>, in the first half of 2011 alone, the company spent $2.1 million lobbying in New York, as much as they spent there in the past four years combined. There's even a dedicated <a href="http://www.walmartnyc.com/">website</a> complete with a <a href="http://www.walmartnyc.com/another-day-another-flawed-study/">"fact-checker"</a> and the heartwarming tagline, "Helping NYC Save Money and Live Better."&nbsp;</div><div><br /></div><div>Philanthropy is another time-honored corporate tactic, often used to buy silence from critics, curry favor with community leaders, or, in this case, grease the wheels to gain entry into a reluctant-but-lucrative market.&nbsp;</div><div><br /></div><div>In December, Walmart <a href="http://www.walmartnyc.com/nyc-charities-receive-250000-from-the-walmart-foundation/">announced</a> a combined gift of $250,000 to five various New York City charities, including a home food delivery service and a soup kitchen. Of course $250K is chump change to a company whose net sales <a href="http://investors.walmartstores.com/phoenix.zhtml?c=112761&amp;p=irol-newsArticle&amp;ID=1392384&amp;highlight=">topped $405 billion in 2010</a>, but to these five groups it no doubt means a lot. Moreover, in its <a href="http://www.walmartnyc.com/nyc-charities-receive-250000-from-the-walmart-foundation/">press release</a>, Walmart made sure to point out the company's "more than $13 million" in donations in New York City since 2007. (Similarly, Walmart <a href="http://www.inthesetimes.com/working/entry/6196/after_hard-fought_chicago_victory_wal-mart_eyes_urban_expansion/">pledged</a> to donate $20 million to Chicago charities.)&nbsp;</div><div><br /></div><div>But Walmart will need a lot more than a few million dollars in tax-deductible contributions to make up for all the job losses, decrease in available fresh food (and even <a href="http://money.msn.com/saving-money-tips/post.aspx?post=ccafecf9-541d-44e1-8ba5-2e84e3d969d9">increased obesity</a>) that could befall New Yorkers.&nbsp;</div><div><br /></div><div>Other cities should also brace themselves, as the company is <a href="http://www.bloomberg.com/news/2010-11-18/wal-mart-stores-to-open-sites-in-washington-d-c-.html">opening four stores in Washington, D.C.</a> later this year, with additional area sites planned. Other locations on the agenda include <a href="http://walmartwatch.org/blog/archives/community-activists-call-attention-to-walmarts-urban-expansion-plans/">Boston</a> and <a href="http://articles.sfgate.com/2010-09-21/business/24013607_1_walmart-wal-mart-stores-grocery-stores">San Francisco</a>. But mostly the company is keeping quiet about its urban expansion agenda, at least publicly. Last year in Boston, the company was said to be <a href="http://www.bostonherald.com/business/general/view/20110128wal-mart_seeks_opening_chains_moves_toward_hub_draw_ire_from_jobs_group/srvc=home&amp;position=also">"quietly chatting up city officials"</a> while scouting neighborhoods.&nbsp;</div><div><br /></div><div>I shudder to think of the consequences to American's already suffering urban populations if Walmart succeeds in duplicating its rural retail takeover. What to do about it? Support the <a href="http://www.ufcw.org/">United Food and Commercial Workers</a>, which has an important campaign called <a href="http://makingchangeatwalmart.org/">Making Change at Walmart</a>. See also the <a href="http://www.bigboxtoolkit.com/">Big Box Tool Kit,</a> which is chock-full of news and practical resources. Communities can work together to fight back, we just have to act before it's too late.&nbsp;</div><div>---------------------</div><div><br /></div><div><i>Michele Simon is a public health lawyer specializing in industry marketing and lobbying tactics. She is the author of "Appetite for Profit: How the Food Industry Undermines Our Health and How to Fight Back" and president of Eat Drink Politics, a consulting firm. Her website is <a href="http://www.appetiteforprofit.com/">Appetite for Profit</a>.</i></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/want-to-decrease-food-access-while-killing-jobs-open-a-walmart/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/want-to-decrease-food-access-while-killing-jobs-open-a-walmart/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Tue, 17 Jan 2012 01:59:01 -0800</pubDate>
         <author>michele@informedeating.org (Michele Simon)</author>
      
      </item>
      
      <item>
         <title>Single Food Agency a Recipe for Singular Disaster?</title>
         <description><![CDATA[<div><div>Food Safety News Editor Dan Flynn <a href="http://www.foodsafetynews.com/2012/01/omb-says-food-agency-consolidation-is-next/">reported</a> on Jan. 14, 2012 that if Congress gives the Obama Administration the authority to consolidate six agencies that deal with international trade into one agency, bringing together the two major food safety agencies into one would follow.</div><div><br /></div><div>This possible move is not totally unexpected from this Administration, nor was the way the Office of Management and Budget's (OMB) thinking was leaked to The Hagstrom Report by a consumer advocate a surprise. What is a surprise to me is that Food &amp; Water Watch was the only consumer advocacy group quoted in the report, which basically fingers them as the leak.</div><div><br /></div><div>The consumer advocate is reported to have said that the OMB wants to move the Food Safety and Inspection Service (FSIS), currently located in the U.S. Department of Agriculture on the nation's Mall, north to Maryland to become part of the Food and Drug Administration (FDA), which is a branch of the Department of Health and Human Services.</div><div><br /></div><div>Most consumer groups will support this move if it develops, although Food &amp; Water Watch said it would &nbsp;"urge against consolidating food safety functions" at this time.</div><div><br /></div><div>A strong proponent of such a move will be Mike Taylor, a former acting Undersecretary for Food Safety at the USDA and the current Deputy Commissioner for Foods at the FDA. Mike and I appeared together on many panels debating food safety in 2007-2008 and at every opportunity he advocated for a single food safety agency located "anywhere but at the USDA."&nbsp;</div><div><br /></div><div>Caroline Smith-DeWaal , Director of Food Safety at Center of Science in the Public Interest, also joined us in several panels and is another strong proponent for a single food safety agency. And the list goes on.</div><div><br /></div><div>It is my sincere belief that a merger of the two food safety agencies would be an unmitigated disaster in the short term because the cultures are so very different. And unless megadollars flowed with the merger, nothing more could be accomplished than is currently done.&nbsp;</div><div><br /></div><div>And there are dozens of other valid reasons to "just say no" to the Administration's thinking.</div><div><br /></div><div>If you have not yet clicked on the link provided in the first paragraph, do so now to better understand why I am afraid of this proposal, as is Carol Tucker-Foreman, who responded to the article with an in-depth comment, a spot-on discussion of why this talk is so scary to those who know the players.&nbsp;</div><div><br /></div><div>FSIS regulates by inspection and enforcement. Their daily presence in nearly every single meat and poultry plant in this country is mandated by law and funded by Congress. They can shutter a plant simply by having the inspectors not show up for work.</div><div><br /></div><div>FDA regulates by education and writing Good Manufacturing Practices and suggesting policies to follow when producing food. Foods like sprouts, cantaloupe, peanut butter and shell eggs come to mind. And FDA inspection is either by a state entity, a third-party auditor paid by the company or themselves when an outbreak is recognized.</div><div><br /></div><div>The FDA has no mandate in inspection or audit frequency, and very little in funding to do so. And therefore they very rarely inspect or audit unless a disaster mandates it.</div><div><br /></div><div>This is not to say one agency is better than the other. They are very different entities, and the laws that they follow are very different also. To blend them into one might be like mixing oil and water.</div><div><br /></div><div>And that brings me to personalities. There has been some obvious tension and conflict between the two agencies and some of their leaders for decades. Those feelings will not disappear with a Presidential mandate.</div><div>&nbsp;</div><div>A very simple example of this is the dual jurisdiction plants. It should be simple to decide if all pizza should be inspected daily, if no pizza needs inspection, or if we should just inspect pizza with meat on it. The same could be said for soups and baby foods. But alas, it is not simple. And a single food safety agency will not change the laws that allow this ridiculous situation to continue.&nbsp;</div><div><br /></div><div>It is often said by those wanting a single food safety agency that there are anywhere from 12-17 agencies involved in food safety. But in reality, 99.9 percent of what we eat is regulated by either FSIS or FDA.</div><div><br /></div><div>Unless you count alcohol as one of your six basic food types, I do not know why the Bureau of Alcohol, Tobacco and Firearms keeps showing up on these lists. Or the EPA, which does have the ability to shut down Gulf Coast commercial fishing when there is an oil spill, but most of our fish comes from overseas anyway.&nbsp;</div><div><br /></div><div>The story in Food Safety News mentioned that Obama's plan includes moving the National Oceanic and Atmospheric Administration, or NOAA, from the Commerce Department to Interior and bringing "all salmon regulation into one agency."</div><div><br /></div><div>I think NOAA just has marine authority for fishing regulations, certainly not commercial salmon farming, or fresh water salmon fishing. And it gets even more convoluted when Congress, in the 2008 Farm Bill, mandated that catfish inspection move from FDA to FSIS, but left all other fish and seafood at FDA.</div><div><br /></div><div>The Food Safety New story also said that "Obama administration officials are said to favor the merger because it would make food safety independent of USDA, which primarily exists to market and promote American farm products."</div><div><br /></div><div>There are seven Mission Areas within the USDA. The five Undersecretaries for Food Safety; Food Nutrition and Consumer Services; Rural Development; Natural Resources and Environment; &nbsp;and Research, Education and Economic will tell you they do not "primarily exist to market and promote American farm products."</div><div><br /></div><div>One might argue, based on prior observations, that the Food and Drug Administration primarily exists to regulate medicines and medical devices.</div><div><br /></div><div>Single Food Safety Agency. Sounds good, but guess what? We had a single food safety agency from 1906, when the Federal Meat Inspection Act and the Pure Food and Drug Acts were passed. USDA had all the authority for food safety.&nbsp;</div><div><br /></div><div>The FDA was transferred out of the USDA in 1940. A single food safety agency must not have been perceived to be working out too well back then.</div><div>&nbsp;</div><div>Some would say mega-bureaucracies lose the nimbleness necessary to respond to outbreaks and other emergencies. Agencies like the Department of Homeland Security come to mind.</div><div><br /></div><div>Maybe the scariest thing about this whole idea of a single food safety agency, located at FDA is that Carol Tucker-Foreman and I agree that it is a bad idea. We don't agree on too much, so when we do, it must be a really good idea (non-O157 STECs as adulterants in beef, for example) or a really bad idea (single food safety agency at FDA).</div></div><div>,</div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/single-food-agency-a-recipe-for-singular-disaster/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/single-food-agency-a-recipe-for-singular-disaster/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Mon, 16 Jan 2012 01:59:03 -0800</pubDate>
         <author>rainman2x11@gmail.com (Dr. Richard Raymond)</author>
      
      </item>
      
      <item>
         <title>Letter From The Editor: PSAs</title>
         <description><![CDATA[<div>One out of six Americans will get sick this year from foodborne illnesses, says a new television commercial.</div><div><br /></div><div>And 3,000 will die, according to a radio spot.</div><div><br /></div><div>Many in the food-safety community know these facts, but lots of people do not.</div><div><br /></div><div>Who is spreading this news?</div><div><br /></div><img alt="adcouncilcampaign-350.jpg" src="http://www.foodsafetynews.com/adcouncilcampaign-350.jpg" width="241" height="240" class="mt-image-right" style="float: right; margin: 0 0 20px 20px;" /><div>None other than the <a href="http://www.fsis.usda.gov/education/Check_Your_Steps/index.asp">Food Safe Families campaign</a>, a project of the Ad Council and USDA's Food Safety and Inspection Service, the Centers for Disease Control and Prevention, and the U.S. Food and Drug Administration.</div><div><br /></div><div>The campaign, which began last year, received complete coverage June 29 in a <a href="http://www.foodsafetynews.com/2011/06/govnt-rolls-out-new-food-safety-ads/">Food Safety News story by Gretchen Goetz.</a></div><div><br /></div><div>Federal food safety agencies have long used public service announcements, but most have been childish and, for sure, not anything that would give the food industry any stomach aches. In the past, those PSAs avoided the simple truth that food poisoning is about illness and death.&nbsp;</div><div><br /></div><div>An example of those can be found on<a href="http://www.youtube.com/watch?v=RFuqQ8_h6Oc"> FSIS's area of YouTube.</a>&nbsp;Called "The Cooking Challenge," it had a team of girls lose to a team of boys in properly preparing some kind of frozen food. &nbsp;"We failed," say the girls, who did not read the food industry's instructions on the package. Thankfully, there were no spankings.</div><div><br /></div><div>The Food Safe Family spots are much smarter and more direct. They don't just say that something "icky" might happen. &nbsp;They say people are going to get sick and die, so listen up about avoiding cross contamination or keeping kitchen surfaces clean.</div><div><br /></div><div>Why is this new campaign so much better?</div><div><br /></div><div>Some might think the Food Safe Families campaign is more honest because the private nonprofit Ad Council gets private sector talent involved and - presto - a better product emerges. &nbsp;&nbsp;</div><div><br /></div><div>That may be true, but this is probably not the first time the Ad Council has been brought in to do a food safety campaign. My bet is that somewhere in here is someone with some political backbone. This an effort that deserves to be rewarded, and I am going to tell you how to do it.</div><div><br /></div><div>It as simple as this. If you like these PSAs, why not help us get more of them aired?</div><div><br /></div><div>Public service announcements run in time slots donated by commercial TV and radio stations. Generally speaking, station managers or the minions they've assigned to PSAs give preference to local organizations. But after that - and this is the secret - most stations run national PSAs that are either trendy or that they've been asked to run by their listening audience.</div><div><br /></div><div>If all of you who care about getting this kind of a food safety message out would just send your commercial stations an email telling them <a href="http://www.adcouncil.org/Our-Work/Current-Work/Health/Food-Safety-Education#Asset687">where they can find</a> these spots and encouraging them to give them some time slots, the PSAs will get airtime. (The station can go to "Get Ads" for the spots in the chosen format. They are free to the radio and tv stations.) Just be nice when you ask!</div><div><br /></div><div>Helping get them some airtime is a great way to thank those who showed some spine by equating foodborne illness with sickness and death. Outside your community's Children's Hospital, you'd be surprised at how many people do not know that 128,000 people will be hospitalized and 3,000 people will die in 2012 from what they eat.</div><div><br /></div><div><br /></div> ]]></description>
         <link>http://www.foodsafetynews.com/contributors.xml?FB_go=1&amp;FB_url=http://www.foodsafetynews.com/2012/01/letter-from-the-editor-psas/</link>
         <guid isPermaLink="false">http://www.foodsafetynews.com/2012/01/letter-from-the-editor-psas/</guid>
         <category domain="http://www.foodsafetynews.com/sections">Opinion &amp; Contributed Articles</category>
         <pubDate>Sun, 15 Jan 2012 01:59:03 -0800</pubDate>
         <author>dflynn@foodsafetynews.com (Dan Flynn)</author>
      
      </item>
      
   </channel>
</rss>

