rebecca lee, phd nappo technical director ephyto steering committee member

25
Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member ePhyto Code Lists Slides courtesy of Nico Horn, 2012, except where otherwise indicated.

Upload: trory

Post on 05-Jan-2016

72 views

Category:

Documents


0 download

DESCRIPTION

Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member. ePhyto Code Lists. Slides courtesy of Nico Horn, 2012, except where otherwise indicated. Harmonisation of Contents: Codes. Why codes? Fullest use of electronic system possible Avoids mismatches by typing errors - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Rebecca Lee, PhDNAPPO Technical Director

ePhyto Steering Committee member

ePhyto Code Lists

Slides courtesy of Nico Horn, 2012, except where otherwise indicated.

Page 2: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

• Why codes?

Fullest use of electronic system possible

– Avoids mismatches by typing errors– Unambiguous spelling of names, etc.– Language independent– Makes digital checks possible– More efficient– Flexibility to update

Harmonisation of Contents: Codes

Page 3: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Four Subgroups of Codes

- Scientific names

- Treatments

- Additional declarations

- Product description

Page 4: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Principles

• Use existing lists as much as possible• Preferrably these lists should be

available on the internet and regularly updated

• Only create new lists where really necessary

Page 5: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Scientific NamesWorking Procedure

• Formulate criteria for lists• Collect possible candidates• Short list three candidates• Select the preferred candidate• Formulate recommendation

Page 6: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Recommendation for Scientific Names

The EPPO list of plants and plant pests is the best candidateavailable at the moment to be used in ePhyto as list of pestand plant names including codes for them.

• Codes are easily accessible• They can be freely accessed:

http://eppo.org/DATABASES/eppt/eppt.htm• Or: Cheap subscription for electronic version of all names and

codes (similar to ISO country code list)• Takes into account synonyms, old names, pathovars and multi-

lingual common names• Additions to the list can be proposed and will be processed• However, additions should be considered only if involved in trade

(allows for prioritization of additions)

Page 7: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member
Page 8: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member
Page 9: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

For cultivated and wild species (including weeds)For cultivated and wild species (including weeds)

5 letters = 3 (genus) + 2 (species)5 letters = 3 (genus) + 2 (species)

S O L T US O L T U

Solanum tuberosum: SOLTU

An unspecified species of Solanum: SOLSSSS

Genus Solanum: 11SOLGG

Solanaceae Family: 11SOLFF

Polemoniales Order: 11POMOO

Dicotyledons Group: 11DICSS

Magnoliophyta Division : 11MAGPP

Plant Kingdom: 11PLAKK

EPPO codes: A few general principles

Courtesy: EPPO, 2012

Page 10: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

EPPO codes: A few general principles (cont.)

For plant pests and pathogens: For plant pests and pathogens:

6 letters = 4 (genus) + 2 (species)6 letters = 4 (genus) + 2 (species)

B E M I T AB E M I T A

The species Bemisia tabaci: BEMITA

An unspecified species of the genus Bemisia: BEMISPSP

Genus Bemisia: 11BEMIGG

Aleyrodidae Family: 11ALEYFF

Sternorrhyncha Suborder: 11STERSS

Hemiptera Order: 11HEMIOO

Insecta Class: 11INSECC

Animal Kingdom: 11ANIMKKCourtesy: EPPO, 2012

Page 11: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

1 biological entity = 1 unique code1 biological entity = 1 unique code

Change of preferred scientific name:Change of preferred scientific name:Gnorimoschema absoluta = Tuta absoluta => The code GNORABGNORAB remains the same

Newly described species:Newly described species:Phytophthora pinifolia => PHYTPFPHYTPF is newly created

New subspecies: additional codesNew subspecies: additional codesXylella fastidiosa = XYLEFAXylella fastidiosa subsp. multiplex => XYLEFMXYLEFMXylella fastidiosa subsp. pauca => XYLEFPXYLEFPXylella fastidiosa subsp. sandyi => XYLEFSXYLEFS

EPPO codes: a few general principles (cont.)

Courtesy: EPPO, 2012

Page 12: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Special form on the web to request new codes

Courtesy: EPPO, 2012

Page 13: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Treatments ListWorking procedure

• Elements of treatment: – date (standard format used)– treatment type – active ingredient – duration *– temperature *– concentration*• No new code list required (UNECE recommendations)

• Focus on treatment type and active ingredient• Different lists available were considered• One list stood out for active ingredient• For treatment type, no useful list available• Therefore, for treatment type, a list was created

Page 14: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

http://ephyto.ippc.int/

Page 15: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Recommendation for Treatment Types

For ePhyto it is useful to code the active ingredients

and the treatment types.

For the active ingredients the CODEX list is proposed (http://www.codexalimentarius.net/pestres/data/pesticides/index.html )

For the type of treatments a table was created and

proposed

Page 16: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Treatment TypesHeat treatment HTFumigation FUMSeed coating SCKiln-drying KDChemical pressure impregnation CPIDevitalization DV Debarking DB Dry heat DHMoist heat MHVapour heat VHDipped DiCold Disinfestation CD Cold treatment CTDusted DuFlood sprayed FSFungicide Fu

Could also be divided by:

Heat treatment

Cold treatment

Chemical

Irradiation

Other

- And then subdivide at a 2d level

Still under discussion based on member comments

Page 17: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Additional Declarations Working Procedure

• One possibility was to collect all ADs used worldwide and code them

• Conclusion was to restrict coding to standard ADs as in appendix 2 of ISPM12

• This will help standardisation, is language-independent, covers the whole range, achievable for the WG

• Standard ADs analysed: some need pest names, area names and some are actually two in one

• Standard ADs were tabled and codes were added

Page 18: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Recommendation for Additional Declarations

For ePhyto, it would be very useful to code additional declarations.

Impossible to code all additional declarations, thereforefree text should always be an option.

The codes represent standard wording of ADs but canbe used irrespective of language and the intention ofthe AD is more important than the exact wording.

Page 19: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Reference Numberin ISPM 12

Text Code AD Additional Code Free text (optional)

1. The plants were inspected and found free …. SAD 1 name organism “soil”“practically free”

2. The plants were tested and found free from…. SAD 2 name organism testing method 3. The growing media in which the plants were grown was

tested prior to planting and found free from…..SAD 3 name organism

4.1. …….is absent in …… SAD 4.1 name organism, name country

name of area

4.2. ……is not known to occur in….. SAD 4.2 name organism, name country

name of area

5.1. The plants were produced in a pest-free area for…. SAD 5.1 name organism “Including a surrounding buffer zone “

5.2. The plants were produced in an area of low pest prevalence for......

SAD 5.2 name organism

5.3. The plants were produced in a pest-free place of production for….

SAD 5.3 name organism “Including a surrounding buffer zone “

5.4. The plants were produced in a pest free production site for….

SAD 5.4 name organism “Including a surrounding buffer zone “

6.1. The place of production was inspected during the growing season and found free from…..

SAD 6.1 name organism number of seasons, “Including a surrounding buffer zone”,frequency of inspection

6.2. The production site was inspected during the growing season and found free from…..

SAD 6.2 name organism number of seasons,frequency of inspection

6.3. The field was inspected during the growing season and found free from…..

SAD 6.3 name organism number of seasons,frequency of inspection

6.4. The field and a surrounding buffer zone was inspected during the growing season and found free from…..

SAD 6.4 name organism number of seasons,frequency of inspection

Code is language independent – this is what we aspire to, based on ISPM 12, seeking more standardization.

Page 20: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Product Description Working Procedure

• Elements of product description: botanical name, intended use, packaging, weight and volume and additional description

• Focus on intended use and additional description• Custom codes/ HS are preferred but worldwide not

sufficiently descriptive for phytosanitary use• No useful list available worldwide• Table with elements created and codes assigned• Free text still needed, e.g. for HS code, further

description

Page 21: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Recommendation for Product Description

Product description coding to be formed from a minimum of 4 elements: - Product (the botanical name where available, WG 2A)– “Intended Use” – Packaging (UNECE codes)– Country of origin (ISO codes).

The combination of the code elements to be formed by eachNPPO to meet the particular needs of the intended ePhyto

The inclusion of a free text field to enable additional informationto be included where applicable or necessary.

Page 22: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Product DescriptionCategory Level – a 4 character code:Growing medium GRMEPlants for Consumption PLCOPlants – Living Other PLLOPlants intended for Planting PLPLPlant Products PLPR

Primary Level – a 3 character code:Bulbs; Corms; Tubers; Rhizomes BCTCut Branches with Foliage CBFCut Branches CBRCut Flowers CFLCotton COTCuttings CUTFruits FRUGrains GRA

Secondary Level – a 2 character code:Baled BABare-rooted BRDried DRFresh FRFrozen FZWith media - unpotted MUWithout bark NBWithout foliage NF

Plants for Consumption Fruits Fresh PLCOFRUFR

Page 23: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Additional Recommendations

• For duration, temperature, concentration (treatment)

• For weight, volume (product description)• For locations (point of entry, address

consignee)

Use UNECE recommendations

Already available, also used by Customs

Page 24: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Concluding Remarks

• The reports of all four WGs are available on the IPPC website

• Development of codes is an on-going process

• What is available now is a good starting point

Page 25: Rebecca Lee, PhD NAPPO Technical Director ePhyto Steering Committee member

Questions???