Team:Virginia/Safety

From 2012.igem.org

(Difference between revisions)
m
 
(17 intermediate revisions not shown)
Line 1: Line 1:
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
<html>
-
!align="center"|[[Team:Virginia|Home]]
+
<head>
-
!align="center"|[[Team:Virginia/Team|Team]]
+
<!-- wiki hacks -->
-
!align="center"|[https://igem.org/Team.cgi?year=2012&team_name=Virginia Official Team Profile]
+
<style type="text/css">
-
!align="center"|[[Team:Virginia/Project|Project]]
+
#globalwrapper {
-
!align="center"|[[Team:Virginia/Parts|Parts Submitted to the Registry]]
+
    width:975px;
-
!align="center"|[[Team:Virginia/Modeling|Modeling]]
+
    padding:20px 0px;
-
!align="center"|[[Team:Virginia/Notebook|Notebook]]
+
    margin: 0 auto;
-
!align="center"|[[Team:Virginia/Safety|Safety]]
+
    background-color:#ffffff;
-
!align="center"|[[Team:Virginia/Attributions|Attributions]]
+
    height:100%;
-
|}
+
}
 +
.firstHeading {
 +
    height:0px;
 +
    visibility:hidden;
 +
}
 +
#footer-box{
 +
height:0px;
 +
    visibility:hidden;
 +
}
-
Use this page to answer the questions on the [[Safety | safety page]].
+
img.centering {  display: block;  margin-left: auto;  margin-right: auto; }
 +
 
 +
img
 +
{
 +
/* For IE8 and earlier */
 +
margin:0px auto;
 +
}
 +
img:hover
 +
{
 +
/* For IE8 and earlier */
 +
margin:0px auto;
 +
}
 +
 
 +
 
 +
body {
 +
    background-color: rgba(235,255,255, 1);
 +
   
 +
   
 +
   
 +
}
 +
#p-logo {
 +
    height:1px; overflow:hidden; display: none;
 +
}
 +
#top-section {
 +
 
 +
    background-repeat: no-repeat;
 +
    border-width:0px;
 +
    border-top-width:1px;
 +
 
 +
}
 +
 
 +
 
 +
#search-controls {
 +
height:0px;
 +
    visibility:hidden;
 +
}
 +
 
 +
#catlinks {
 +
visibility:hidden;
 +
}
 +
#content {
 +
background-color: rgba(255, 255, 255, 0);
 +
border-left:none;
 +
border-right:none;
 +
}
 +
 
 +
 
 +
 
 +
#navbar
 +
ul.navbar {
 +
float:left;
 +
width:100%;
 +
padding:0;
 +
margin:0;
 +
list-style-type:none;
 +
}
 +
 
 +
ul.navbar a {
 +
float:left;
 +
text-align:center;
 +
width:7em;
 +
text-decoration:none;
 +
color:white;
 +
background-color:#1A2B32;
 +
padding:0.2em 0.6em;
 +
border-right:1px solid white;
 +
}
 +
ul.navbar a:hover {background-color:#A3ABAE;}
 +
ul.navbar li {display:inline;}
 +
 
 +
#long {
 +
width:10em;
 +
}
 +
 
 +
#menubar li {visibility: hidden;
 +
}
 +
#menubar li a:hover{visibility: hidden;}
 +
 
 +
.navbar {
 +
padding:2 10px;
 +
}
 +
 
 +
 
 +
#float_corner {
 +
z-index:4000;
 +
position:fixed;_position:absolute;top:0px;  display: block;  margin-left: auto;  margin-right: auto;  clip:
 +
inherit;_top:expression(document.documentElement.scrollTop+document.documentElement.clientHeight-this.clientHeight);_left:expression(document.documentElement.scrollLeft + document.documentElement.clientWidth - offsetWidth);}
 +
 
 +
navig{position:fixed; top:12px; left:12px; right:12px; z-index:3000; min-width:450px;
 +
background:url("") top left  no-repeat;
 +
background-position: 20px 0px;
 +
display: inline;
 +
float: left;
 +
height: 50px;
 +
margin-bottom: 0;
 +
 
 +
background-color:rgba(120,154,161,0.6);
 +
height:48px;
 +
/* Firefox v1.0+ */
 +
-moz-border-radius:12px ;
 +
/* Safari v3.0+ and by Chrome v0.2+ */
 +
-webkit-border-radius:12px ;
 +
/* Firefox v4.0+ , Safari v5.0+ , Chrome v4.0+ , Opera v10.5+  and by IE v9.0+ */
 +
border-radius:12px ;
 +
/* Firefox v3.5+ */
 +
-moz-box-shadow:0px 7px 15px rgb(0,0,0) ,inset 0px 0px 11px rgba(0,0,0,0.59);
 +
/* Safari v3.0+ and by Chrome v0.2+ */
 +
-webkit-box-shadow:0px 7px 15px rgb(0,0,0) ,inset 0px 0px 11px rgba(0,0,0,0.59);
 +
/* Firefox v4.0+ , Safari v5.1+ , Chrome v10.0+, IE v10+ and by Opera v10.5+ */
 +
box-shadow:0px 7px 15px rgb(0,0,0) ,inset 0px 0px 11px rgba(0,0,0,0.59);
 +
-ms-filter:"progid:DXImageTransform.Microsoft.dropshadow(OffX=0,OffY=7,Color=#c9000000,Positive=true)";
 +
filter:progid:DXImageTransform.Microsoft.dropshadow(OffX=0,OffY=7,Color=#c9000000,Positive=true);
 +
 
 +
 
 +
 
 +
}
 +
 
 +
/* begin css tabs */
 +
 
 +
ul#tabnav { /* general settings */
 +
text-align: center; /* set to left, right or center */
 +
margin: 1em 0 1em 0; /* set margins as desired */
 +
font: bold 13px verdana, arial, sans-serif; /* set font as desired */
 +
color:#a1787f;
 +
border-bottom: 0px solid #6c6; /* set border COLOR as desired */
 +
list-style-type: none;
 +
padding: 3px 10px 3px 10px; /* THIRD number must change with respect to padding-top (X) below */
 +
position:fixed; top:0px;  z-index:3000;
 +
width: 950px;
 +
margin-left: auto;    margin-right: auto;
 +
}
 +
 
 +
ul#tabnav li { /* do not change */
 +
display: inline;
 +
}
 +
 
 +
body#tab1 li.tab1, body#tab2 li.tab2, body#tab3 li.tab3, body#tab4 li.tab4 { /* settings for selected tab */
 +
border-bottom: 1px solid #fff; /* set border color to page background color */
 +
background-color: #fff; /* set background color to match above border color */
 +
}
 +
 
 +
body#tab1 li.tab1 a, body#tab2 li.tab2 a, body#tab3 li.tab3 a, body#tab4 li.tab4 a { /* settings for selected tab link */
 +
background-color: #fff; /* set selected tab background color as desired */
 +
color: #000; /* set selected tab link color as desired */
 +
position:relative;
 +
top: 1px;
 +
padding-top: 2px; /* must change with respect to padding (X) above and below */
 +
}
 +
 
 +
ul#tabnav li a { /* settings for all tab links */
 +
padding: 4px 6px; /* set padding (tab size) as desired; FIRST number must change with respect to padding-top (X) above */
 +
/*border: 1px solid #6c6; set border COLOR as desired; usually matches border color specified in #tabnav */
 +
 
 +
background-color:rgba(74,92,97, 0);
 +
color: #000000;
 +
 
 +
 
 +
 
 +
/*background-color: #cfc;  set unselected tab background color as desired */
 +
color: #000000; /* set unselected tab link color as desired */
 +
margin-right: 15px; /* set additional spacing between tabs as desired */
 +
text-decoration: none;
 +
border-bottom: none;
 +
}
 +
 
 +
ul#tabnav a:hover { /* settings for hover effect */
 +
background-color:rgba(255,255,255, 0);
 +
color: #000000;
 +
background-image: -moz-radial-gradient(50% 50%, ellipse cover, rgba(255,255,255, 0.8), rgba(74,92,97, 0) 100%);
 +
background-image: -webkit-radial-gradient(50% 50%, ellipse cover, rgba(255,255,255, 0.8), rgba(74,92,97, 0) 100%);
 +
background-image: -o-radial-gradient(50% 50%, ellipse cover, rgba(255,255,255, 0.8), rgba(74,92,97, 0) 100%);
 +
background-image: -ms-radial-gradient(50% 50%, ellipse cover, rgba(255,255,255, 0.8), rgba(74,92,97, 0) 100%);
 +
background-image: radial-gradient(50% 50%, ellipse cover, rgba(255,255,255, 0.8), rgba(74,92,97, 0) 100%)
 +
}
 +
</style>
 +
<script type="text/javascript">
 +
 
 +
  var _gaq = _gaq || [];
 +
  _gaq.push(['_setAccount', 'UA-32492100-1']);
 +
  _gaq.push(['_trackPageview']);
 +
 
 +
  (function() {
 +
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
 +
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
 +
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
 +
  })();
 +
 
 +
 
 +
 
 +
</script>
 +
</head>
 +
 
 +
<body>
 +
 
 +
 
 +
<navig><ul id="tabnav">
 +
 +
 +
 +
<li class="tab2"><a href="/Team:Virginia/Project">Project</a></li>
 +
<li class="tab4"><a href="/Team:Virginia/Parts">Parts</a></li>
 +
        <li class="tab8"><a href="/Team:Virginia/Team">Team</a></li>
 +
<li class="tab9"><a href="/Team:Virginia/Practices">Practices</a></li>
 +
<li class="tab5"><a href="/Team:Virginia">
 +
&nbsp;&nbsp;<img src="https://static.igem.org/mediawiki/2012/b/b8/Igemlogo.fw.png" border="0"/>&nbsp;&nbsp;</a></li>
 +
 
 +
<li class="tab3"><a href="/Team:Virginia/Modeling">Modeling</a></li>
 +
<li class="tab6"><a href="http://openwetware.org/wiki/IGEM:Virginia_2012">Notebook</a></li>
 +
<li class="tab7"><a href="/Team:Virginia/Safety">Safety</a></li>
 +
<li class="tab7"><a href="/Team:Virginia/Attributions">Attributions</a></li>
 +
</ul></navig>
 +
</p><p><br />
 +
 
 +
<div>
 +
 
 +
<p><br />
 +
 
 +
<tr><td rowspan="3">
 +
<p><ul>
 +
<h1> <span class="mw-headline" id="Safety"> <b>Safety</b> </span></h1><br/>
 +
<b>Would any of your project ideas raise safety issues in terms of:</b></li><br/><br/><UL><b>
 +
Researcher safety?</b><UL><li>
 +
Because some standard lab materials were hazardous, we carefully followed all safety precautions regarding their handling and use. Specifically, we used dedicated containers for agarose gels containing ethidium bromide, worked in a fume hood when handling mercapethanol, wore protective gear when using UV light for gel excision, disposed of sharps in sharps waste, and wore gloves at all times in the lab.<li>
 +
All team members satisfactorily completed online biosafety training for performing BSL2 work (http://ehs.virginia.edu/biosafety/bio.training.html) before working in lab, and most team members took our spring semester course on synthetic biology, which included biosafety orientation. At least two people were in lab to ensure safety whenever a procedure was being performed, and most work was done in the presence of the grad students and post-docs with whom we shared the lab.</li><li>
 +
We performed our project in a BSL2-certified lab. We used standard lab strains of <i>E. coli</i>, <i>B. bronchiseptica</i>, T7 phage, and BPP phase-locked phage in accordance with our host lab’s safety practices. The majority of our work was at BSL1, and experiments using <i>B. pertussis</i> were conducted within a collaborating BSL2-certified lab that specifically works with the strain.</li><li>
 +
All biological waste was disposed of in containers for contaminated waste and subsequently removed by a licensed waste contractor.</li></UL><br/>
 +
<b>Public safety?</b><UL><li>
 +
We do not anticipate any threat to public safety. None of our modifications impact virulence, and our reporter gene is non-toxic.</li></UL><br/>
 +
<b>Environmental safety?</b><UL><li>
 +
We do not anticipate any threat to environmental safety from our project. None of our organisms or constructs have any known environmental impacts, all were physically contained using safe lab techniques, and our lab strains are unlikely to be competitive outside the lab.</li></UL></UL><br/>
 +
<b>Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues?</b><UL><li>
 +
We do not foresee any safety issues raised by our BioBrick parts or devices this year. None of our constructs code for human toxins or have any predicted environmental interactions, although chronic internal overexposure of our reporter may be harmful. The diagnostic procedure we envision would not involve exposing humans to engineered organisms or gene products.</li><li>
 +
We plan to submit phage lysins as BioBricks. Lysins specifically lyse bacterial cells, and would not affect eukaryotes.</li></UL><br/>
 +
<b>Is there a local biosafety group, committee, or review board at your institution?
 +
If yes, what does your local biosafety group think about your project?</b><UL><li>
 +
Our project was approved and overseen by multiple faculty members and performed in an active faculty lab which is directly responsible to our local EHS. All team members satisfactorily completed our local biosafety group’s online training course.</li><br/></UL>
 +
<b>Do you have any other ideas how to deal with safety issues that could be useful for future iGEM competitions? How could parts, devices and systems be made even safer through biosafety engineering?</b><UL><li>
 +
When constructs are predicted to have consequences if released, engineers should use multiple containment strategies in combination, such as physical containment, nutritional containment, orthogonality, and kill-switches.</li><li>
 +
Before synthesis or assembly, protein-coding genes should be screened through protein-protein interaction databases for potential non-intuitive interactions, especially if planned for environmental release.</li><li>
 +
Tools for algorithmic or predictive assessment of the safety of synthetic constructs should be developed and deployed, rather than solely relying on self-reported/intuitive projections of synthetic construct safety.</li></UL>
 +
</tr></td>
 +
</p>

Latest revision as of 02:24, 27 October 2012



    Safety


    Would any of your project ideas raise safety issues in terms of:

      Researcher safety?
      • Because some standard lab materials were hazardous, we carefully followed all safety precautions regarding their handling and use. Specifically, we used dedicated containers for agarose gels containing ethidium bromide, worked in a fume hood when handling mercapethanol, wore protective gear when using UV light for gel excision, disposed of sharps in sharps waste, and wore gloves at all times in the lab.
      • All team members satisfactorily completed online biosafety training for performing BSL2 work (http://ehs.virginia.edu/biosafety/bio.training.html) before working in lab, and most team members took our spring semester course on synthetic biology, which included biosafety orientation. At least two people were in lab to ensure safety whenever a procedure was being performed, and most work was done in the presence of the grad students and post-docs with whom we shared the lab.
      • We performed our project in a BSL2-certified lab. We used standard lab strains of E. coli, B. bronchiseptica, T7 phage, and BPP phase-locked phage in accordance with our host lab’s safety practices. The majority of our work was at BSL1, and experiments using B. pertussis were conducted within a collaborating BSL2-certified lab that specifically works with the strain.
      • All biological waste was disposed of in containers for contaminated waste and subsequently removed by a licensed waste contractor.

      Public safety?
      • We do not anticipate any threat to public safety. None of our modifications impact virulence, and our reporter gene is non-toxic.

      Environmental safety?
      • We do not anticipate any threat to environmental safety from our project. None of our organisms or constructs have any known environmental impacts, all were physically contained using safe lab techniques, and our lab strains are unlikely to be competitive outside the lab.

    Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues?
    • We do not foresee any safety issues raised by our BioBrick parts or devices this year. None of our constructs code for human toxins or have any predicted environmental interactions, although chronic internal overexposure of our reporter may be harmful. The diagnostic procedure we envision would not involve exposing humans to engineered organisms or gene products.
    • We plan to submit phage lysins as BioBricks. Lysins specifically lyse bacterial cells, and would not affect eukaryotes.

    Is there a local biosafety group, committee, or review board at your institution? If yes, what does your local biosafety group think about your project?
    • Our project was approved and overseen by multiple faculty members and performed in an active faculty lab which is directly responsible to our local EHS. All team members satisfactorily completed our local biosafety group’s online training course.

    Do you have any other ideas how to deal with safety issues that could be useful for future iGEM competitions? How could parts, devices and systems be made even safer through biosafety engineering?
    • When constructs are predicted to have consequences if released, engineers should use multiple containment strategies in combination, such as physical containment, nutritional containment, orthogonality, and kill-switches.
    • Before synthesis or assembly, protein-coding genes should be screened through protein-protein interaction databases for potential non-intuitive interactions, especially if planned for environmental release.
    • Tools for algorithmic or predictive assessment of the safety of synthetic constructs should be developed and deployed, rather than solely relying on self-reported/intuitive projections of synthetic construct safety.