Team:RMIT Australia/Safety

From 2010.igem.org

(Difference between revisions)
(Prototype team page)
(→Safety Issues)
 
(25 intermediate revisions not shown)
Line 1: Line 1:
-
<!-- *** What falls between these lines is the Alert Box!  You can remove it from your pages once you have read and understood the alert *** -->
+
__NOTOC__
-
 
+
<html>
<html>
-
<div id="box" style="width: 700px; margin-left: 137px; padding: 5px; border: 3px solid #000; background-color: #fe2b33;">
+
<body style="background-color:#CCCCCC">
-
<div id="template" style="text-align: center; font-weight: bold; font-size: large; color: #f6f6f6; padding: 5px;">
+
 
-
This is a template page. READ THESE INSTRUCTIONS.
+
<style>
-
</div>
+
h1.firstHeading { display: none; }
-
<div id="instructions" style="text-align: center; font-weight: normal; font-size: small; color: #f6f6f6; padding: 5px;">
+
 
-
You are provided with this team page template with which to start the iGEM season.  You may choose to personalize it to fit your team but keep the same "look." Or you may choose to take your team wiki to a different level and design your own wiki. You can find some examples <a href="https://2008.igem.org/Help:Template/Examples">HERE</a>.
+
p {text-align: justify;}
-
</div>
+
 
-
<div id="warning" style="text-align: center; font-weight: bold; font-size: small; color: #f6f6f6; padding: 5px;">
+
a:link { color: #FF0000; text-decoration: none}
-
You <strong>MUST</strong> have a team description page, a project abstract, a complete project description, a lab notebook, and a safety page. PLEASE keep all of your pages within your teams namespace.
+
a:visited { color:#FF0000; text-decoration: none}
-
</div>
+
a:hover { color:#FF0000; text-decoration: none}
 +
a:active { color:#FF0000; text-decoration: none}
 +
 
 +
#bodyContent { padding: 10px auto; width: 910px; margin: auto; clear: none; }
 +
 
 +
table#team_members { text-align: justify; border: 0; }
 +
table#team_members h2, table#team_members h3 { clear: both; }
 +
 
 +
 
 +
/*-----------------------------------------------------------------------------------------------*/
 +
div.MenuBar ul li ul.DropDownMenu {
 +
  display: none; /* Hides all drop-down menus. */
 +
 
 +
}
 +
/*
 +
li:hover works in IE7 and FF2.
 +
a:hover works in IE6 and FF2.
 +
a:hover breaks li:hover in FF2.
 +
*/
 +
div.MenuBar ul li:hover ul.DropDownMenu li ul.SideMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a ul.SideMenu {
 +
  display: none; /* Hides all side menus. */
 +
}
 +
/*------------------------------------------------------------------------------------- Menu Bar */
 +
div.MenuBar {
 +
  font: arial, helvetica, sans-serif;
 +
  height: 30px;
 +
  width: 910px;
 +
  /*width: 100%*/
 +
  margin: 0;
 +
  border-top: 0;
 +
  border-right: 0;
 +
  border-left: 0;
 +
  padding: 0;
 +
  background: black;
 +
 
 +
}
 +
div.MenuBar ul {
 +
  font: arial, helvetica, sans-serif;
 +
  text-align: center;
 +
  list-style-type: none;
 +
  margin: 0.5em auto;
 +
  border: 0;
 +
  padding: 0;
 +
  background: black;
 +
}
 +
div.MenuBar ul li {
 +
  font: arial, helvetica, sans-serif;
 +
  display: block;
 +
  padding: 0;
 +
  margin: 0;
 +
  font-size: 1.3em;
 +
  float: left;
 +
  background: black;
 +
  text-align: center;
 +
  width: 107px;
 +
  position: relative; /* Sets the positioning context for each drop-down menu. */
 +
}
 +
 
 +
div.MenuBar ul li a {
 +
  font: arial, helvetica, sans-serif;
 +
  display: block;
 +
  background: black;
 +
  height: 22px; /* Keep height + padding-top + padding-bottom sync with the menu bar height. */
 +
  color: #ffffff;
 +
  padding-top: 4px;
 +
  padding-bottom: 4px;
 +
  padding-left: 1em; /* Sets the left space between top-level items. */
 +
  padding-right: 1em; /* Sets the right space between top-level items. */
 +
  text-decoration: none;
 +
}
 +
 
 +
/*------------------------------------------------------------------------------ Drop-Down Menus */
 +
div.MenuBar ul li:hover ul.DropDownMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu {
 +
  display: block;
 +
  width: 10em; /* Drop-down menu width.
 +
                  Use MenuTailor.css to customize. */
 +
  height: 1em;
 +
  padding: 1px; /* Sets the drop-down menu "effective border" width. */
 +
  position: absolute;
 +
  top: 23px; /* Places the drop-down menu under the menu bar.
 +
                Keep it sync with the menu bar height. */
 +
  left: 0; /* Aligns the drop-down menu to its top-level item. */
 +
  background-color: black; /* Selected item. */
 +
  color: #FFFFFF;
 +
 
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu li a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a {
 +
  width: 10em; /* Keep it sync with the drop-down menu width.
 +
                            Use MenuTailor.css to customize. */
 +
  height: 1em;
 +
  padding-left: 0;
 +
  padding-right: 0;
 +
  background-color: black; /* Selected item. */
 +
  color: #FFFFFF;
 +
}
 +
ul.DropDownMenu li a span {
 +
  display: block;
 +
  padding-left: 0.75em; /* Sets the left space of each drop-down menu item. */
 +
  padding-right: 0.25em; /* Sets the right space of each drop-down menu item. */
 +
  text-align: right; /* Aligns the >> symbol to the right. */
 +
}
 +
ul.DropDownMenu li a span span {
 +
  float: left; /* Aligns the text (back) to the left. */
 +
  font: 12px arial, helvetica, sans-serif; /* Required for IE55. */
 +
  height: 20px;
 +
  color: #FFFFFF;
 +
}
 +
/*----------------------------------------------------------------------------------- Side Menus */
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu {
 +
  display: block;
 +
  width: 11em; /* Side menu width.
 +
                  Use MenuTailor.css to customize. */
 +
  padding: 1px; /* Sets the side menu "effective border" width. */
 +
  position: absolute;
 +
  top: -1px; /* Aligns the side menu to its drop-down menu item.
 +
                Keep it sync with the side menu "effective border" width. */
 +
  left: 13em; /* Places the side menu to the right of the drop-down menu.
 +
                            Keep it sync with the drop-down menu width.
 +
                            Use MenuTailor.css to customize. */
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a {
 +
  width: 11em; /* Keep it sync with the side menu width.
 +
                            Use MenuTailor.css to customize. */
 +
  font: 12px arial, helvetica, sans-serif; /* Required for IE55. */
 +
  left: 13em; /* Places the side menu to the right of the drop-down menu.
 +
                            Keep it sync with the drop-down menu width.
 +
                            Use MenuTailor.css to customize. */
 +
}
 +
div.MenuBar ul li ul.DropDownMenu li ul.SideMenu li a span {
 +
  padding-left: 1.5em; /* Sets the left space of each side menu item. */
 +
  padding-right: 0.5em; /* Sets the right space of each side menu item. */
 +
  text-align: left;
 +
  font: 12px arial, helvetica, sans-serif; /* Required for IE55. */
 +
  left: 13em; /* Places the side menu to the right of the drop-down menu.
 +
                            Keep it sync with the drop-down menu width.
 +
                            Use MenuTailor.css to customize. */
 +
}
 +
/*----------------------------------------------------------------------------- Browser Specific */
 +
* html div.MenuBar ul li a {
 +
  float: left; /* Required for IE55 and IE6.
 +
                            Breaks O9.
 +
                            Hidden (* html) from non-IE browsers. */
 +
}
 +
* html ul.DropDownMenu li a:hover {
 +
  cursor: hand; /* Required for IE55.
 +
                  Hidden (* html) from non-IE browsers. */
 +
}
 +
ul.DropDownMenu li a:hover {
 +
  cursor: pointer; /* Required for IE6 and IE7.
 +
                      Hidding it (* html) from non-IE browsers breaks IE7!
 +
}
 +
* html div.MenuBar a:hover {
 +
  text-decoration: none; /* Required for IE55 and IE6.
 +
                            Hidden (* html) from non-IE browsers. */
 +
}
 +
* html div.MenuBar ul li table,
 +
* html div.MenuBar ul li table td {
 +
  border: 0; /* Required for IE55 and IE6.
 +
                Hidden (* html) from non-IE browsers. */
 +
}
 +
/*------------------------------------------------------------------------------- Default Colors */
 +
div.MenuBar {
 +
  background-color: Menu;
 +
  border-bottom: 1px solid ButtonShadow;
 +
}
 +
div.MenuBar a {
 +
  background-color: Menu; /* Top-level unselected items. */
 +
  color: MenuText;
 +
}
 +
div.MenuBar ul li:hover a,
 +
div.MenuBar ul li a:hover {
 +
  color: #ea7f16;
 +
  background-color: Highlight; /* Top-level selected item. */
 +
  color: HighlightText;
 +
}
 +
/*...............................................................................................*/
 +
div.MenuBar ul li:hover ul.DropDownMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu {
 +
  background-color: ButtonShadow; /* Sets the drop-down menu "effective border" color. */
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu li a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a {
 +
  background-color: Menu;  Drop-down menu unselected items.
 +
                            Sets the drop-down menu "effective background" color. */
 +
  color: MenuText;
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover {
 +
  background-color: Highlight; /* Drop-down menu selected item. */
 +
  color: HighlightText;
 +
}
 +
/*...............................................................................................*/
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu {
 +
  background-color: ButtonShadow; /* Sets the side menu "effective border" color. */
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a {
 +
  background-color: Menu; /* Side menu unselected items.
 +
                            Sets the side menu "effective background" color. */
 +
  color: MenuText;
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a:hover,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a:hover {
 +
  background-color: Highlight; /* Side menu selected item. */
 +
  color: HighlightText;
 +
}
 +
/*-----------------------------------------------------------------------------------------------*/
 +
/*Script-Free 3-Level Menu 1.2 Tailor
 +
  www.CesarDaniel.info
 +
/*-------------------------------------------------------------------------------------- General */
 +
body {
 +
  background: white;
 +
  color: black;
 +
  margin: 0;
 +
  border: 0;
 +
  padding: 0;
 +
}
 +
 
 +
 
 +
div.MenuBar {
 +
  font: 13px arial, helvetica, sans-serif;
 +
}
 +
div.MenuBar ul {
 +
  font: 13px arial, helvetica, sans-serif; /* Required for IE55. */
 +
}
 +
/*--------------------------------------------------------------------------------------- Colors */
 +
div.MenuBar {
 +
  background-color: black; /* Selected item. */
 +
  color: #FFFFFF;
 +
  border-bottom: 1px solid ButtonShadow;
 +
}
 +
div.MenuBar a,
 +
div.MenuBar ul li:hover ul.DropDownMenu li a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a,
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a {
 +
  background-color: black; /* Selected item. */
 +
  color: #FFFFFF;
 +
}
 +
div.MenuBar ul li:hover a,
 +
div.MenuBar ul li a:hover,
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover a,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover,
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu li a:hover,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu li a:hover {
 +
  background-color: #FF0000; /* Selected item. */
 +
  color: #FFFFFF;
 +
}
 +
div.MenuBar ul li:hover ul.DropDownMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu,
 +
div.MenuBar ul li:hover ul.DropDownMenu li:hover ul.SideMenu,
 +
div.MenuBar ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu {
 +
  background-color: ButtonShadow; /* Sets the drop-down and side menus "effective border" color. */
 +
}
 +
/*--------------------------------------------------------------------------------------- Widths */
 +
/*
 +
 
 +
/*
 +
Menu Bar 1
 +
Drop-Down Menu #2
 +
*/
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM4,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM4,
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM4 li a,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM4 li a {
 +
  width: 11em; /* Drop-down menu width. */
 +
}
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM5,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM5,
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu#MB1-DDM5 li a,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu#MB1-DDM5 li a {
 +
  width: 12em; /* Drop-down menu width. */
 +
}
 +
 
 +
/*...............................................................................................*/
 +
/*
 +
Menu Bar 1
 +
Drop-Down Menu #2
 +
Side Menu #1
 +
*/
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM1,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM1 {
 +
  left: 15.5em !important; /* Places the side menu to the right of the drop-down menu.
 +
                            Keep it sync with the drop-down menu width. */
 +
}
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM1,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM1,
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM1 li a,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM1 li a {
 +
  width: 10em; /* Side menu width. */
 +
}
 +
/*...............................................................................................*/
 +
/*
 +
Menu Bar 1
 +
Drop-Down Menu #2
 +
Side Menu #2
 +
*/
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM2,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM2 {
 +
  left: 15.5em !important; /* Places the side menu to the right of the drop-down menu.
 +
                            Keep it sync with the drop-down menu width. */
 +
}
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM2,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM2,
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM2 li a,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM2 li a {
 +
  width: 10em; /* Side menu width. */
 +
}
 +
/*...............................................................................................*/
 +
/*
 +
Menu Bar 1
 +
Drop-Down Menu #2
 +
Side Menu #3
 +
*/
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM3,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM3 {
 +
  left: 15.5em  !important; /* Places the side menu to the right of the drop-down menu.
 +
                            Keep it sync with the drop-down menu width. */
 +
}
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM3,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM3,
 +
div.MenuBar#navi ul li:hover ul.DropDownMenu li:hover ul.SideMenu#MB1-DDM2-SM3 li a,
 +
div.MenuBar#navi ul li a:hover ul.DropDownMenu li a:hover ul.SideMenu#MB1-DDM2-SM3 li a {
 +
  width: 10em; /* Side menu width. */
 +
}
 +
/*...............................................................................................*/
 +
 
 +
</style>
 +
 
 +
 
 +
<body>
 +
<div id="header"><img src="https://static.igem.org/mediawiki/2010/3/31/RMIT_logo.png" /></div>
 +
<div class='MenuBar' id="navi">
 +
<ul>
 +
<li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia" style="color: white">Home
 +
<!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
 +
<!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
</li>
 +
<li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Team" style="color: white">Team
 +
                        <!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
 +
                        <!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
</li>
 +
                <li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Project" style="color: white">Projects
 +
                        <!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
 +
<!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
 
 +
                  </li>
 +
    <li>
 +
 
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Parts" style="color: white">Parts
 +
                        <!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
 +
                        <!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
</li>
 +
<li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Modeling" style="color:white">Modelling
 +
                        <!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
 +
                        <!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
</li>
 +
<li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Notebook" style="color: white">Notebook
 +
                        <!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
                       
 +
 
 +
</li>
 +
              <li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Safety" style="color: white">Safety
 +
                        <!--[if gt IE 6]><!--></a><!--<![endif]-->
 +
<!--[if lt IE 7]><table border="0" cellpadding="0" cellspacing="0"><tr><td><![endif]-->
 +
        <!--[if lte IE 6]></td></tr></table></a><![endif]-->
 +
</li>
 +
 
 +
<li>
 +
<a href="https://2010.igem.org/Team:RMIT_Australia/Sponsors" style="color: white">Sponsors</a>
 +
</li>
 +
</ul>
 +
 
</div>
</div>
 +
<div id="header_bottom"><img src="https://static.igem.org/mediawiki/2008/e/ef/Navi_bg.gif" alt="" / ></div>
 +
</body>
</html>
</html>
-
<!-- *** End of the alert box *** -->
 
 +
==The Perceived Dangers Associated with Gene Technology and Creating Artificial Life==
 +
 +
With the rapid advances and the high impact of molecular biology in our lives, it is extremely important to be aware of the consequences science has on society and our environment. Scientists do most of their work in enclosed laboratories and following strict guidelines governed by regulatory bodies (in Australia the Office of the Gene Technology Regulator - OGTR). Though regulations dictate the containment of all genetically modified organisms (GMOs), there have been several cases in which GMO's have been unintentionally released.
 +
<p></p>
 +
For these reasons we were interested in collaborating with Penn State who undertook a survey on the perceptions of Synthetic Biology in society and the acceptance of GMO's in our everyday lives. Societal perceptions will continue to change as biotechnology increasing is rolled forward to deliver greater outcomes to mankind and such surveys are important benchmarks to these changes in perceptions and practices.
 +
<p></p>
 +
<p></p>
 +
The RMIT 2010 iGEM team is attempting to create a biological system that will produce therapeutic peptides at a low economic cost. A biological machine will be created that uses an inactivated thermostable polymerase as a carrier protein with an attached desired peptide - in our case a therapeutic peptide. There are several safety concerns when undergoing this project that we have addressed:
 +
<p></p>
 +
<p></p>
 +
Our project involves working with polymerases, which are proteins found in all living organisms and are involved in the process of DNA replication. More specifically Taq polymerase (found in the Archeon Thermus aquaticus), being a revolutionary enzyme in the field of molecular biology due to its thermostability, was the focus of our work. The immediate danger is a bacterium containing a Taq plasmid part escaping into the environment and altering the genetic material of many organisms. RMIT team has reduced these dangers by creating mutations that will not allow this protein to bind to DNA or undertake polymerase activity.
 +
<p></p>
 +
<p></p>
 +
 +
The chosen peptides that are being ligated with the Taq polymerase are Losartan and arginine vasopressin. Losartan is a peptide that reduces blood pressure as an antagonist of the angiotensin system. This peptide is safe if not ingested intentionally for harmful purposes as recognised by drug and therapeutic agencies world wide.
 +
<p></p>
 +
<p></p>
 +
 +
The second peptide is arginine vasopressin (AVP), commonly known as antidiuretic hormone. It is associated with water, glucose and salt regulation in the human body and, unlike Losartan, it increases blood pressure.
 +
<p></p>
 +
<p></p>
 +
 +
<p></p>
 +
<p></p>
 +
The bacteria used are Escherichia coli XL-1-Blue and NEB Turbo (High Efficiency), which are commercially available E.coli strain derived from E.coli K12 and used for routine and widespread molecular biology studies. Derivatives of K12 are avirulent and may be considered to be ACDP biological agents hazard group 1 because they have an established record of safety in the laboratory with no adverse effects on human, animal or plant health or the environment. Furthermore E.coli XL-1-Blue is incapable of survival outside the laboratory.
 +
 +
==Safety Issues==
 +
<p></p>
 +
<p></p>
 +
'''1. Would any of your project ideas raise safety issues in terms of: '''
 +
* '''researcher safety, '''
 +
* '''public safety, or '''
 +
* '''environmental safety? '''
 +
<p></p>
 +
<p></p>
 +
 +
No facet of our project would cause significant safety issues. All work is to be contained in PC2 labs. Processes carried out will be done so only after training is received and will be supervised by a skilled instructor to ensure the proper protocols are followed. Our labs will also diminish risks by avoiding the use of carcinogenic products like ethidium bromide, and instead use a more safe nucleic acid stain. This stain – GelStar - does not require UV light to be visualized but blue light, making it safer.
 +
The environment will be protected from contamination by waste products because any dangerous material will be disposed of in the correct container (e.g. biohazard containers for biological waste such as E. coli colonies), autoclaved and disposed of responsibly by the university. Team members will also be taught proper molecular biology skills and aseptic techniques.
 +
Public safety is ensured as no member of the public is permitted access within the PC2 labs unless approved by the university. Team members will follow proper PCR facility procedures like washing their hands with disinfectant before leaving the laboratory to avoid transmitting potentially harmful material to the public/environment.
 +
<p></p>
 +
<p></p>
 +
 +
'''2. Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues? If yes,
 +
o Did you document these issues in the Registry?
 +
o How did you manage to handle the safety issue?
 +
o How could other teams learn from your experience? '''
 +
<p></p>
 +
<p></p>
 +
 +
None of our newly engineered BioBrick parts raise safety issues. On the contrary, our system may actually help in reducing risk overall because if the platform works it will reduce the usage of chemicals associated with protein purification.
 +
<p></p>
 +
<p></p>
 +
 +
As previously stated as a safety measure the Taq polymerase part has been mutated in such a way that it will no longer bind to DNA. Through these mutations we eliminate its function and will just be a harmless globular protein in the cell. According to the MSDS, Taq polymerase does not produce any toxic compounds but may do so in the presence of strong oxidising agents/bases, degrade to form CO and CO2. In such an event, this side effect can be combated simply by ventilating the area.
 +
<p></p>
 +
<p></p>
 +
If a biopart, for example the modified Taq polymerase, mutated back to bind to E. coli DNA it might kill the cell. This however is unlikely.
 +
<p></p>
 +
<p></p>
-
{|align="justify"
+
'''3. Is there a local biosafety group, committee, or review board at your institution? '''
-
|You can write a background of your team here. Give us a background of your team, the members, etc.  Or tell us more about something of your choosing.
+
<p></p>
-
|[[Image:RMIT_Australia_logo.png|200px|right|frame]]
+
<p></p>
-
|-
+
-
|
+
-
''Tell us more about your project.  Give us background.  Use this is the abstract of your project.  Be descriptive but concise (1-2 paragraphs)''
+
-
|[[Image:RMIT_Australia_team.png|right|frame|Your team picture]]
+
-
|-
+
-
|
+
-
|align="center"|[[Team:RMIT_Australia | Team Example]]
+
-
|}
+
-
<!--- The Mission, Experiments --->
+
Yes. Our supervisor, Dr. Leonard Pattenden is on the biosafety committee. There was an internal requirement to complete a project risk assessment to cover all areas of the project. Our project has been deemed low risk. Additionally, our project required registration and was granted an “exempt dealing” by the Biosafety Commitee due to it's low risk, acting under Australian regulations from the Office of the Gene Technology Regulator (OGTR).
 +
<p></p>
 +
<p></p>
-
{| style="color:#1b2c8a;background-color:#0c6;" cellpadding="3" cellspacing="1" border="1" bordercolor="#fff" width="62%" align="center"
+
'''4. 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? '''
-
!align="center"|[[Team:RMIT_Australia|Home]]
+
<p></p>
-
!align="center"|[[Team:RMIT_Australia/Team|Team]]
+
<p></p>
-
!align="center"|[https://igem.org/Team.cgi?year=2010&team_name=RMIT_Australia Official Team Profile]
+
-
!align="center"|[[Team:RMIT_Australia/Project|Project]]
+
-
!align="center"|[[Team:RMIT_Australia/Parts|Parts Submitted to the Registry]]
+
-
!align="center"|[[Team:RMIT_Australia/Modeling|Modeling]]
+
-
!align="center"|[[Team:RMIT_Australia/Notebook|Notebook]]
+
-
!align="center"|[[Team:RMIT_Australia/Safety|Safety]]
+
-
|}
+
 +
Ideally, risk assessments should be conducted for each individual depending on their experience and expertise in handling the chemicals/organisms and carrying out the protocols. In addition, each student should write a risk assessment of the protocols employed to complete the project. This way all students will know and understand the risks of each experiment being done.
 +
<p></p>
 +
<p></p>
-
==Safety==
+
Knowledge is power: the more information known about a newly created part/device/system, the easier it is to identify and combat the associated risks. Greater recording of details and greater characterisation of parts in the registry would improve safety.
 +
<p></p>
 +
<p></p>
 +
'''5. Could there be an unplanned event or series of events involving your project, resulting in either death, injury, occupational illness, death, damage to equipment or property, or damage to the environment?'''
 +
<p></p>
 +
<p></p>
 +
Any time a person steps into a laboratory there is a risk of a serious emergency occurring. The likelihood of such an occurrence has been reduced due to the risk management techniques employed in the laboratory plus the oversight and training of students to comply with OHS best practice standards. Students are personally supervised at all times during iGEM work by an immediate project supervisor to reduce such events. It’s important to note however that risk assessments focus on the danger of the task as opposed to the skill level of the person carrying out the task (e.g. a postgraduate is less likely to injure themselves than an undergraduate). This means risk assessments on students need to be suitably adjusted. for our project a Project Risk assessment was completed for all students undertaking the work and students were educated in this practice and made to read MSDS and risk assessment documents before undertaking the work.
 +
<p></p>
 +
<p></p>
 +
'''6. Does your project require the exposure or release of the engineered organism to people or the environment (e.g. as medicine, for bioremediation)? '''
 +
<p></p>
 +
<p></p>
-
Please use this page to answer the safety questions posed on the [[Safety | safety page]].
+
This project involves the creation of new technology to produce peptides with high purity with a significantly lower cost. If the experiment is successful, the next step in this experiment would be testing the effect of these peptides in assays and perhaps in animal models. The bacterium itself would not be released or gene circuits, but the product created by it may and so would undergo standard FDA/other testing.

Latest revision as of 01:07, 28 October 2010


The Perceived Dangers Associated with Gene Technology and Creating Artificial Life

With the rapid advances and the high impact of molecular biology in our lives, it is extremely important to be aware of the consequences science has on society and our environment. Scientists do most of their work in enclosed laboratories and following strict guidelines governed by regulatory bodies (in Australia the Office of the Gene Technology Regulator - OGTR). Though regulations dictate the containment of all genetically modified organisms (GMOs), there have been several cases in which GMO's have been unintentionally released.

For these reasons we were interested in collaborating with Penn State who undertook a survey on the perceptions of Synthetic Biology in society and the acceptance of GMO's in our everyday lives. Societal perceptions will continue to change as biotechnology increasing is rolled forward to deliver greater outcomes to mankind and such surveys are important benchmarks to these changes in perceptions and practices.

The RMIT 2010 iGEM team is attempting to create a biological system that will produce therapeutic peptides at a low economic cost. A biological machine will be created that uses an inactivated thermostable polymerase as a carrier protein with an attached desired peptide - in our case a therapeutic peptide. There are several safety concerns when undergoing this project that we have addressed:

Our project involves working with polymerases, which are proteins found in all living organisms and are involved in the process of DNA replication. More specifically Taq polymerase (found in the Archeon Thermus aquaticus), being a revolutionary enzyme in the field of molecular biology due to its thermostability, was the focus of our work. The immediate danger is a bacterium containing a Taq plasmid part escaping into the environment and altering the genetic material of many organisms. RMIT team has reduced these dangers by creating mutations that will not allow this protein to bind to DNA or undertake polymerase activity.

The chosen peptides that are being ligated with the Taq polymerase are Losartan and arginine vasopressin. Losartan is a peptide that reduces blood pressure as an antagonist of the angiotensin system. This peptide is safe if not ingested intentionally for harmful purposes as recognised by drug and therapeutic agencies world wide.

The second peptide is arginine vasopressin (AVP), commonly known as antidiuretic hormone. It is associated with water, glucose and salt regulation in the human body and, unlike Losartan, it increases blood pressure.

The bacteria used are Escherichia coli XL-1-Blue and NEB Turbo (High Efficiency), which are commercially available E.coli strain derived from E.coli K12 and used for routine and widespread molecular biology studies. Derivatives of K12 are avirulent and may be considered to be ACDP biological agents hazard group 1 because they have an established record of safety in the laboratory with no adverse effects on human, animal or plant health or the environment. Furthermore E.coli XL-1-Blue is incapable of survival outside the laboratory.

Safety Issues

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

  • researcher safety,
  • public safety, or
  • environmental safety?

No facet of our project would cause significant safety issues. All work is to be contained in PC2 labs. Processes carried out will be done so only after training is received and will be supervised by a skilled instructor to ensure the proper protocols are followed. Our labs will also diminish risks by avoiding the use of carcinogenic products like ethidium bromide, and instead use a more safe nucleic acid stain. This stain – GelStar - does not require UV light to be visualized but blue light, making it safer. The environment will be protected from contamination by waste products because any dangerous material will be disposed of in the correct container (e.g. biohazard containers for biological waste such as E. coli colonies), autoclaved and disposed of responsibly by the university. Team members will also be taught proper molecular biology skills and aseptic techniques. Public safety is ensured as no member of the public is permitted access within the PC2 labs unless approved by the university. Team members will follow proper PCR facility procedures like washing their hands with disinfectant before leaving the laboratory to avoid transmitting potentially harmful material to the public/environment.

2. Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues? If yes, o Did you document these issues in the Registry? o How did you manage to handle the safety issue? o How could other teams learn from your experience?

None of our newly engineered BioBrick parts raise safety issues. On the contrary, our system may actually help in reducing risk overall because if the platform works it will reduce the usage of chemicals associated with protein purification.

As previously stated as a safety measure the Taq polymerase part has been mutated in such a way that it will no longer bind to DNA. Through these mutations we eliminate its function and will just be a harmless globular protein in the cell. According to the MSDS, Taq polymerase does not produce any toxic compounds but may do so in the presence of strong oxidising agents/bases, degrade to form CO and CO2. In such an event, this side effect can be combated simply by ventilating the area.

If a biopart, for example the modified Taq polymerase, mutated back to bind to E. coli DNA it might kill the cell. This however is unlikely.

3. Is there a local biosafety group, committee, or review board at your institution?

Yes. Our supervisor, Dr. Leonard Pattenden is on the biosafety committee. There was an internal requirement to complete a project risk assessment to cover all areas of the project. Our project has been deemed low risk. Additionally, our project required registration and was granted an “exempt dealing” by the Biosafety Commitee due to it's low risk, acting under Australian regulations from the Office of the Gene Technology Regulator (OGTR).

4. 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?

Ideally, risk assessments should be conducted for each individual depending on their experience and expertise in handling the chemicals/organisms and carrying out the protocols. In addition, each student should write a risk assessment of the protocols employed to complete the project. This way all students will know and understand the risks of each experiment being done.

Knowledge is power: the more information known about a newly created part/device/system, the easier it is to identify and combat the associated risks. Greater recording of details and greater characterisation of parts in the registry would improve safety.

5. Could there be an unplanned event or series of events involving your project, resulting in either death, injury, occupational illness, death, damage to equipment or property, or damage to the environment?

Any time a person steps into a laboratory there is a risk of a serious emergency occurring. The likelihood of such an occurrence has been reduced due to the risk management techniques employed in the laboratory plus the oversight and training of students to comply with OHS best practice standards. Students are personally supervised at all times during iGEM work by an immediate project supervisor to reduce such events. It’s important to note however that risk assessments focus on the danger of the task as opposed to the skill level of the person carrying out the task (e.g. a postgraduate is less likely to injure themselves than an undergraduate). This means risk assessments on students need to be suitably adjusted. for our project a Project Risk assessment was completed for all students undertaking the work and students were educated in this practice and made to read MSDS and risk assessment documents before undertaking the work.

6. Does your project require the exposure or release of the engineered organism to people or the environment (e.g. as medicine, for bioremediation)?

This project involves the creation of new technology to produce peptides with high purity with a significantly lower cost. If the experiment is successful, the next step in this experiment would be testing the effect of these peptides in assays and perhaps in animal models. The bacterium itself would not be released or gene circuits, but the product created by it may and so would undergo standard FDA/other testing.

Retrieved from "http://2010.igem.org/Team:RMIT_Australia/Safety"