New category Reported 10kg

[Mike Dewhirst]

AICIS published new rules in late November for a Reported category for chemicals with an annual volume of 10kg or less.

The main effect is relaxation of the rigour surrounding provision of information; low volume being recognised as reducing absolute risk.

The chemical does need to be categorised as Reported 10kg.

Some extra characteristics are declared such as not containing Fluorine or being an inorganic salt and not being on the banned or restricted EU or USA lists of cosmetic ingredient lists.

These will give rise to specific tickets here.

This ticket will remain open as a summary of the changes until all work is done. Further study will result in edits hereto.

[Mike Dewhirst]

REPORTED10KG

Subsection 27(6) (new subsection relaxes rigour by using the word "known")

The word "known" implies that the person introducing the chemical would say so if the characteristic of interest to AICIS was known to exist.

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.

The new Reported category of 10kg or less does not need to tick the boxes ticked for normal categories.

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.

The entire purpose of the new 10kg category is to relax information provision requirements which are so difficult for Australian introducers with taciturn overseas suppliers.

Program redesign

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.

If the risk is actually very-low, we might ignore REPORTED10KG and categorise as Exempted. The reasoning is that REPORTED10KG is then unnecessary and if used AICIS would need to be notified in future if volumes increased beyond 10kg.

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.

We need a mechanism for the user to opt for REPORTED10KG. See Ticket #36

In any case, if the chemical fails the set of rules for <= 10kg then it will be Exempted, Reported or Assessed.

This puts the new hierarchy of categories as:

1. Exempted - very low risk
2. Reported <= 10kg - low risk
3. Reported - low risk
4. Assessed - medium to high risk

When all is working correctly and unit tests are passing this ticket will be closed.

Rules

For REPORTED10KG category, the software must ensure:

Not (known) mutagenic or

Not (known) carcinogenic or

Not (known) reprotoxic or

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.

If used in a cosmetic, must not be prohibited or restricted in cosmetics by EU or USA

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

and

Not (known to be) a solid or a dispersion or

Physical state of 'Unknown' is already treated by the software as equivalent with 'Solid' and/or 'Dispersion' for nanoscale processing. See Ticket #30.

Not (known) to be nanoscale

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 28#comment:3 which implements this.

and

Not (known) to contain Fluorine or

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.

IS known to be an inorganic salt

We already have element detection methods and organic/inorganic detection. See Ticket #33

and

Not (known) Persistent, Bioaccumulative and ToxicT

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 #37

Section 42A (relaxes rigour by using the word "reasonably")

Identification is identical with all other introductions. The difference is relaxed rigour in providing it - or not, if "reasonably practicable" to find out only when asked.

We will not need the MOU. Introducer can merely keep contact details of the person reasonably believed to know the information to provide to the Executive Director on request.

Section 46 - record keeping

We only need a useful link pointing to the AICIS record keeping checklist for REPORTED10KG. See Ticket #38

Section 56A - specific records to retain

A relaxed rigour around the actual name of the chemical. Just retain the "known" names.

However, there is NO relaxed rigour around knowing the product names and chemical volumes introduced. See also Ticket #38.

We will need to review the Introduction Report to adjust output based on REPORTED10KG. See Ticket #39

[Mike Dewhirst]

All sub-tickets of this ticket are now closed and so this ticket is now complete.