Team:Costa Rica-TEC-UNA/Safety

From 2012.igem.org

(Difference between revisions)
 
(6 intermediate revisions not shown)
Line 1: Line 1:
-
{| style="color:#000000;background-color:#D4EBF9;" cellpadding="2" cellspacing="2" border="1" bordercolor="#fff" width="90%" align="center"
+
__NOTOC__
-
!align="center"|[[Team:Costa_Rica-TEC-UNA|Home]]
+
<html>
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Team|Team]]
+
<html xmlns="http://www.w3.org/1999/xhtml">
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Project|Project]]
+
<script language="javascript" type="text/javascript">
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Parts|Parts Submitted to the Registry]]
+
// Copyright 2006-2007 javascript-array.com
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Modeling|Modeling]]
+
 
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Notebook|Notebook]]
+
var timeout = 500;
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Safety|Safety]]
+
var closetimer = 0;
-
!align="center"|[[Team:Costa_Rica-TEC-UNA/Attributions|Attributions]]
+
var ddmenuitem = 0;
-
!align="center"|[https://igem.org/Team.cgi?year=2012&team_name=Costa_Rica-TEC-UNA Official Team Profile]
+
 
-
|}
+
// open hidden layer
 +
function mopen(id)
 +
{
 +
// cancel close timer
 +
mcancelclosetime();
 +
 
 +
// close old layer
 +
if(ddmenuitem) ddmenuitem.style.visibility = 'hidden';
 +
 
 +
// get new layer and show it
 +
ddmenuitem = document.getElementById(id);
 +
ddmenuitem.style.visibility = 'visible';
 +
 
 +
}
 +
// close showed layer
 +
function mclose()
 +
{
 +
if(ddmenuitem) ddmenuitem.style.visibility = 'hidden';
 +
}
 +
 
 +
// go close timer
 +
function mclosetime()
 +
{
 +
closetimer = window.setTimeout(mclose, timeout);
 +
}
 +
 
 +
// cancel close timer
 +
function mcancelclosetime()
 +
{
 +
if(closetimer)
 +
{
 +
window.clearTimeout(closetimer);
 +
closetimer = null;
 +
}
 +
}
 +
 
 +
// close layer when click-out
 +
document.onclick = mclose;
 +
</script>
 +
 
 +
<style type="text/css">
 +
#sddm
 +
{      margin: 0;
 +
padding: 0;
 +
z-index: 30}
 +
 
 +
#sddm li
 +
{ margin: 0;
 +
padding: 0;
 +
list-style: none;
 +
float: left;
 +
font: bold 11px arial}
 +
 
 +
#sddm li a
 +
{ display: block;
 +
margin: 0 1px 0 0;
 +
padding: 4px 10px;
 +
width: 60px;
 +
background: #147AFF;
 +
color: #FFF;
 +
text-align: center;
 +
text-decoration: none}
 +
 
 +
#sddm li a:hover
 +
{ background: #49A3FF}
 +
 
 +
#sddm div
 +
{ position: absolute;
 +
visibility: hidden;
 +
margin: 0;
 +
padding: 0;
 +
background: #EAEBD8;
 +
border: 1px solid #5970B2}
 +
 
 +
#sddm div a
 +
{ position: relative;
 +
display: block;
 +
margin: 0;
 +
padding: 5px 10px;
 +
width: auto;
 +
white-space: nowrap;
 +
text-align: left;
 +
text-decoration: none;
 +
background: #FFFFFF;
 +
color: #000000;
 +
font: 11px arial}
 +
 
 +
#sddm div a:hover
 +
{ background: #3366D5;
 +
color: #000000}
 +
 
 +
 
 +
body {
 +
margin: 0;
 +
padding: 0;
 +
font-family: seriff;
 +
font-size: 13px;
 +
background-color: #FFFFFF
 +
        }
 +
</style>
 +
 
 +
<head>
 +
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 +
</head>
 +
<body>
 +
<ul id="sddm">
 +
    <li><a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA">Home</a></li>
 +
    <li><a href="#"  
 +
        onmouseover="mopen('m1')"  
 +
        onmouseout="mclosetime()">Team</a>
 +
        <div id="m1"  
 +
            onmouseover="mcancelclosetime()"
 +
            onmouseout="mclosetime()">
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Team">Team Members and Advisors</a>
 +
        </div>
 +
    </li>
 +
    <li><a href="#"  
 +
        onmouseover="mopen('m2')"
 +
        onmouseout="mclosetime()">Project</a>
 +
        <div id="m2"
 +
            onmouseover="mcancelclosetime()"
 +
            onmouseout="mclosetime()">
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Project">Description</a>
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Notebook">Notebook</a>
 +
        </div>
 +
    </li>
 +
    <li><a href="#"  
 +
        onmouseover="mopen('m3')"
 +
        onmouseout="mclosetime()">Biobricks</a>
 +
        <div id="m3"
 +
            onmouseover="mcancelclosetime()"
 +
            onmouseout="mclosetime()">
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Parts">Parts Submitted to the registry</a>
 +
        </div>
 +
    </li>
 +
    <li><a href="#"  
 +
        onmouseover="mopen('m4')"
 +
        onmouseout="mclosetime()">Others</a>
 +
        <div id="m4"  
 +
            onmouseover="mcancelclosetime()"
 +
            onmouseout="mclosetime()">
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Safety">Safety</a>
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Attributions">Attributions</a>
 +
        <a href="https://2012.igem.org/Team:Costa_Rica-TEC-UNA/Human Practice">Human Practice</a>
 +
        <a href="https://igem.org/Team.cgi?year=2012&team_name=Costa_Rica-TEC-UNA">Official team profile</a>
 +
 
 +
        </div>
 +
    </li>
 +
</ul>
 +
<br/>
 +
</body>
 +
</html>
<!--
<!--
Line 18: Line 169:
-->
-->
-
'''1.Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?'''  
+
<p align="justify">'''1.Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?''' </p>
-
No, our project doesn't raise any safety issue in terms of public or enviromental safety. In terms of researcher safety, there is a low individual risk, because our team is using parts that come from ''Pseudomona cepacia'' and ''Acinetobacter'' sp. both from risk group 2, as well as other parts from the ''B. subtilis'' and ''Rhodococcus rhodochrous'' from risk group 1 and parts from bacteriophages. Our team is also using ''Rhodococcus opacus'' and ''Escherichia coli'', from risk group 1.  
+
<p align="justify">No, our project doesn't raise any safety issue in terms of public or enviromental safety. In terms of researcher safety, there is a low individual risk, because our team is using parts that come from ''Pseudomona cepacia'' and ''Acinetobacter'' sp. both from risk group 2, as well as other parts from the ''B. subtilis'' and ''Rhodococcus rhodochrous'' from risk group 1 and parts from bacteriophages. Our team is also using ''Rhodococcus opacus'' and ''Escherichia coli'', from risk group 1. </p>
-
'''2.Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues?'''  
+
<p align="justify">'''2.Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues?''' </p>
-
No, they don't.
+
<p align="justify">No, they don't. </p>
-
'''3.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? If no, which specific biosafety rules or guidelines do you have to consider in your country?'''
+
<p align="justify">'''3.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? If no, which specific biosafety rules or guidelines do you have to consider in your country?'''</p>
-
Costa Rican Laboratories are regulated by the Ministry of Health and Universities. They both make no difference in normal microorganism and GM microorganism since they are contained used. Regulations such as Cartagena Protocol do not apply because of the contained used. Environmental Regulations are still not in place, but once in place they will ask for a registry at CONAGEBio an environmental office for biodiversity.  Customs ask for a letter from Ministry of Health in order to release the GM microorganism. The Universities need to explain to the Ministry of Health the used of the GM microorganism.
+
<p align="justify">Costa Rican Laboratories are regulated by the Ministry of Health and Universities. They both make no difference in normal microorganism and GM microorganism since they are contained used, which is why Regulations such as Cartagena Protocol do not apply. Environmental Regulations are still not in place, but once in place they will ask for a registry at CONAGEBio, an environmental office for biodiversity.  Customs ask for a letter from Ministry of Health in order to release the GM microorganism. The Universities need to explain to the Ministry of Health the used of the GM microorganism.</p>
-
'''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?'''
+
<p align="justify">'''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?'''</p>
-
First of all, knowing the microorganism you're working with is essential, so it is important to inform yourselves if that MO has been used before on field work, so that we can have some references of it's behaviour.  
+
<p align="justify">First of all, knowing the microorganism you're working with is essential, so it is important to inform yourselves if that MO has been used before on field work, so that we can have some references of it's behaviour. Some times, if there's no documentation on the microorganism you'll be working with, doing a preliminary risk  assessment would be incredibly useful. Also, there should be some containment measures and a restricted area destined to work with constructs and gene insertions. Of course, the small things are important too, so keeping a perfect record of all the work done on the project is a must. That way it would be easier to react in any case it is needed. Contacting your country's biosafety commitee to get a review of your project is a good idea too.</p>
-
Some times, if there's no documentation on the microorganism you'll be working with, doing a preliminary risk  assessment would be incredibly useful. Also, there should be some containment measures and a restricted area destined to work with constructs and gene insertions. Of course, the small things are important too, so keeping a perfect record of all the work done on the project is a must. That way it would be easier to react in any case it is needed.
+
-
Contacting your country's biosafety commitee to get a review of your project is a good idea too.
+

Latest revision as of 02:54, 27 September 2012



1.Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?

No, our project doesn't raise any safety issue in terms of public or enviromental safety. In terms of researcher safety, there is a low individual risk, because our team is using parts that come from Pseudomona cepacia and Acinetobacter sp. both from risk group 2, as well as other parts from the B. subtilis and Rhodococcus rhodochrous from risk group 1 and parts from bacteriophages. Our team is also using Rhodococcus opacus and Escherichia coli, from risk group 1.

2.Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues?

No, they don't.

3.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? If no, which specific biosafety rules or guidelines do you have to consider in your country?

Costa Rican Laboratories are regulated by the Ministry of Health and Universities. They both make no difference in normal microorganism and GM microorganism since they are contained used, which is why Regulations such as Cartagena Protocol do not apply. Environmental Regulations are still not in place, but once in place they will ask for a registry at CONAGEBio, an environmental office for biodiversity. Customs ask for a letter from Ministry of Health in order to release the GM microorganism. The Universities need to explain to the Ministry of Health the used of the GM microorganism.

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?

First of all, knowing the microorganism you're working with is essential, so it is important to inform yourselves if that MO has been used before on field work, so that we can have some references of it's behaviour. Some times, if there's no documentation on the microorganism you'll be working with, doing a preliminary risk assessment would be incredibly useful. Also, there should be some containment measures and a restricted area destined to work with constructs and gene insertions. Of course, the small things are important too, so keeping a perfect record of all the work done on the project is a must. That way it would be easier to react in any case it is needed. Contacting your country's biosafety commitee to get a review of your project is a good idea too.

Retrieved from "http://2012.igem.org/Team:Costa_Rica-TEC-UNA/Safety"