EFSA Data Collection using SSD2 for pesticide monitoring results Jens Hinge Andersen (jhia@food.dtu.dk) Dept. of Risk Assessment and Nutrition National Food Institute, DTU Food (www.food.dtu.dk)

Outline SSD: Standard Sample Description Using SSD for pesticide monitoring results: Some challenges using SSD1 Moving from SSD1 to SSD2 Some challenges using SSD2 Some potential improvements using SSD2 Implementation of FoodEx2 in DK

SSD: Standard Sample Description EFSA collects data from National authorities Research institutions Industry In a standardised data format on Pesticide residues Chemical contaminants Additives Zoonosis Veterinary drugs Food consumption FoodEx2 SSD1 SSD2

SSD1 SSD2 ≈35 relevant elements ≈35 relevant elements 76 elements total 204 elements total

Some challenges using SSD1 for pesticide monitoring results (1) Product Treatment / MRL applicabillity Are EU-MRL applicable for processed food? No element for this specific information is present in SSD1. Pesticide domain: Use Product Treatment (prodTreat): Unprocessed => EU-MRL is applicable Processed => EU-MRL is not applicable This may conflict with other data domains when e.g. dry beans or black tea must be reported as ‘Unprocessed’ in the pesticide domain to reflect MRL legislation.

Some challenges using SSD1 for pesticide monitoring results (2) Program Type / EU coordinated program Are sample part of the EU coordinated program ? No element for this specific information is present in SSD1. Pesticide domain: Use Program Type (progType): ‘Official (EU) programme’ => YES ‘Official (EU or National) programme’ => YES ‘Official (National) programme’ => NO This may conflict with other data domains when e.g. samples from Directive 96/23 must be reported (draft 2014 Guideline) as ‘Official (National) programme’ in the pesticide domain.

Moving from SSD1 to SSD2 New names to elements, new ordering of elements You can keep your present structure, just changing names and ordering when XML-file is written New type of element: Compound elements You can keep fields separate in your database, just creating the compound text when the XML-file is written New catalogue structure: FoodEx2 catalogue Parameter catalogue Method catalogue !!! (changes in structure can be ignored) (changes in structure can be ignored)

Moving from SSD1 to SSD2 SSD1 SSD2 Product Code (prodCom/MATRIX) Product Treatment (prodTreat/PRODTR) Type of matrix (sampMatType/MTXTYP): Food Feed Coded description of the matrix of the sample taken (sampMatCode /FoodEx2) Analytical method type (anMethType/ ANLYTYP): Quantitative Screening

Some challenges using SSD2 for pesticide monitoring results (1) New food description catalogue: FoodEx2 Base code A0DZB for ‘Oranges’ A03AM for ‘Juice, orange’ +Facets A0DZB#F21.A07SE for ‘Oranges (organic production)’ A03AM#F21.A07SE$F28.A07KQ for ‘Juice, orange (organic production, frozen)’ http://www.efsa.europa.eu/en/datex/datexfoodclass.htm Francesco Vernazza <Francesco.VERNAZZA@efsa.europa.eu>

Some challenges using SSD2 for pesticide monitoring results (2) prodCode/MATRIX catalogue is missing from SSD2 prodTreat/PRODTR catalogue is missing from SSD2 FoodEx2 codes not directly linked to legislation No simple relation between FoodEx2 code and MRL applicability

prodCode/MATRIX catalogue P0110020A

prodTreat/PRODTR catalogue prodTreat in the pesticide data domain is used as: EU-MRL is applicable or not No simple relation between FoodEx2 code and MRL applicability

prodTreat/PRODTR catalogue Suggested solution in SSD2 Create a new element: Is EU-MRL applicable ? (YES or NO) in a compound element In addition, create a new element: Processing factor (decimal) in the same compound element Compound element: sampMatInfo or resInfo

prodTreat/PRODTR catalogue Suggested solution in SSD2 <sampMatInfo> MRLapplic=NO $procFactor=3.4 $Com=PF based on loss of water during drying </sampMatInfo>

Transformation of data from DK LIMS to EFSA via DTU Food DVFA Extract from datawarehouse at Danish Vet. and Food Administration DTU Extract received in DTU data base Recoded by local translation tables Supplemented with missing data Write data set as an XML file EFSA XML received in DCF (Data Collection Framework)

Implementation of FoodEx2 in DK (1) DK LIMS categorise products by: Base element (e.g. ‘Orange juice’) Three facets for Heat treatment (e.g. frozen) Physical condition (e.g. powder) Other treatment (e.g. concentrate) FoodEx2 code: Base code: A03CA (Juice concentrate, orange) Facet: F28.A07KQ (TECHNO=Freezing) XML: <sampMatCode>A03CA# F28.A07KQ</sampMatCode>

Implementation of FoodEx2 in DK (2) DTU EFSA product table DK LIMS product table DTU EFSA production table DK LIMS sample table Frozen orange juice concentrate, organic production: <sampMatCode>A03CA#F28.A07KQ$F21.A07SE</sampMatCode>

Thank you for your attention