E. coli O157:H7 Outbreak In Canada – Again!

The Canadian Food Inspection Agency is warning the public not to consume certain frozen beef burgers, due to a risk of E. coli O157:H7 contamination after finding E. coli O157:H7 in products tested as part of an “ongoing outbreak investigation.” The Public Health Agency of Canada has not yet released any information about this new outbreak.

Canada Safeway Limited has recalled the following products, which were distributed in Ontario, Manitoba, Saskatchewan, Alberta, British Columbia and Northwest Territories:

  • The Gourmet Meat Shoppe Big & Juicy Burger (1.13 kg: UPC 0 58200 10650 3; Best before 2013 AU 14 EST 752)
  • The Gourmet Meat Shoppe Prime Rib Burger (907g; UPC 0 58200 10733 3; Best before 2013 AU 14 EST 752)
  • The Butcher’s Cut Pure Beef Patties, 10 Patties (1.13 kg; UPC 0 58200 21604 2; Best before 2013 AU 14 EST 752)
  • The Butcher’s Cut Pure Beef Patties, 20 Patties (2.27 kg; UPC 0 58200 21592 2; Best before 2013 AU 14 EST 752)
  • The Butcher’s Cut Pure Beef Patties, 40 Patties (4.45 kg; UPC 0 58200 21594 6; Best before 2013 AU 14 EST 752)

All of the above-listed products originated from Cardinal Meat Specialists Limited (Establishment 752. 155 Hedgedale Road, Brampton, Ontario). This is the same establishment that was linked to a 5-case outbreak of E. coli O157:H7 in December 2012. The same establishment that was investigated ‘extensively’ – and fruitlessly – by CFIA in December 2012.

The detailed report promised in its final investigation update, posted on December 24th, has not yet been released to the public. Perhaps it’s just as well; that ‘final’ report would have been premature.

At this stage of the investigation, all we have are questions:

  1. How large is this outbreak? How many patients? Which provinces?
  2. Is this the same genetic strain of E. coli O157:H7 that was responsible for the December 2012 outbreak?
  3. Has production been suspended at the Cardinal Meat facility? If not, why not?
  4. What does CFIA plan to do this time to improve on its December 2012 performance?

This is the third meat-related E. coli O157:H7 outbreak in Canada in less than one year. What is the federal government doing to prevent E. coli O157:H7 from spiraling out of control in Canadian beef?

Guest Blog: Salmonella’s Not an Adulterant?

The following Guest Blog first appeared on Food Safety News (February 2, 2013), and is reproduced here with the kind permission of its author, Bill Marler.

Salmonella’s Not an Adulterant?

– by William D. Marler

Personally, as I said to the Los Angeles Times several months ago, “I think that anything that can poison or kill a person should be listed as an adulterant [in food].”

Ignoring Salmonella in meat makes little, if any, sense. Even after the Court’s twisted opinion in Supreme Beef v. USDA, where it found Salmonella “not an adulterant per se, meaning its presence does not require the USDA to refuse to stamp such meat ‘inspected and passed,” our government’s failure to confront the reality of Salmonella, especially antibiotic-resistant Salmonella, is inexcusable. The Wisconsin Supreme Court in Kriefall v Excel called it as it saw it:

The E. coli strain that killed Brianna and made the others sick is a “deleterious substance which may render [meat] injurious to health.” There is no dispute about this. Thus, under the first part of 21 U.S.C. § 601(m)(1), meat that either “bears or contains” E. coli O157:H7 (the “deleterious substance”) is “adulterated.” That E. coli O157:H7 contamination can be rendered non-“injurious to health” by cooking thoroughly, as discussed below, does not negate this; Congress used the phrase “may render,” not “in every circumstance renders.” Moreover, if the E. coli bacteria is not considered to be “an added substance,” because it comes from some of the animals themselves and is not either applied or supplied during the slaughtering process (although we do not decide this), it cannot be said that the E. coli strain “does not ordinarily render [the meat on or in which it appears] injurious to health.” Accordingly, meat contaminated by E. coli O157:H7 is also “adulterated” under the second part of § 601(m)(1).

Now, why would Salmonella be different?

According to the CDC, it is estimated that 1.4 million cases of salmonellosis occur each year in the U.S. Of those cases, 95 percent are related to foodborne causes. Approximately 220 of each 1000 cases result in hospitalization, and 8 of every 1000 cases result in death. About 500 to 1,000 deaths – 31 percent of all food-related deaths – are caused by Salmonella infections each year.

So, where do we stand with the existing USDA/FSIS law on adulteration? Here is the law:

21 U.S.C. § 601(m)(4) – SUBCHAPTER I – INSPECTION REQUIREMENTS; ADULTERATION AND MISBRANDING – CHAPTER 12 – MEAT INSPECTION – TITLE 21—FOOD AND DRUGS

(m) The term “adulterated” shall apply to any carcass, part thereof, meat or meat food product under one or more of the following circumstances:

(1) if it bears or contains any poisonous or deleterious substance which may render it injurious to health; but in case the substance is not an added substance, such article shall not be considered adulterated under this clause if the quantity of such substance in or on such article does not ordinarily render it injurious to health; …

(3) if it consists in whole or in part of any filthy, putrid, or decomposed substance or is for any other reason unsound, unhealthful, unwholesome, or otherwise unfit for human food;

(4) if it has been prepared, packed, or held under insanitary conditions whereby it may have become contaminated with filth, or whereby it may have been rendered injurious to health; …

Hmmm. It is hard to read the above and not think that the words in bold equate to all E. coli and Salmonella (frankly, all pathogens in food). I know, I am just a lawyer, but don’t ya think that when food with animal feces (and a dash of E. coli O157:H7) in it is considered an adulterant, that other animal feces (with dashes of other pathogens, like Salmonella) in them, should be considered adulterated too? But, hey, that is just me.

Another odd governmental fact is that the FDA does not seem to make a distinction between pathogens it considers adulterants or not. FDA’s enabling legislation – Sec. 402. [21 USC §342] of the Food, Drug & Cosmetic Act also defines “Adulterated Food” as food that is:

(a) Poisonous, insanitary, or deleterious ingredients.

(1) If it bears or contains any poisonous or deleterious substance which may render it injurious to health; but in case the substance is not an added substance such food shall not be considered adulterated under this clause if the quantity of such substance in such food does not ordinarily render it injurious to health;

(2) If it bears or contains any added poisonous or added deleterious substance … that is unsafe within the meaning of section 406;

(3) if it consists in whole or in part of any filthy, putrid, or decomposed substance, or if it is otherwise unfit for food;

(4) if it has been prepared, packed, or held under insanitary conditions whereby it may have become contaminated with filth, or whereby it may have been rendered injurious to health …

It would be interesting, and perhaps entertaining, to have House and Senate hearings focusing on what should and should not be considered adulterants in our food. I can see panels of scientists from various fields, FDA, USDA and FSIS officials, beef and produce industry representatives and consumers discussing this. I would pay to watch it.

About the author: Bill Marler is a personal injury and products liability attorney, and an internationally known food safety advocate. He began litigating foodborne illness cases in 1993, when he represented Brianne Kiner, the most seriously injured survivor of the Jack in the Box E. coli O157:H7 outbreak. Bill is a graduate of the Seattle University School of Law, and the Law School’s “Lawyer in Residence.”

Guest Blog: Does The “No Illnesses” Language Belong in Recall Notices?

The following Guest Blog first appeared on Food Safety News, and is reproduced here with the kind permission of its author, Dan Flynn.

Does The “No Illnesses” Language Belong in Recall Notices?

by Dan Flynn

Food companies that are voluntarily recalling a product usually use the language suggested by regulatory agencies that is then distributed electronically via the federal government websites. Recalls not connected to outbreaks almost always contain a line saying there are no reported illnesses associated with the recalled product.

William F. Keene, Oregon’s senior state epidemiologist, thinks it’s time for reporters and editors to “not let themselves be duped into amplifying press release boilerplate.”

Both the U.S. Food and Drug Administration (FDA) and USDA’s Food Safety and Inspection Service (FSIS) have templates for companies to use when writing a recall announcement. They are:

FDA: ”No illnesses have been reported to date.”

FSIS: “There have been no reports of illnesses associated with consumption of these products.”

“Until they have the isolate(s) serotyped, have PFGE’d (conducted a pulsed-field gel electrophoresis analysis), and compared to PulseNet or analogous data,” says Keene, “they are just blowing smoke.” He says that without subtyping data, the media should not fall for it. The only accurate report is that there is no way of knowing (at this time) if there are any associated illnesses.

Dr. David Acheson, who previously held top posts at both FSIS and FDA before becoming a partner at Leavitt Partners, says Keene “is correct, but nobody other than a microbiologist would know that the heck that means and the basic statement from the regulators is still correct.”

Acheson says the point of recall announcements is to answer the public’s “what should I do” questions, and he prefers keeping it “simple and specific.” Acheson says he might add the word “yet” to statements about no illnesses being reported.

Phyllis Entis, the food safety microbiologist and author, who publishes the highly respected eFoodAlert, covering food recalls worldwide, goes a step further than Keene.

“I think that an absence of a ‘no illnesses’ statement would be preferable to the current boilerplate,” she says. “I agree that we should be asking the question, and I have queried CDC in some cases. At times, I even get an answer!”

And Entis notes that boilerplate is used worldwide. The XL Foods recall, the largest beef recall in Canada’s history, originally came out with this line from the template: “There have been on reported illnesses associated with the consumption of these products.”

A short time later the Public Health Agency of Canada (PHAC) was confirming 18 cases of E coli O157:H7 from XL’s contaminated beef.

Keene, who has solved many a multistate outbreak, admits he is motivated by a desire to “light a fire” under food companies to get them to turn over isolates to public health labs so they can be subtyped. Only then can the food isolates be matched to any human cases that might exist.

“As you can imagine, Keene says, “this is not a prospect that excites many food processors, as it literally asking for trouble. I think making it clear that we don’t know if there might be illnesses will prompt people to ask more of the right questions.”

Keene notes that often-ill people who are matched to contaminated food are never asked (or told) if they ate it. He says the system is complicated, with the left hand often not knowing what the right hand is doing.

Carol L. Tucker-Foreman, distinguished food policy fellow at the Consumer Federation of America and USDA’s former Assistant Secretary for Food and Consumer Services, says where there is a recall, there is risk.

“The current FSIS language suggests that there are no reported illnesses as yet and therefore no risk to public health,” she says. “But if that were the case there would be no recall. The recall means the company and FSIS know some meat from the recalled lot is available to the public. That means there is some continuing risk and the agency should say so.”

With her experience in and out of the federal government, Tucker-Foreman says both FDA and FSIS “are eager not to alarm the public unnecessarily or create to much of a problem for the company where there’s no reported illnesses.”

She says food companies “particularly hate the fact that a press release and recall occur based only on plant testing, However, there is no recall unless FSIS believes some contaminated product left the plant and has not yet been recover.”

For his part, Keene is the first to acknowledge that most recalls are not associated with illnesses. However, he says, that is only partially true because nobody is asking. If isolates were turned over to public health labs and searches for matches conducted, then we’d know more about whether or not there were illnesses.

Keene says even then if the test produced a common pattern and there was no spiking of the pattern, its unlikely CDC would bother getting back to “state epi people” and the matches might not be contemporaneous enough to make it worthwhile to health officials to get back in touch with the ill people.

Keene was last in the national news in September 2011 when Del Monte Fresh Produce dropped a lawsuit against the epidemiologist that some said sought to put the science of epidemiology on trial. Del Monte was upset because some of its Central American grown cantaloupe were subjected to an import alert.

© Food Safety News

About the author: Dan Flynn is a Denver-based writer and editor with more than ten years of food safety experience. As a public affairs professional, he worked with government and regulatory agencies at the local, state, and federal levels. At present, he is Editor of Food Safety News.