Texas man ‘skinned like a deer’ by Vibrio that killed him slowly over two weeks after fishing trip

Mia De Graaf of the Daily Mail writes a 78-year-old Texas man died after an agonizing two-week battling against flesh-eating bacteria he contracted on a fishing trip last month.

Jerry Sebek, of San Marcos, did not get in the water, did not have any open wounds, and did not have any health issues that would weaken his immune system.

And yet, hours after returning from Turtle Bay on June 13, he became delirious, vomiting, and struggling to breathe.

His daughter Kim took him to a clinic, where doctors said it looked like heat stroke.

But the next morning, he was taken to hospital, where he tested positive for vibrio, an aggressive type of bacteria that eats away at muscle and tissue.

His right arm, where the infection started, was ‘skinned like a deer,’ Kim told SanAntonio.com.

Despite amputating his arm and leg, and putting him in a medically-induced coma, doctors could not defeat the infection.

‘I’m still a little shocked and in disbelief,’ Kim told the site. 

‘Dad was a wonderful family man who loved to hunt and fish and do things out in the water.’

She added: ‘We’ve been coming here [to Turtle Bay] for years and this is just an unfortunate thing that happened.’

North American Cyclospora outbreaks

My aunt got sick from Cyclospora in some basil-based thingy in Florida, in 2005.

She was sick for weeks.

On June 12, 1996, Ontario’s chief medical officer, Dr. Richard Schabas, issued a public health advisory on the presumed link between consumption of California strawberries and an outbreak of diarrheal illness among some 40 people in the Metro Toronto area. The announcement followed a similar statement from the Department of Health and Human Services in Houston, Texas, who were investigating a cluster of 18 cases of Cyclospora illness among oil executives.

Dr. Schabas advised consumers to wash California berries “very carefully” before eating them, and recommended that people with compromised immune systems avoid them entirely. He also stated that Ontario strawberries, which were just beginning to be harvested, were safe for consumption. Almost immediately, people in Ontario stopped buying strawberries. Two supermarket chains took California berries off their shelves, in response to pressure from consumers. The market collapsed so thoroughly that newspapers reported truck drivers headed for Toronto with loads of berries being directed, by telephone, to other markets.

However, by June 20, 1996, discrepancies began to appear in the link between California strawberries and illness caused by the parasite, Cyclospora, even though the number of reported illnesses continued to increase across North America. Texas health officials strengthened their assertion that California strawberries were the cause of the outbreak, while scientists at the U.S. Centers for Disease Control and Prevention (CDC) and the Food and Drug Administration (FDA) said there were not yet ready to identify a food vehicle for the outbreak. On June 27, 1996, the New York City Health Department became the first in North America to publicly state that raspberries were also suspected in the outbreak of Cyclospora.

By July 18, 1996, the CDC declared that raspberries from Guatemala — which had been sprayed with pesticides mixed with water that could have been contaminated with human sewage containing Cyclospora — were the likely source of the Cyclospora outbreak, which ultimately sickened about 1,000 people across North America. Guatemalan health authorities and producers have vigorously refuted the charges. The California Strawberry Commission estimates it lost $15 million to $20 million in reduced strawberry sales.

Cyclospora cayetanensis is a recently characterised coccidian parasite; the first known cases of infection in humans were diagnosed in 1977. Before 1996, only three outbreaks of Cyclospora infection had been reported in the United States. Cyclospora is normally associated with warm, Latin American countries with poor sanitation.

One reason for the large amount of uncertainty in the 1996 Cyclospora outbreak is the lack of effective testing procedures for this organism. To date, Cyclospora oocysts have not been found on any strawberries, raspberries or other fruit, either from North America or Guatemala. That does not mean that cyclospora was absent; it means the tests are unreliable and somewhat meaningless. FDA, CDC and others are developing standardized methods for such testing and are currently evaluating their sensitivity.

The initial, and subsequent, links between Cyclospora and strawberries or raspberries were therefore based on epidemiology, a statistical association between consumption of a particular food and the onset of disease. For example, the Toronto outbreak was first identified because some 35 guests attending a May 11, 1996 wedding reception developed the same severe, intestinal illness, seven to 10 days after the wedding, and subsequently tested positive for cyclospora. Based on interviews with those stricken, health authorities in Toronto and Texas concluded that California strawberries were the most likely source. However, attempts to remember exactly what one ate two weeks earlier is an extremely difficult task; and larger foods, like strawberries, are recalled more frequently than smaller foods, like raspberries. Ontario strawberries were never implicated in the outbreak.

Once epidemiology identifies a probable link, health officials have to decide whether it makes sense to warn the public. In retrospect, the decision seems straightforward, but there are several possibilities that must be weighed at the time. If the Ontario Ministry of Health decided to warn people that eating imported strawberries might be connected to Cyclospora infection, two outcomes were possible: if it turned out that strawberries are implicated, the ministry has made a smart decision, warning people against something that could hurt them; if strawberries were not implicated, then the ministry has made a bad decision with the result that strawberry growers and sellers will lose money and people will stop eating something that is good for them. If the ministry decides not to warn people, another two outcomes are possible: if strawberries were implicated, then the ministry has made a bad decision and people may get a parasitic infection they would have avoided had they been given the information (lawsuits usually follow); if strawberries were definitely not implicated then nothing happens, the industry does not suffer and the ministry does not get in trouble for not telling people. Research is currently being undertaken to develop more rigorous, scientifically-tested guidelines for informing the public of uncertain risks.

But in Sarnia (Ontario, Canada) they got a lot of sick people who attended the Big Sisters of Sarnia-Lambton Chef’s Challenge on May 12, 2010.

Michael T. Osterholm, PhD, who has a lot of titles and once called me at 5 a.m. to tell me I was an asshole (maybe not the exact words, but the sentiment) and chair of the Holstein Blue-Ribbon Panel on the Prevention of Foodborne Cyclospora Outbreaks writes that the 1996 cyclosporiasis outbreak in the United States and Canada associated with the late spring harvest of imported Guatemalan-produced raspberries was an early warning to public health officials and the produce industry that the international sourcing of produce means that infectious agents once thought of as only causing traveler’s diarrhea could now infect at home. The public health investigation of the 1996 outbreak couldn’t identify how, when, where, or why the berries became contaminated with Cyclospora cayetanensis.

The investigation results were published in the New England Journal of Medicine in 1997. I was asked to write an editorial to accompany the investigation report.2 In my editorial, I noted the unknowns surrounding the C. cayetanensis contamination. The 1997 spring harvest of Guatemalan raspberries was allowed to be imported into both the United States and Canada—and again, a large outbreak of cyclosporiasis occurred. As in the 1996 outbreak, no source for the contamination of berries was found. Later in 1997, the Food and Drug Administration (FDA) prohibited the importation of future spring harvests of Guatemalan raspberries until a cause for the contamination could be demonstrated and corrective actions taken. While the FDA did not permit the 1998 importation of the raspberries into the United States, the berries continued to be available in Canada. Outbreaks linked to raspberries occurred in Ontario in May 1998. When the U.S. Centers for Disease Control and Prevention (CDC)-led investigative team published its 1997 outbreak findings in the Annals of Internal Medicine, 3 I was again asked to write an accompanying editorial.4 As I had done in my previous editorial, I highlighted how little we know about the factors associated with the transmission Cyclospora on produce and how to prevent it.

Unfortunately, the state of the art for preventing foodborne, produce-associated cyclosporiasis had changed little since the 1996 outbreak despite the relatively frequent occurrence of such outbreaks.

Thirty-four years after that first Guatemalan raspberry-associated outbreak — and a year after produce-associated cyclosporiasis outbreaks that were linked to U.S.-grown produce — there has been a major leap in prevention, yet the outbreaks still happen.

 Foodborne outbreaks of cyclosporiasis have been reported in the United States since the mid-1990s and have been linked to various types of imported fresh produce, including raspberries, basil, snow peas, mesclun lettuce, and cilantro; no commercially frozen produce has been implicated to date. U.S. foodborne outbreaks of cyclosporiasis that occurred before 2000 were summarized previously, as were the major documented outbreaks in 2013 and 2014. Foodborne outbreaks during the 18-year period of 2000–2017 are summarized here.

The table provides information about 39 reported foodborne outbreaks of cyclosporiasis that occurred in the United States during 2000–2017; the total case count was 1,730. No outbreaks were reported in 2003, 2007, or 2010. Overall, a median of two outbreaks were reported per year, with a median of 19 cases per outbreak (range, 3 to 582 cases). Although the outbreaks occurred during 8 different months (December through July), the peak months were May, June, and July. As indicated in the table, a food vehicle of infection was identified (or suspected) for 17 of the 39 outbreaks.

Identifying the particular food item/ingredient that caused an outbreak of cyclosporiasis can be very challenging—for example, if fresh produce was served as a garnish or topping or if several types of produce were mixed together. CDC and other agencies are working to develop and validate molecular typing methods that could distinguish among different strains of the parasite Cyclospora cayetanensis that causes cyclosporiasis. In the future, such tools could help link cases of cyclosporiasis to each other and to particular types of produce, which could help public health officials investigate and prevent cases and outbreaks of Cyclospora infection.

Table: Summary of U.S. foodborne outbreaks of cyclosporiasis, 2000–2017
Year(s)* Month(s)* Jurisdiction(s)* No. of cases† Food vehicle and source, if identified‡
2000 May Georgia 19 Raspberries and/or blackberries (suspected)
2000 June Pennsylvania 54 Raspberries
2001 January–February Florida 39
2001 January New York City 3
2001–02 December–January Vermont 22 Raspberries (likely)
2002 April–May Massachusetts 8
2002 June New York 14
2004 February Texas 38
2004 February Illinois 57 Basil (likely)
2004 May Tennessee 12
2004 May–June Pennsylvania 96 Snow peas from Guatemala ⁂
2005 March–May Florida 582 ¶ Basil from Peru
2005 May South Carolina 6
2005 April Massachusetts 58
2005 May Massachusetts 16
2005 June Connecticut 30 Basil (suspected)
2006 June Minnesota 14
2006 June New York 20
2006 July Georgia 3
2008 March Wisconsin 4 Sugar snap peas (likely) ⁂
2008 July California 45 ¶ Raspberries and/or blackberries (likely)
2009 June District of Columbia 34
2011 June Florida 12
2011 July Georgia 88**
2012 June–July Texas 16
2013†† June Iowa, Nebraska, and neighboring states 162 Bagged salad mix from Mexico
2013†† June–July Texas 38 Cilantro from Mexico
2013 July Wisconsin 8 Berry salad (suspected)
2014 June Michigan 14
2014‡‡ June–July Texas 26 Cilantro from Mexico
2014 July South Carolina 13
2015 May–July Georgia, Texas, and Wisconsin 90 Cilantro from Mexico
2016 June–July Texas 6¶¶ Carrots or green cabbage (suspected)
2017 May Florida 6 Berries (suspected)
2017 May–July Texas 38*** Scallions (i.e., green onions)
2017 June Michigan 29
2017 June Tennessee 4†††
2017 June Connecticut 3
2017 July Florida 3‡‡‡

* The entries in the first three columns refer to the known or likely year(s), month(s), and jurisdiction(s) in which the exposure(s) to Cyclospora occurred.

† The case counts include laboratory-confirmed and probable cases of cyclosporiasis. By definition, each outbreak included at least two linked cases, at least one of which was laboratory confirmed.

‡ A food vehicle is specified only if a single ingredient or commodity was identified in an outbreak investigation.

¶ Cases that occurred in Canadian travelers to the United States were not included.

** An additional 10 probable cases were associated with this outbreak but were not counted in the table: nine of these cases were in residents of states in which cyclosporiasis was not a reportable condition, and the other case was in a patient whose state of residence was unknown.

†† For additional details, see summary information about the outbreak investigations in 2013. For the purposes of this table, the exposure month(s) and case counts are limited to those explicitly linked in the investigations to the food item specified in the last column.

‡‡ For additional perspective, see summary information about outbreak investigations in 2014. For the purposes of this table, the exposure months and the case count for the outbreak in Texas are limited to those explicitly linked in the investigations to the food item specified in the last column.

¶¶ An additional nine suspected cases were identified in persons associated with this outbreak but were not counted in the table because of reporting issues (e.g., insufficient case data).

*** An additional three probable cases were identified in persons associated with this outbreak but were not counted in the table because of reporting issues (e.g., insufficient case data).

††† An additional two probable cases were identified in persons associated with this outbreak but were not counted in the table because of reporting issues (e.g., insufficient case data).

‡‡‡ One additional probable case was identified in a person associated with this outbreak but was not counted in the table because of a reporting issue.

⁂ More information to help distinguish among types of peas can be found herepdf icon.

Table: Summary of U.S. foodborne outbreaks of cyclosporiasis, 2000–2017
Year(s)* Month(s)* Jurisdiction(s)* No. of cases† Food vehicle and source, if identified‡
2000 May Georgia 19 Raspberries and/or blackberries (suspected)
2000 June Pennsylvania 54 Raspberries
2001 January–February Florida 39
2001 January New York City 3
2001–02 December–January Vermont 22 Raspberries (likely)
2002 April–May Massachusetts 8
2002 June New York 14
2004 February Texas 38
2004 February Illinois 57 Basil (likely)
2004 May Tennessee 12
2004 May–June Pennsylvania 96 Snow peas from Guatemala ⁂
2005 March–May Florida 582 ¶ Basil from Peru
2005 May South Carolina 6
2005 April Massachusetts 58
2005 May Massachusetts 16
2005 June Connecticut 30 Basil (suspected)
2006 June Minnesota 14
2006 June New York 20
2006 July Georgia 3
2008 March Wisconsin 4 Sugar snap peas (likely) ⁂
2008 July California 45 ¶ Raspberries and/or blackberries (likely)
2009 June District of Columbia 34
2011 June Florida 12
2011 July Georgia 88**
2012 June–July Texas 16
2013†† June Iowa, Nebraska, and neighboring states 162 Bagged salad mix from Mexico
2013†† June–July Texas 38 Cilantro from Mexico
2013 July Wisconsin 8 Berry salad (suspected)
2014 June Michigan 14
2014‡‡ June–July Texas 26 Cilantro from Mexico
2014 July South Carolina 13
2015 May–July Georgia, Texas, and Wisconsin 90 Cilantro from Mexico
2016 June–July Texas 6¶¶ Carrots or green cabbage (suspected)
2017 May Florida 6 Berries (suspected)
2017 May–July Texas 38*** Scallions (i.e., green onions)
2017 June Michigan 29
2017 June Tennessee 4†††
2017 June Connecticut 3
2017 July Florida 3‡‡‡

By July 18, 1996, the CDC declared that raspberries from Guatemala — which had been sprayed with pesticides mixed with water that could have been contaminated with human sewage containing Cyclospora — were the likely source of the Cyclospora outbreak, which ultimately sickened about 1,000 people across North America. Guatemalan health authorities and producers have vigorously refuted the charges. The California Strawberry Commission estimates it lost $15 million to $20 million in reduced strawberry sales.

Cyclospora cayetanensis is a recently characterised coccidian parasite; the first known cases of infection in humans were diagnosed in 1977. Before 1996, only three outbreaks of Cyclospora infection had been reported in the United States. Cyclospora is normally associated with warm, Latin American countries with poor sanitation.

One reason for the large amount of uncertainty in the 1996 Cyclospora outbreak is the lack of effective testing procedures for this organism. To date, Cyclospora oocysts have not been found on any strawberries, raspberries or other fruit, either from North America or Guatemala. That does not mean that cyclospora was absent; it means the tests are unreliable and somewhat meaningless. FDA, CDC and others are developing standardized methods for such testing and are currently evaluating their sensitivity.

The initial, and subsequent, links between Cyclospora and strawberries or raspberries were therefore based on epidemiology, a statistical association between consumption of a particular food and the onset of disease. For example, the Toronto outbreak was first identified because some 35 guests attending a May 11, 1996 wedding reception developed the same severe, intestinal illness, seven to 10 days after the wedding, and subsequently tested positive for cyclospora. Based on interviews with those stricken, health authorities in Toronto and Texas concluded that California strawberries were the most likely source. However, attempts to remember exactly what one ate two weeks earlier is an extremely difficult task; and larger foods, like strawberries, are recalled more frequently than smaller foods, like raspberries. Ontario strawberries were never implicated in the outbreak.

Once epidemiology identifies a probable link, health officials have to decide whether it makes sense to warn the public. In retrospect, the decision seems straightforward, but there are several possibilities that must be weighed at the time. If the Ontario Ministry of Health decided to warn people that eating imported strawberries might be connected to Cyclospora infection, two outcomes were possible: if it turned out that strawberries are implicated, the ministry has made a smart decision, warning people against something that could hurt them; if strawberries were not implicated, then the ministry has made a bad decision with the result that strawberry growers and sellers will lose money and people will stop eating something that is good for them. If the ministry decides not to warn people, another two outcomes are possible: if strawberries were implicated, then the ministry has made a bad decision and people may get a parasitic infection they would have avoided had they been given the information (lawsuits usually follow); if strawberries were definitely not implicated then nothing happens, the industry does not suffer and the ministry does not get in trouble for not telling people. Research is currently being undertaken to develop more rigorous, scientifically-tested guidelines for informing the public of uncertain risks.

But in Sarnia (Ontario, Canada) they got a lot of sick people who attended the Big Sisters of Sarnia-Lambton Chef’s Challenge on May 12, 2010.

Michael T. Osterholm, PhD, who has a lot of titles and once called me at 5 a.m. to tell me I was an asshole (maybe not the exact words, but the sentiment) and chair of the Holstein Blue-Ribbon Panel on the Prevention of Foodborne Cyclospora Outbreaks writes that the 1996 cyclosporiasis outbreak in the United States and Canada associated with the late spring harvest of imported Guatemalan-produced raspberries was an early warning to public health officials and the produce industry that the international sourcing of produce means that infectious agents once thought of as only causing traveler’s diarrhea could now infect at home. The public health investigation of the 1996 outbreak couldn’t identify how, when, where, or why the berries became contaminated with Cyclospora cayetanensis.

The investigation results were published in the New England Journal of Medicine in 1997. I was asked to write an editorial to accompany the investigation report.2 In my editorial, I noted the unknowns surrounding the C. cayetanensis contamination. The 1997 spring harvest of Guatemalan raspberries was allowed to be imported into both the United States and Canada—and again, a large outbreak of cyclosporiasis occurred. As in the 1996 outbreak, no source for the contamination of berries was found. Later in 1997, the Food and Drug Administration (FDA) prohibited the importation of future spring harvests of Guatemalan raspberries until a cause for the contamination could be demonstrated and corrective actions taken. While the FDA did not permit the 1998 importation of the raspberries into the United States, the berries continued to be available in Canada. Outbreaks linked to raspberries occurred in Ontario in May 1998. When the U.S. Centers for Disease Control and Prevention (CDC)-led investigative team published its 1997 outbreak findings in the Annals of Internal Medicine, 3 I was again asked to write an accompanying editorial.4 As I had done in my previous editorial, I highlighted how little we know about the factors associated with the transmission Cyclospora on produce and how to prevent it.

Unfortunately, the state of the art for preventing foodborne, produce-associated cyclosporiasis had changed little since the 1996 outbreak despite the relatively frequent occurrence of such outbreaks.

Thirty-four years after that first Guatemalan raspberry-associated outbreak — and a year after produce-associated cyclosporiasis outbreaks that were linked to U.S.-grown produce — there has been a major leap in prevention, yet the outbreaks still happen.

Foodborne outbreaks of cyclosporiasis have been reported in the United States since the mid-1990s and have been linked to various types of imported fresh produce, including raspberries, basil, snow peas, mesclun lettuce, and cilantro; no commercially frozen produce has been implicated to date. U.S. foodborne outbreaks of cyclosporiasis that occurred before 2000 were summarized previously, as were the major documented outbreaks in 2013 and 2014. Foodborne outbreaks during the 18-year period of 2000–2017 are summarized here.

The table provides information about 39 reported foodborne outbreaks of cyclosporiasis that occurred in the United States during 2000–2017; the total case count was 1,730. No outbreaks were reported in 2003, 2007, or 2010. Overall, a median of two outbreaks were reported per year, with a median of 19 cases per outbreak (range, 3 to 582 cases). Although the outbreaks occurred during 8 different months (December through July), the peak months were May, June, and July. As indicated in the table, a food vehicle of infection was identified (or suspected) for 17 of the 39 outbreaks.

Identifying the particular food item/ingredient that caused an outbreak of cyclosporiasis can be very challenging—for example, if fresh produce was served as a garnish or topping or if several types of produce were mixed together. CDC and other agencies are working to develop and validate molecular typing methods that could distinguish among different strains of the parasite Cyclospora cayetanensis that causes cyclosporiasis. In the future, such tools could help link cases of cyclosporiasis to each other and to particular types of produce, which could help public health officials investigate and prevent cases and outbreaks of Cyclospora infection.

Table: Summary of U.S. foodborne outbreaks of cyclosporiasis, 2000–2017
Year(s)* Month(s)* Jurisdiction(s)* No. of cases† Food vehicle and source, if identified‡
2000 May Georgia 19 Raspberries and/or blackberries (suspected)
2000 June Pennsylvania 54 Raspberries
2001 January–February Florida 39
2001 January New York City 3
2001–02 December–January Vermont 22 Raspberries (likely)
2002 April–May Massachusetts 8
2002 June New York 14
2004 February Texas 38
2004 February Illinois 57 Basil (likely)
2004 May Tennessee 12
2004 May–June Pennsylvania 96 Snow peas from Guatemala ⁂
2005 March–May Florida 582 ¶ Basil from Peru
2005 May South Carolina 6
2005 April Massachusetts 58
2005 May Massachusetts 16
2005 June Connecticut 30 Basil (suspected)
2006 June Minnesota 14
2006 June New York 20
2006 July Georgia 3
2008 March Wisconsin 4 Sugar snap peas (likely) ⁂
2008 July California 45 ¶ Raspberries and/or blackberries (likely)
2009 June District of Columbia 34
2011 June Florida 12
2011 July Georgia 88**
2012 June–July Texas 16
2013†† June Iowa, Nebraska, and neighboring states 162 Bagged salad mix from Mexico
2013†† June–July Texas 38 Cilantro from Mexico
2013 July Wisconsin 8 Berry salad (suspected)
2014 June Michigan 14
2014‡‡ June–July Texas 26 Cilantro from Mexico
2014 July South Carolina 13
2015 May–July Georgia, Texas, and Wisconsin 90 Cilantro from Mexico
2016 June–July Texas 6¶¶ Carrots or green cabbage (suspected)
2017 May Florida 6 Berries (suspected)
2017 May–July Texas 38*** Scallions (i.e., green onions)
2017 June Michigan 29
2017 June Tennessee 4†††
2017 June Connecticut 3
2017 July Florida 3‡‡‡

21 sick: Ground bison products recalled due to E. coli 0121 and 0103

Little Powell would get them.

Company / Firm:

Northfork Bison Distributions Inc.

Distribution:

National

Extent of the distribution:

Consumer

Contents

Recall details

Recalled products

What you should do

Background

Illnesses

Photos

Public enquiries and media

Recall details

Ottawa, July 16, 2019 – Northfork Bison Distributions Inc. is voluntarily recalling ground bison products from the marketplace due to possible E. coli O121 and O103 contamination. Consumers should not consume the recalled products described below.

Recalled products

Brand Name Common Name Size UPC Code(s) on Product
Natural Frontier Foods Bison – ground meat 280 g 6 76842 00147 7 EXP 190311
EXP 190314
EXP 190315
EXP 190316
EXP 190317
EXP 190318
Sensations Extra Lean Ground Bison 280 g 6 23682 11159 0 EXP 190311
EXP 190314
EXP 190315
EXP 190316
EXP 190317
EXP 190318
La Terre des Bisons Bison ground (lean) 1.5 lb 96768420002598 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01
Northfork Canadian Bison Ranch Bison ground regular 1.25 kg 86768420002577 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01
Northfork Canadian Bison Ranch Bison ground regular 4.54 kg /10 lb 86768420002263 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01
Northfork Canadian Bison Ranch Bison ground 10 lbs regular 4.54 kg 96768420111061 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01
Northfork Canadian Bison Ranch Bison Ground 1 l b regular 0.45 kg / 1 lb 96768420111054 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01
Northfork Canadian Bison Ranch Bison Burger 20 x 8oz 2 lb 96768420111092 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01
Northfork Canadian Bison Ranch Bison Burger 4oz x 4 1 lb 96768420111184 Packed on 19-02-22
Packed on 19-02-25
Packed on 19-02-26
Packed on 19-02-27
Packed on 19-02-28
Packed on 19-03-01

What you should do

If you think you became sick from consuming a recalled product, call your doctor.

Check to see if you have recalled products in your home. Recalled products should be thrown out or returned to the store where they were purchased.

Food contaminated with E. coli O121 and O103 may not look or smell spoiled but can still make you sick. Symptoms can include nausea, vomiting, mild to severe abdominal cramps and watery to bloody diarrhea. In severe cases of illness, some people may have seizures or strokes, need blood transfusions and kidney dialysis or live with permanent kidney damage. In severe cases of illness, people may die.

Worker scratching his crotch led to Florida restaurant’s temporary closure

Beau Zimmer of WTSP reports that ants were seen crawling inside a Tampa Bay area Mexican restaurant – our favorite part of Florida and equidistant from the equator as is Brisbane.

Sabor A Mexico in Brandon is the go-to spot for customer Anna Brooks.

“I just love their home homemade salsa and just a lot of their entrees are really good,” Brooks said as she arrived for lunch.  

Brooks and other customers had no idea this Mexican restaurant was shut down by state inspectors just two weeks earlier.  

The restaurant racked up 65 violations, including meat and salsa stored on the floor and employees not properly washing their hands.  

The report indicated one employee was spotted going from working with raw meat to lettuce. Another was seen scratching their crotch area without changing gloves.

“I have no words for that,” a near speechless Brooks said with a look of bewilderment on her face.  “That’s very gross. That’s very disappointing.”

Health inspectors weren’t done there. The restaurant’s inspection report also listed too many ants to count walking around in the walk-in cooler area.  There was also roach excrement on dry storage shelves holding food and rodent activity with a chewed up plastic lid on top of the tortilla container.

“Wow! That’ eye-opening,” Brooks said.  

The restaurant has now had two full weeks to clean up their kitchen so Wednesday 10News stopped in unannounced.

Within minutes of arriving, the restaurant allowed us behind the kitchen door and almost immediately we started spotting positive changes, like soap and paper towels at all the kitchen handwashing sinks.

137 sick: FDA investigating contaminated pig ear treats connected to Salmonella

I’ve been told that pig ear treats are the equivalent of potato chips for dogs.

One of daughter Sorenne’s chores is to feed our two cats every night, with their special anti-neurotic food.

And every night I say, wash your hands.

Same with Ted the Wonder Dog and treats.

With the recent announcements of the Food and Drug Administration (FDA) and the Centers for Disease Control and Prevention (CDC) investigating contaminated Pig Ear Treats connecting to Salmonella, Pet Supplies Plus is advising consumers it is recalling bulk pig ear product supplied to all locations by several different vendors due to the potential of Salmonella contamination. Salmonella can affect animals eating the products and there is risk to humans from handling contaminated pet products, especially if they have not thoroughly washed their hands after having contact with the products or any surfaces exposed to these products.

There is now 137 sick with Salmonella from handling these things.

Testing by the Michigan Department of Agriculture and Rural Development revealed that aging bulk pig ear product in one of our stores tested positive for Salmonella. We have pulled bulk pig ear product from the shelves at all of our stores and have stopped shipping bulk pig ears from our Distribution Center. We are working with the FDA as they continue their investigation as to what caused the reported Salmonella related illnesses.

Food safety is not simple

If food safety is simple, why do so many get sick?

Because it’s not simple: it’s complex, constant, requires commitment and information must be compelling.

Government, industry and academics continue to flog the food safety is simple line, despite outbreaks becoming increasingly complex and in the complete absence of any data that the message works.

We’ve shown that food safety stories can work. And I’m not embarrassed to wear the Leafs hoodie, because they are at least watchable now, unlike the last 52 years.

Every summer (sure it’s winter here in Australia, but that’s an equator thing, and I still wear shorts 365 days of the year), tucked away in the back pages of every newspaper, it’s the same thing: bland pronouncements about how food safety is easy if consumers follow some simple steps, while the front page usually has another story about another outbreak of foodborne illness.
What’s so simple about outbreaks in produce, pet food and peanut butter? Once the products were home, there was nothing individuals could have done to prevent the subsequent illnesses and deaths. Are consumers really expected to cook all their fresh tomatoes and leafy greens to 165F to kill salmonella? Fry up peanut butter? Bake the cat food?
 Yet there are a multitude of well-meaning groups who preach to the masses that food safety begins at home.
Whether it’s a U.S. Department of Agriculture official saying in 2005 that, “Foodborne illness is very serious but easily prevented if foods are handled, prepared and cooked properly,” or a Canadian retail association saying in 2006 that “E. coli can be prevented through simple in home food safety practices such as washing thoroughly fresh produce in clean water for several minutes before consuming,” the it’s-simple message is pervasive, condescending and wrong.
 Food safety is complex, constant and requires commitment.
Produce, peanut butter and pet food demonstrate that messages focused solely on consumers are woefully incomplete. The World Health Organization recognized this back in 2001 and included a fifth key to safer food: use safe water and raw materials, or, source food from safe sources (http://www.who.int/foodsafety/consumer/5keys/en/index.html).
Consumers must recognize — and demand — that the first line of defense be the farm. Every mouthful of fresh produce, processed food or pet food is a consumer’s act of faith. Every grower, packer, distributor, retailer and restaurant must stop blaming consumers and work instead on developing their own culture that values and promotes microbiologically safe food.

Two elderly Australians die after eating Listeria-contaminated smoked salmon

Sahil Makkar of the Daily Mail writes two elderly people have died and a third is fighting for their life after eating salmon believed to be contaminated.

The two people were from New South Wales and Victoria respectively, while the third person who was rushed to hospital was from Queensland.

All three people have contracted listeriosis.

‘Investigations have implicated smoked salmon as the likely source,’ Australian chief medical officer Brendan Murphy said in a statement.

‘All cases occurred in people aged over 70 years and all had significant underlying health conditions.

Tasmanian salmon products are believed to be the source of the outbreak.

But its two largest suppliers said they are not aware of any evidence linking their products to the outbreak. 

‘Tassal products have not been deemed unsafe, nor has it breached the Food Standards Code,’ Tassal said in a statement.

Huon Aquaculture said health authorities had recently tested and cleared of any food safety law breaches.

Tassal and Huon command 30 per cent and 20 per cent of market share respectively.

Tasmania’s Minister for Primary Industries Guy Barnet said his department has investigated the matter.

Food Safety Talk 187: Must Split and Toast

Don and Ben do their annual live from IAFP show. This year, from the dungeons of the Kentucky International Convention Center, the guys are joined by listeners coming from as far at New Zealand. The show starts with a discussion of IAFP meeting happenings, symposia and back room chatter. The discussion goes to some listener feedback on Chipotle, English muffins, donut walls and ignoring voluntary recall guidance. And papayas.

Photo: Renee Comet (Getty Images)

A few in-studio listeners then join Don and Ben at the mic and ask questions (and get asked questions).

The episode can be found on iTunes and here.

Show notes so you can follow at home:

Faith-based food safety sucks

In a decision issued [June 19, 2019] in Marchand v. Barnhill et al., No. 533, 2018 (Del. June 19, 2019), the Delaware Supreme Court reversed the dismissal of a stockholder derivative lawsuit against the members of the board of directors and two officers of Blue Bell Creameries USA, Inc.

The lawsuit arose out of a serious food contamination incident in 2015 that resulted in widespread product recalls and was linked to three deaths. The Delaware Supreme Court, applying the “duty to monitor” doctrine enunciated in In re Caremark International, Inc. Derivative Litigation, 698 A.2d 959 (Del. Ch. 1996), and noting the very high hurdle to claims under it, nonetheless ruled that the plaintiff had adequately alleged the requisite bad faith by the members of the Blue Bell board.

Plaintiff did so by using information obtained in a Section 220 books and records demand to show facts supporting their contention that the Company did not have in place “a reasonable board-level system of monitoring and reporting” with respect to food safety, which the Court deemed to be “a compliance issue intrinsically critical to the company’s business.”

After concluding that “food safety was essential and mission critical” to Blue Bell’s business, the Supreme Court ruled that bad faith was adequately pled by alleging “that no board-level system of monitoring or reporting on food safety existed.” The Court thus declined to dismiss a claim that the directors breached their duty of loyalty, potentially exposing directors to non-exculpated (and potentially not indemnifiable) monetary damages.

In light of the Blue Bell decision, boards of directors should review carefully their board processes and procedures to ensure that “reasonable compliance system and protocols” are in place with respect to “safety and legal compliance” and other regulatory and business threats that may pose significant risks for their particular company.

Equally important, boards should document the procedures followed to identify significant risks, including advice from management, counsel and other advisors, as well as the processes and procedures implemented to provide for board reporting and appropriate supervision of these risks, and maintain written records of the implementation of these processes and procedures in practice. The principal basis upon which the Court in Blue Bell found the record to support the complete failure to impose any board-level “system of controls” with respect to food safety was the absence of any written board procedures or documented discussion on the topic, and the lack of any mention of food safety in board minutes in periods before the food contamination outbreak, despite previous food safety issues that allegedly had arisen in previous years, including positive tests for listeria in Company facilities beginning in 2013.

The Blue Bell decision makes clear that oversight with respect to these kinds of issues is a board-level responsibility, and goes beyond mere compliance with laws. The Delaware court opined that “the fact that Blue Bell nominally complied with FDA regulations does not imply that the board implemented a system to monitor food safety at the board level.”

“In short,” the Delaware Supreme Court ruled, “to satisfy their duty of loyalty, directors must make a good faith effort to implement an oversight system and then monitor it.” While “routine regulatory requirements, although important, are not typically directed at the board,” companies should ensure that they have written processes and procedures in place for the board to be timely informed about, and to monitor regularly, compliance, safety and business developments that are important to the company, or may be viewed as critical to the company in hindsight. [1]

This decision, while only on a motion to dismiss, illustrates the continued importance of the Caremar kdoctrine as a strand of Delaware law governing the conduct of directors. While the burden for withstanding a motion to dismiss a Caremark claim is high, and the theory remains “possibly the most difficult theory in corporation law upon which a plaintiff might hope to win a judgment,” [2] it can be met. Caremark is an important tool in the Delaware jurisprudential arsenal for enforcing what Delaware courts view as reasonable director conduct, and when applied sends a powerful message because of the potential it creates for personal director liability.

11.jul.19

Harvard Law School Forum on Corporate Governance and Financial Regulation

Brian Frawley, Joseph Frumkin and Krishna Veeraraghavan

https://corpgov.law.harvard.edu/2019/07/11/bad-faith-monitoring-on-food-safety-issues/

Indian takeaway which had no sink and served raw chicken ordered to pay £42K in UK

Latifa Yedroudj of the Mirror reports an Indian takeaway boss has been ordered to pay £42,000 in fines after food hygiene inspectors found his restaurant did not have a sink.

Mr Biryani restaurant in Slough, Berkshire has been slammed for breaching food hygiene requirements 10 times over the past two years since the eatery opened for business.

Owner Santosh Ragalpavi Balasubramaniam, 37, from Maidenhead, Berks has been slapped with staggering fines after inspectors found his chefs did not have a sink to wash their hands and served undercooked chicken.

The restaurant was also ordered to dispose of all of its food and disinfect the premises after sewage water flooded the basement.