Changes between Version 10 and Version 11 of Ticket #29, comment 1
- Timestamp:
- 2022-12-09T04:34:28Z (17 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29, comment 1
v10 v11 14 14 We have a set_category() method which first eliminates excluded, prohibited and other possible categorisations including Listed set according to ''Circumstances'' defined by AICIS Rules and selected by the user and then tests for risk to determine Exempted, Reported or Assessed. 15 15 16 If the risk is actually very-low, we might ignore REPORTED10KG and categorise as Exempted. The reasoning isthat if REPORTED10KG is used AICIS would need to be notified in future if volumes increased beyond 10kg.16 If the risk is actually very-low, we could ignore REPORTED10KG and categorise as Exempted. The reasoning might be that if REPORTED10KG is used AICIS would need to be notified in future if volumes increased beyond 10kg. 17 17 18 However, an introducer would opt for REPORTED10KG simply to avoid having to obtain documentation potentially demanded by AICIS to prove the Exempted or Reported category. The boxes which do need to be ticked won't keep the chemical out of the Assessed category if it is reviewed pre-introduction and AICIS detect or suspect a medium to high risk.18 However, an introducer would probably opt for REPORTED10KG simply to avoid having to obtain studies to prove an Exempted or Reported category. 19 19 20 20 We need a mechanism for the user to opt for REPORTED10KG. See Ticket #36 21 21 22 In any case, if the chemical fails the set of rules for <= 10kg then it will be Exempted, Reported or Assessed. 23 24 This puts the new hierarchy of categories as: 25 26 1. Exempted - very low risk 27 2. Reported <= 10kg - low risk 28 3. Reported - low risk 29 4. Assessed - medium to high risk 30 22 In any case, if the chemical fails any of the set of rules for <= 10kg then it will be Exempted, Reported or Assessed. 31 23 32 24 '''Rules''' … … 35 27 36 28 Not (known) mutagenic or 37 38 29 Not (known) carcinogenic or 39 40 30 Not (known) reprotoxic or 41 31 42 For these three we need a new method which simply returns True if any of GHS hazards H340 or H341 or H350 or H351 or H360 or H361 are attached to the chemical. See ticket #37.32 For these three we need a new method which simply returns True if any of GHS hazards H340 or H341 or H350 or H351 or H360 or H361 are attached to the chemical. Likewise for PBT. See ticket #37. 43 33 44 34 If used in a cosmetic, it must not be prohibited or restricted in cosmetics by EU or USA … … 46 36 For this we need a new ''is_banned_for_cosmetics()'' method which scans the index for a chemical (CAS and/or name and/or EC number) and if detected returns True if prohibited or restricted. 47 37 48 There are chemicals on the EUR-Lex Cosmetics lists which are allowed with conditions. Some of those cosmetic conditions may concern AICIS when/if the chemical is listed on the Australian inventory, the listing may carry similar conditions. There are similar lists for the USA. See Ticket #34 38 There are chemicals on the EUR-Lex Cosmetics lists which are allowed with conditions. That means they are not banned by AICIS for REPORTED10KG. 39 40 As an aside, some of those cosmetic conditions may concern AICIS. When/if they list the chemical on the Australian inventory, the listing may carry similar conditions. See Ticket #34 49 41 50 42 and … … 60 52 and 61 53 62 Not (known) to contain Fluorine or54 Not (known) to contain Fluorine 63 55 64 56 We do need a ''has_fluorine()'' method which returns True if the molecular formula has a symbol 'F' or there is 'fluo' in the names. Returning False means it is not known to contain Fluorine. See Ticket #32. 65 57 66 IS known to be an inorganic salt58 OR IS known to be an inorganic salt 67 59 68 60 We already have element detection methods and organic/inorganic detection. See Ticket #33
