Changes between Version 9 and Version 10 of Ticket #29, comment 1
- Timestamp:
- 2022-12-08T21:54:55Z (18 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29, comment 1
v9 v10 1 1 '''REPORTED10KG''' 2 2 3 ''Subsection 27(6) (new subsection relaxes rigour by using the word "known")'' 4 5 The word "known" implies that the person introducing the chemical would say so if the characteristic of interest to AICIS was known to exist. 3 ''Subsection 27(6) new subsection relaxes rigour by using the word "known"'' 6 4 7 5 For example, if the software did not independently detect mutagenicity, carcinogenicity or reprotoxicity then it can be accepted as not known by the introducer to be so. This is because the user can add such hazards and the software would thereby "know" such a characteristic exists. 8 9 The new Reported category of 10kg or less does not need to tick the boxes ticked for normal categories.10 6 11 7 In practice, health and environment categorisation volumes are irrelevant - they are less than 10kg. Exposure and release factors are also irrelevant for such a small quantity. … … 16 12 '''Program redesign''' 17 13 18 We have a set_category() method which first eliminates excluded, prohibited and other possible categorisations including Listed set according to circumstances established by the user and then tests for risk to determine Exempted, Reported or Assessed.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. 19 15 20 If the risk is actually very-low, we might ignore REPORTED10KG and categorise as Exempted. The reasoning is that REPORTED10KG is then unnecessary and ifused AICIS would need to be notified in future if volumes increased beyond 10kg.16 If the risk is actually very-low, we might ignore REPORTED10KG and categorise as Exempted. The reasoning is that if REPORTED10KG is used AICIS would need to be notified in future if volumes increased beyond 10kg. 21 17 22 However, an introducer might opt for the REPORTED10KG simply to avoid having to obtain documentation potentially demanded by AICIS to prove the Exempted 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 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. 23 19 24 20 We need a mechanism for the user to opt for REPORTED10KG. See Ticket #36 … … 32 28 3. Reported - low risk 33 29 4. Assessed - medium to high risk 34 35 When all is working correctly and unit tests are passing this ticket will be closed.36 30 37 31 … … 48 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. 49 43 50 If used in a cosmetic, must not be prohibited or restricted in cosmetics by EU or USA44 If used in a cosmetic, it must not be prohibited or restricted in cosmetics by EU or USA 51 45 52 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. There are chemicals on the EUR-Lex Cosmetics lists which are allowed with conditions. Some of those 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 46 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 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 53 49 54 50 and … … 60 56 Not (known) to be nanoscale 61 57 62 ''Nano-material'' already has a selection 'Not known' which AICIS (and the software) treats as 'Yes' but without a study report on nano particle dimensions. See Ticket [ticket:28#comment:3] which implements this.58 ''Nano-material'' already has a selection 'Not known' which AICIS (and the software) treats as 'Yes' but without needing a study report on nano particle dimensions. See Ticket [ticket:28#comment:3] which implements this. 63 59 64 60 and … … 66 62 Not (known) to contain Fluorine or 67 63 68 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.64 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. 69 65 70 66 IS known to be an inorganic salt … … 74 70 and 75 71 76 Not (known) Persistent, Bioaccumulative and Toxic T72 Not (known) Persistent, Bioaccumulative and Toxic (PBT) 77 73 78 Already detected via CAS number search of the list of chemicals with high hazards for categorisation or the user has entered data including adding GHS H400 or H410 hazards. See Ticket #3774 Already detected via CAS number search of the high hazard chemicals for regular categorisation - or the user has added the hazard data. See Ticket #37 79 75 80 76
