Cyclospora outbreak ends; FDA investigation continues

Record each authority status on its own clock

The direct answer is that “outbreak over” and “investigation complete” are not interchangeable. FDA's official page attributes the September 11 outbreak-end declaration to CDC and separately says FDA's investigation continues. A maintained record should name the authority, outbreak reference or identity, food and supplier scope stated by that authority, status class, status date, observation time, source URL, prior state, and any open activity. One summary status should not close both records.

Use precise states such as active outbreak response, outbreak declared over, recall active or completed when an authority establishes it, investigation continuing, root cause unresolved, inspection or sampling underway, post-response work active, and record closed. Do not infer a consumer-risk window, product shelf-life status, recall completion, contamination source, responsible party, or investigation result from CDC's outbreak-end declaration. Those conclusions require their own authoritative evidence.

Freeze the traceback and recall evidence actually stated

FDA says that in July the agencies' traceback converged on a single supplier of iceberg lettuce and that Taylor Farms de Mexico initiated a voluntary recall. It also says onsite inspections and sample collection began in August. Preserve each event with its date, authority, named food, supplier identity as stated, geographic and lot scope when established, supporting record, linked recall, inspection or sample identifier, and limits. Later status changes should append to that sequence rather than rewrite it.

Traceback convergence is not the same as a completed root-cause finding. A supplier-level statement also does not identify every farm, field, harvest, lot, shipment, customer, or consumer unit. Lot genealogy should retain transformation, commingling, repacking, shipment, receipt, inventory, disposition, and correction events only where supported. Unknown lot or distribution boundaries must remain unknown instead of being filled from a company name or category.

Keep post-response work attached to open questions

FDA says it continues investigating the outbreak and its root cause, is working with Mexican public-health and agricultural officials, is calling for supply-chain collaboration, and plans to update its prevention action plan with lessons learned. Each action should identify the question it addresses, accountable authority or partner, source, start and completion state, evidence produced, affected prevention or response control, and publication or implementation decision.

A meeting, industry letter, action-plan update, inspection, or sample can advance prevention work without resolving the outbreak's cause. Separate recommendations from binding requirements and observed findings from planned activity. If FDA later publishes a root-cause analysis or changes the outbreak record, retain the September 11 snapshot and link the new evidence. That chronology lets teams explain what was known when recall and prevention decisions were made.

Test closure without closing the wrong record

Run a tabletop in which CDC declares an outbreak over while FDA investigation, supplier records, inspection results, corrective actions, and action-plan work remain open. Reviewers should update public-health status, preserve recall and lot records, identify unresolved root-cause and distribution questions, route new evidence, and show which internal cases can close and which must stay active. The test should also verify that later corrections do not silently change the historical outbreak snapshot.

FDA's official page establishes the attributed outbreak-end status, continuing investigation, prior traceback and recall sequence, inspection and sampling activity, and planned post-response work. It does not establish the root cause, every affected lot or recipient, recall effectiveness, complete distribution, supplier fault, legal liability, future control effectiveness, compliance, or food-safety outcome. FDA, CDC, state and international authorities, food businesses, recall coordinators, laboratories, and qualified food-safety and legal owners retain those responsibilities.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Food Traceability Ledger will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.