--- title: "Cyclospora refrigerator checklist" date: "2026-07-11" canonical: "https://raytally.com/en/ideas/2026-07-11-cyclospora-parasite-outbreak-3870527/" generator: "RayTally · dev-prompt-v4" signal: query: "cyclospora parasite outbreak" observed_at: "2026-07-11T01:31:01.810Z" window_hours: 168 sources: - url: "https://apnews.com/article/022730ccbc514e15b1f0021c47bf1b68" boundary: "Published at 2026-07-10." - url: "https://www.fda.gov/food/outbreaks-foodborne-illness/investigations-foodborne-illness-outbreaks" boundary: "Published at 2026-06-26." - url: "https://www.michigan.gov/mdhhs/inside-mdhhs/newsroom/2026/07/01/cyclosporiasis" boundary: "Published at 2026-07-01." - url: "https://www.prnewswire.com/news-releases/recallsentry-app-launch--your-home-safety-hub--free-on-ios--android-302710138.html" boundary: "Published at 2026-03-09." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-11-cyclospora-parasite-outbreak-3870527/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Cyclospora refrigerator checklist Turns shopping receipts into a refrigerator checklist during a Cyclospora outbreak. ## Product concept Someone who sees news about a Cyclospora outbreak after lunch can photograph fresh-produce labels in the refrigerator or upload a shopping receipt. The page separates the produce items into a list, item by item. After the user selects the purchase date and location, it generates a kitchen checklist with three categories: do not eat yet, check closely, and not currently involved. It also shows where to find the package lot number. If a family member develops symptoms, the user can organize high-risk foods eaten over the past two weeks, purchase locations, and dates into a short record to bring to a medical visit. The result is not a generic food-safety article, but same-evening handling steps generated from the contents of the user’s refrigerator. It is designed for the confusing moment in a Cyclospora outbreak when symptoms may be delayed and consumers have difficulty remembering what they ate. ## Why now (backed by facts) As of July 10, 2026, Michigan had reported more than 1,500 Cyclospora infections, another 30 states were investigating similar cases, and the FDA still had not identified the specific product sources for two related outbreaks on June 26. A trend snapshot from the same period showed about 200000+ related searches in the United States, up about 1000%. During the window when cases are rising but contaminated products have not been identified, turning shopping records and refrigerator contents into checklists that can update with the investigation is especially worth building. ## Direction (model inference, not independently verified) Target user: Household shoppers who have just seen news about Cyclospora cases or a fresh-produce outbreak in their state and are standing at the refrigerator trying to decide what to discard. They may also open it when a family member has persistent diarrhea and is preparing to contact a doctor, to fill in the past two weeks of foods, stores, and dates. Minimal entry point: The first version accepts only shopping receipts or fresh-produce label photos. Users add the purchase date and location, and the product generates a three-level checklist based on official outbreak and recall notices. It also provides a one-page, exportable record of foods eaten and purchased over the past two weeks. The strongest case against: The strongest case against this is that, when an investigation has not identified a specific product, the tool cannot reliably label a particular fresh item as "do not eat yet." If its categories appear more certain than the official evidence, it could create false alarms or a false sense of safety. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Create state-level investigation pages for high-intent searches such as "cyclospora outbreak + state name," "which fruits and vegetables are affected," and "how long until symptoms appear." Keep them updated as official investigations change, and let users share household checklists without medical privacy information with family members. ## Competitors & gaps (model inference) - RecallSentry: RecallSentry already scans UPCs and matches household items with official recall data from the FDA, USDA, and others. The gap here is handling fresh produce without a clear UPC and outbreaks that have not yet resulted in a formal recall, then organizing receipts, purchase locations, dates, and eating history into an action checklist for the specific investigation. ## How it makes money (model inference) Charge households a one-time fee for an outbreak-check package that includes receipt parsing, continuously updated checklists, and an exportable doctor-visit summary. ## Trend background Theme: Cyclospora outbreak Trigger query (original English): cyclospora parasite outbreak Approx. search volume: 200000+ (approximate) Approx. increase: +1,000% (approximate) The trend data is a historical snapshot from the moment it was captured; volume and increase are approximate and only explain “why now.” Do not write them into product copy as precise market numbers. ## Sources - How to stay safe and still enjoy produce this summer with the outbreak of diarrhea-causing parasite (https://apnews.com/article/022730ccbc514e15b1f0021c47bf1b68) - Investigations of Foodborne Illness Outbreaks (https://www.fda.gov/food/outbreaks-foodborne-illness/investigations-foodborne-illness-outbreaks) - Outbreak of cyclosporiasis occurring in Michigan (https://www.michigan.gov/mdhhs/inside-mdhhs/newsroom/2026/07/01/cyclosporiasis) - RecallSentry App Launch -- Your Home Safety Hub -- Free on iOS & Android (https://www.prnewswire.com/news-releases/recallsentry-app-launch--your-home-safety-hub--free-on-ios--android-302710138.html) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.