21.01.2015 Views

Soil Generic Assessment Criteria for Human Health Risk ... - ESdat

Soil Generic Assessment Criteria for Human Health Risk ... - ESdat

Soil Generic Assessment Criteria for Human Health Risk ... - ESdat

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

www.esdat.net Esdat Environmental Database Management Software +61 2 8875 7948<br />

2.2.1<br />

What the EIC/AGS/CL:AIRE GAC are<br />

The Environment Agency of England and Wales guidance describes what SGV are and are not. These definitions<br />

apply equally to the EIC/AGS/CL:AIRE GAC and are summarised in Box 1.<br />

Box 1. What the EIC/AGS/CL:AIRE GAC are/are not<br />

Definition of what EIC/AGS/CL:AIRE GAC are:<br />

• They are scientifically based screening criteria that have been derived using the CLEA model (v1.06)<br />

in general 2 accordance with the CLEA framework;<br />

• They can be used as a starting point <strong>for</strong> evaluating long-term risks to human health from chemicals<br />

in soil; and<br />

• They provide an indication of the chemical concentration in soil below which the long-term human<br />

health risks <strong>for</strong> site occupants (<strong>for</strong> various generic land-use scenarios) are considered to be tolerable<br />

or minimal<br />

• They are screening criteria to determine the need <strong>for</strong> further investigations and the need <strong>for</strong> a<br />

DQRA.<br />

Definition and Use<br />

Definition of what EIC/AGS/CL:AIRE GAC are NOT:<br />

• They do not represent the “trigger” <strong>for</strong> unacceptable intake, i.e. exceedence of the GAC does not<br />

necessarily imply significant possibility of significant harm (SPOSH);<br />

• They do not cover other types of risk to humans such as fire, suffocation or explosion, risks from<br />

chemicals in groundwater or ground gas or short term and acute exposures;<br />

• They cannot be used to evaluate risks to construction workers or non-human receptors; and<br />

• They are not explicitly derived to define remediation standards.<br />

2.2.2<br />

How the EIC/AGS/CL:AIRE GAC should be used<br />

Like the SGV, the EIC/AGS/CL:AIRE GAC have been derived based on generic conceptual site models <strong>for</strong> a number<br />

of land-uses and making generic assumptions about receptor type and behaviour and building and soil properties.<br />

These generic assumptions must be considered in the context of the conceptual site model to determine whether<br />

the GAC are an appropriate tool <strong>for</strong> assessing risks at the site under consideration. The practitioner should<br />

familiarise themselves with the suite of CLEA framework documents in order to understand these assumptions and<br />

the methodology used <strong>for</strong> deriving GAC. In particular, the assessor should consider the following:<br />

• Are there potential pollutant linkages present that the GAC do not consider, e.g. risk to workers<br />

in excavations, inhalation of vapours generated from contaminants in groundwater, diffusion of<br />

contaminants through drinking water pipes The presence of such pollutant linkages does not<br />

preclude the use of GAC, but the assessor should recognise that the use of GAC alone will not<br />

assess all the potential risks at the site;<br />

2 Unlike the SGVs the EIC/AGS/CL:AIRE GAC are not in strict accordance with the CLEA framework. For example, the CLEA SR2 document<br />

recommends the use of an expert toxicologist to review the health criteria from expert review groups and to challenge these criteria where appropriate.<br />

Although the EIC/AGS/CL:AIRE GAC project volunteers were all experienced human health risk assessors none were qualified toxicologists and thus the<br />

HCV have been derived on the basis of available health criteria and guidance provided in the SR2 document.<br />

7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!