Transcript Codex Alimentarius

Science - the basis
of CODEX work
The Role of Science in Codex
Decision-Making
Science guides the whole process of Codex work
Key principles
 Risk analysis guide Codex stds from development to
implementation
 Codex texts shall be based on science and evidence
 Food safety risk assessment should be based on
sound data and includes four steps process
 Functional separation of Risk Assessment & Risk
Management
Codex Process: Science-based,
Participatory and Transparent
International Risk Assessment
• JECFA
(food additives, veterinary
drug residues, contaminants in
food)
Requests for
advice, risk
assessment
• JMPR
(pesticide residues in food)
• JEMRA (microbiological
hazards in food)
• ad hoc expert consultations
emerging issues (e.g.
Nanotechnologies in agri-food
sector)
Scientific
advice
International
Risk Management
CODEX
ALIMENTARIUS
COMMISION
Criteria for the Establishment of
Codex Work Priorities





Contribution to the protection of consumer health
Diversification of national legislations and potential
impediment to international trade
Product suitability for standardization
Existence of duplication with work already undertaken in this
area
Volume of production and consumption
Members can request for prioritization of work
•Provide scientific arguments to include topic in the priority list
•Provide data
Science to start work: the case of Sorghum
Sorghum - mycotoxin formation
 Concerns raised
in the Codex
Committee on Contaminants as to
human health impact
 Important staple food in many African
countries
 Lack of information on formation and
levels of mycotoxins in grain
FAO/WHO are implementing a project
with funding from EC in Burkina Faso,
Ethiopia, Mali and Sudan to
 gather data and knowledge
 to feed back into the discussion at
international level on options for action
Science to update work: the example
of Fumonisins


Fumonisins were previously evaluated by JECFA in 2001
The 3rd Session of the CCCF agreed to initiate work on establishing MLs for fumonisins in
maize and some maize-based products



Data were submitted only by Argentina, Australia, China, Japan, Nigeria, EU, the UK and USs
General agreement on the need for MLs but not on the levels
The 4th session CCCF agreed to retain the proposed draft MLs at Step 4 until further
advice was provided by JECFA

JECFA (June 2011) evaluation concluded




Implementation of the MLs proposed by CCCF could significantly reduce exposure to total
fumonisins
the proposed MLs would result in rejection of 2–88% of “Corn/maize grain, unprocessed” and 4–
57% of “Corn/maize flour/meal” across the clusters.
submitted data show that the exceedance of the PMTDI occurs only in limited regions presenting
high maize consumption levels and highly contaminated maize.
PMTDI for fumonisins was retained
Science to implement work: the case
of Vibrio
Codex Guidelines on the Application of General Principles of
Food Hygiene to the Control of Pathogenic Vibrio Species in
Seafood in have been developed in 2010
CCFH requested FAO/ WHO to work on risk assessment tools to
facilitate the implementation of Codex guidelines


FAO/ WHO work




An expert meeting was organized in Ottawa, Canada on October 17-19, 2011 to:
(a) identify possible end uses of Vibrio methodologies (b) look at the performance
characteristics of available methods and provide recommendations on the requirements
for different end uses (c) provide recommendations for collection of data to support
national/regional risk assessments.
The output of this Expert Meeting and subsequent discussions are being used to develop a
“Guidance document” addressing performance characteristics of Vibrio methodology and
approaches for data collection.
As a follow up to this, a Regional training Workshop for Asia on Vibrio methodologies is
scheduled to be held in Singapore during November 19-23, 2012.
Conclusions

Science guide Codex working process from stds
development to implementation.

It is essential that countries generate science
data/information
to support their positions at Codex
 to actively guide the stds development process
 to ensure global relevance of Codex outputs
