Team:HIT-Harbin/Safety

From 2014.igem.org

(Difference between revisions)
 
(21 intermediate revisions not shown)
Line 4: Line 4:
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/style.css?action=raw&amp;ctype=text/css">
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/style.css?action=raw&amp;ctype=text/css">
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/contentstyle.css?action=raw&amp;ctype=text/css">
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/contentstyle.css?action=raw&amp;ctype=text/css">
 +
<link type="text/css" rel="stylesheet" media="screen" href="https://2014.igem.org/Team:HIT-Harbin/css/projectstyle.css?action=raw&amp;ctype=text/css">
<script type="text/javascript" src="https://2014.igem.org/Team:HIT-Harbin/js/main.js?action=raw&amp;ctype=text/javascript"></script>
<script type="text/javascript" src="https://2014.igem.org/Team:HIT-Harbin/js/main.js?action=raw&amp;ctype=text/javascript"></script>
<!--main content -->
<!--main content -->
Line 11: Line 12:
   <div id="nav">
   <div id="nav">
     <!--project -->
     <!--project -->
-
     <div id="project" class="nav1" onmouseover="displaySubMenu(this)" onmouseout="hideSubMenu(this)">                                    <a href="https://2014.igem.org/Team:HIT-Harbin/Project" name="top">Project</a>
+
     <div id="project" class="nav1" >                                     
 +
        <a href="https://2014.igem.org/Team:HIT-Harbin/Project" name="top">Project</a>
       <ul>
       <ul>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Design">Design</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Design">Design</a></li>
-
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/FutureWork">Advantages</a></li>
+
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Advantages">Advantages</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Modeling">Modeling</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Modeling">Modeling</a></li>
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Results">Results</a></li>
 
       </ul>  
       </ul>  
     </div>
     </div>
-
     <!--Judging-->
+
     <!--Safety-->
-
     <div id="judging" class="nav1" onmouseover="displaySubMenu(this)" onmouseout="hideSubMenu(this)"><a href="https://2014.igem.org/Team:HIT-Harbin/Judging">Judging</a>
+
     <div id="judging" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Safety"><span>Safety</span></a>
-
      <ul>
+
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Biobrick">Biobrick</a></li>
+
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Achievement">Achievement</a></li>
+
     </div>
     </div>
     <!--Wetlab-->
     <!--Wetlab-->
-
     <div id="wetlab" class="nav1" onmouseover="displaySubMenu(this)" onmouseout="hideSubMenu(this)"><a href="https://2014.igem.org/Team:HIT-Harbin/Wetlab"><span>Wetlab</span></a>
+
     <div id="wetlab" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Wetlab">Wetlab</a>
       <ul>
       <ul>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Protocols">Protocols</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Protocols">Protocols</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Notebook">Notebook</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Notebook">Notebook</a></li>
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Safety">Safety</a></li>
 
     </div>
     </div>
 +
    <!--kuang-->
 +
    <div class="nav1 home" ><a href="https://2014.igem.org/Team:HIT-Harbin"></a></div>
     <!--software-->
     <!--software-->
-
     <div id="software" class="nav1" onmouseover="displaySubMenu(this)" onmouseout="hideSubMenu(this)"><a href="https://2014.igem.org/Team:HIT-Harbin/Software">Software</a>
+
     <div id="software" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Software">Software</a>
     </div>
     </div>
     <!--Team -->
     <!--Team -->
-
     <div id="team" class="nav1" onmouseover="displaySubMenu(this)" onmouseout="hideSubMenu(this)"><a href="https://2014.igem.org/Team:HIT-Harbin/Team">Team</a>
+
     <div id="team" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Team">Team</a>
       <ul>
       <ul>
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Members">Members</a></li>
 
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Advisors">Advisors</a></li>
 
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Instructors">Instructors</a></li>
 
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li>
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li>
 +
        <li><a href="https://igem.org/Team.cgi">Profile</a></li>
       </ul>
       </ul>
     </div>
     </div>
     <!--humanPractices -->
     <!--humanPractices -->
-
     <div id="humanPractices" class="nav1" onmouseover="displaySubMenu(this)" onmouseout="hideSubMenu(this)"><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices">Human&nbsp;&nbsp;practices</a>
+
     <div id="humanPractices" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices">Human&nbsp;&nbsp;practices</a>
       <ul>
       <ul>
-
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Preliminary">Preliminary</a></li>
+
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices#Preliminary">Preliminary</a></li>
-
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Meetup">Meet Up</a></li>
+
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices#Meetup">Meet Up</a></li>
-
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Course">Course</a></li>
+
         <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices#Course">Course</a></li>
-
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Wechat">WeChat</a></li>
+
       </ul>  
       </ul>  
     </div>
     </div>
   </div>
   </div>
<div id="minibar" class="floater" style="display: none;">
<div id="minibar" class="floater" style="display: none;">
-
<ul>
+
<!--projectd -->
-
  <li><a href="https://2014.igem.org/Team:HIT-Harbin/Project"><button><span>Project</span></button></a></li>
+
    <div id="projectd" class="nav1" >                                     <a href="https://2014.igem.org/Team:HIT-Harbin/Project" name="top">Project</a>
-
  <li><a href="https://2014.igem.org/Team:HIT-Harbin/Judging"><button class="default">Judging</button></a></li>
+
      <ul>
-
  <li><a href="https://2014.igem.org/Team:HIT-Harbin/Wetlab"><button class="default">Wetlab</button></a></li>
+
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Background">Background</a></li>
-
  <li><a href="https://2014.igem.org/Team:HIT-Harbin/Software"><button class="default">Software</button></a></li>
+
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Design">Design</a></li>
-
  <li><a href="https://2014.igem.org/Team:HIT-Harbin/Team"><button class="default">Team</button></a></li>
+
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/FutureWork">Advantages</a></li>
-
  <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices"><button class="default">Human&nbsp;&nbsp;practices</button></a></li>
+
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Modeling">Modeling</a></li>
-
</ul>
+
      </ul>
 +
    </div>
 +
    <!--Judgindg-->
 +
    <div id="judgingd" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Safety">Safety</a>
 +
    </div>
 +
 
 +
    <!--Wetlabd-->
 +
    <div id="wetlabd" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Wetlab">Wetlab</a>
 +
      <ul>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Protocols">Protocols</a></li>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Notebook">Notebook</a></li>
 +
    </div>
 +
<div class="nav1 home" ><a href="https://2014.igem.org/Team:HIT-Harbin"></a></div>
 +
    <!--softwared-->
 +
    <div id="softwared" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Software">Software</a>
 +
    </div>
 +
    <!--Teamd -->
 +
    <div id="teamd" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Team">Team</a>
 +
      <ul>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Attribution">Attribution</a></li>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Acknowledge">Acknowledge</a></li>
 +
        <li><a href="https://igem.org/Team.cgi">Profile</a></li>
 +
      </ul>
 +
    </div>
 +
    <!--humanPracticesd -->
 +
    <div id="humanPracticesd" class="nav1" ><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices">Human&nbsp;&nbsp;practices</a>
 +
      <ul>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices#Preliminary">Preliminary</a></li>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices#Meetup">Meet Up</a></li>
 +
        <li><a href="https://2014.igem.org/Team:HIT-Harbin/Humanpractices#Course">Course</a></li>
 +
      </ul>
 +
    </div>
</div>
</div>
 +
      <!--mainarea -->
 +
  <div id="mainarea">
 +
<div id="title">
 +
      <h2>Safety</h2>
 +
    </div>
 +
                    <div class="multi-columns">
 +
                    <div class="paragraphs">
 +
<h3 class="hashed"><span><cufon class="cufon cufon-canvas" alt="Overview: " style="width: 59px; height: 18px;"><cufontext>1.material level</cufontext></cufon></span></h3>
 +
                    <p>There are 3 types of the biological material we have used this year, which are carriers, engineering bacteria and target fragments. Sources of these materials were igem standard library, synthesis and donation from our professor. In the "check in" section, we have backup all the coding protein sequences and obtained the license as well. We will analysis the detail of the safety of material point by point in the paragraphs below.</p>
 +
<p><strong>Strain:</strong> The strains for carrier expression we used this year are E.coli DH5α and yeast BY4741, of which the biological threat level is 1. They are known as harmless microbes, especially the common strains of yeast for brewing, which is a kind of edible strains, whose history of safe using can be traced back to 3000 years ago.</p>
 +
<p><strong>Carrier:</strong> In the experiment of submitting and enzyme-cutting and linking up, we used  PSB1C3, which has proved to be harmless, as the operating carrier to should the official requirement. In the transduction of yeast, we used PRS304 and PRS306 as the carrier, which are commonly used in biological experiment. The carrier is of ammonia benzyl resistance, containing no dangerous pathogenic sequence.</p>
 +
<p><strong>Purpose:</strong> we used TEF2 and the optimized Lexaop + cyc1 as the promoter, and TADH as the separant and the terminator. They are common promoters and terminators in the yeast, with no virulence genes. In addition, lexa DBD is widely used as a common DNA binding protein, and ECFP is also a commonly used fluorescent protein. Moreover, mdr521 Mdr83-805-805 is the polychlorinated biphenyls (PCBS) receptor protein of mice , which widely exists in animals and has no pathogenic effect to people and livestock.
 +
To sum up, in the use of genetic materials, our project is absolutely safe.</p>
 +
                </div>
-
<!--mainarea -->
+
<div class="paragraphs">
 +
<h3 class="hashed"><span><cufon class="cufon cufon-canvas" alt="Overview: " style="width: 59px; height: 18px;"><cufontext>2.application level </cufontext></cufon></span></h3>
 +
                    <p>The track of our project this year is the environment. In terms of environment, we focus on the enrichment, detection and degradation of the serious chemical pollution, dioxin, in the environment. And that made our project an environmentally friendly project.</p>
 +
<p>Compared with the previous methods of dioxin detection, such as enzyme-linked immunoassay and HRGC/HRMS, this project has advantages of low cost, safety, wide application and open nature. For details, please see the <strong>Project Advantages</strong>.</p>
 +
<p>And, of course, this project is still in its developing and perfecting process, and the related researches and tests are only available in the laboratory for now. So we conducted strict monitoring of the safety of the laboratory and make sure the experimental staffs do their job. We never allow emissions of liquid waste and experimental equipment from the lab without sterilization.</p>
 +
                </div>
-
<div id="mainarea">  
+
<div class="paragraphs">
-
            <div id="subheader-bar">
+
<h3 class="hashed"><span><cufon class="cufon cufon-canvas" alt="Overview: " style="width: 59px; height: 18px;"><cufontext>3.safety software</cufontext></cufon></span></h3>
-
                    <div class="site-description"><h4><span class="colored"><cufon class="cufon cufon-canvas" alt="Safety" style="width: 65px; height: 20px;"><canvas width="71" height="27" style="width: 71px; height: 27px; top: -7px; left: 1px;"></canvas><cufontext>Safety</cufontext></cufon></span></h4></div>
+
                     <p>Although every year we fill out the safety form as well as the “check in”, the safety of the parts is still what we're focused on. The existing detection methods about the safety of parts of igem is subjective to a certain degree, and the screening and safety assessment to the parts one by one take a lot of energy of staff and teams. We read some relevant paper concerning about safety and integrated the existing resources to develop the GENE Sequence Corporation, software aimed at safety test. Once you input the parts to be submitting in the interface, the software will compare this sequence with the related toxic protein sequences in the database, thus determine the safety of the parts submitted. In addition, the software can achieve the function of maximum retention of functional protein sequence and elimination of toxicity of the toxic protein sequences.The idea come very late but it is so brilliant so that we don't want to give up.For more details of the sofeware,welcome to our presentation!</p>
-
                      
+
                </div>
-
           
+
-
                <div class="mainarea">
+
-
                    <div class="multi-columns">
+
-
                        <div class="half">
+
-
                            <p></p>1.Risks to the safety and health of team members or others working in the lab?
+
-
<p>No risk. All that we use in our lab are harmless to workers under normal conditions. Once we finished our experiment, all wares we used would be sterilized in high temperature, then we would discard waste in waste bins designated for our iGEM lab, and we would wear gloves when we washed wares.</p>
+
-
                        </div>
+
-
                        <div class="half last">
+
-
                            <p></p>2.Risks to the safety and health of the general public, if released by design or by accident?
+
-
<p>No risk. Our biological materials cannot prevail in natural environment because of their special requirements of cultivation and competitions between microorganisms.
+
-
</p>
+
-
                        </div>
+
-
                    </div>
+
-
                    <div class="multi-columns">
+
                </div>
-
                        <div class="third">
+
                <div style="width: 300px; margin: 0 auto;">
-
                            <p></p>3.Risks to the environment, if released by design or by accident?
+
                <img width="300px" src="https://static.igem.org/mediawiki/2014/6/6e/S1.png">
-
<p>No risk. Our biological materials cannot prevail in natural environment because of their special requirements of cultivation and competitions between microorganisms.
+
                </div>
-
</p>
+
-
                        </div>
+
-
                        <div class="third">
+
-
                            <p></p>4.Risks to security through malicious misuse by individuals, groups, or countries?
+
-
<p>No risk. Our biological materials have no latent menace more than general biological materials.</p>
+
-
                        </div>
+
-
                        <div class="third last">
+
-
                            <p></p>5.If your project moved from a small-scale lab study to become widely used as a commercial/industrial product, what new risks might arise? Also, what risks might arise if the knowledge you generate or the methods you develop became widely available?
+
-
<p>No risk. Our project is friendly to public and environment.</p>
+
-
                        </div>
+
-
                    </div>
+
-
                    <div class="multi-columns">
 
-
                        <div class="fourth">
 
-
                            <p></p>6.Does your project include any design features to address safety risks? (For example: kill switches, auxotrophic chassis, etc.) Note that including such features is not mandatory to participate in iGEM, but many groups choose to include them.
 
-
<p>No, because simple processes, such as sterilizing, can solve the safety problems. Even if we do nothing, the bacteria we use will die due to lack of nutrition, before they propagate.</p>
 
-
                        </div>
 
-
                        <div class="fourth">
 
-
                            <p></p>7.What safety training have you received (or plan to receive in the future)? Provide a brief description, and a link to your institution’s safety training requirements, if available.
 
-
<p>We received safety training about the self-protection, experimental rules, and methods under emergent conditions.
 
-
</p>
 
-
                        </div>
 
-
                        <div class="fourth">
 
-
                            <p></p>8.Does your institution have an Institutional Biosafety Committee, or an equivalent group? If yes, have you discussed your project with them? Describe any concerns they raised with your project, and any changes you made to your project plan based on their review.
 
-
<p>Yes, our institution has the committee that establish guidelines and policies on biosafety. Evaluation of biosafety are regularly carried out, including evaluation of research proposals and monitoring of experimental procedures.
 
-
</p>
 
-
                        </div>
 
-
                        <div class="fourth last">
+
<div class="multi-columns">
-
                            <p></p>9.Does your country have national biosafety regulations or guidelines? If so, please provide a link to these regulations or guidelines if possible.
+
                    <div class="paragraphs">
-
<p>http://english.biosafety.gov.cn/
+
<h3 class="hashed"><span><cufon class="cufon cufon-canvas" alt="Overview: " style="width: 59px; height: 18px;"><cufontext>Wechat Platformlevel</cufontext></cufon></span></h3>
 +
       
 +
<h4>1.1 Overview</h4>
 +
<p>Hitgem is a portable type of inquiry platform for biosafety in microbiological and biomedical laboratories designed for iGemers and some researchers, based on Tencent weChat.</p>
 +
 
 +
<p>It has pros as follows:
 +
a)Users on mobile phone, PC, and iPad can get access to it since it is established via weChat;
 +
b)WeChat has its great amount of users so that this platform can be spread out rapidly;
 +
c)IGemers can check out the biosafety regulations about experiments anytime.
</p>
</p>
-
                        </div>
 
-
                    </div>                     
 
 +
<h4>1.2 Background</h4>
 +
<p>The biosafety of synthetic biology is gathering people’s attention. What’s more, it is a must for every undergraduate team to give out instruction and guidance about safety. Meanwhile, weChat is an instant messaging software developed by Tencent China, whose weChat public platform offers API ports and has over hundred million users all over the world, such that it becomes the first choice as a portable publicizing means.</p>
 +
 +
<h4>1.3 Guidance</h4>
 +
<p><strong>1.3.1 Log in your weChat account</strong></p>
</div>
</div>
</div>
</div>
 +
<div style="width: 321px; margin: 0 auto;">
 +
<img class="wech" width="321px" height="570px" src="https://static.igem.org/mediawiki/2014/4/42/We1.png">
 +
</div>
 +
<div class="multi-columns">
 +
<div class="paragraphs">
-
       
+
<p><strong>1.3.2 Choose <em>Add Contacts</em>, enter <em>hitgem</em> and search</strong></p>
 +
</div>
 +
</div>
 +
<div style="width: 321px; margin: 0 auto;">
 +
<img class="wech" width="321px" height="570px" src="https://static.igem.org/mediawiki/2014/a/a3/We2.png">
 +
</div>
 +
<div class="multi-columns">
 +
<div class="paragraphs">
 +
<p><strong>1.3.3 Tap <em>Follow</em> button, then you will receive a greeting and brief instruction from hitgem</strong></p>
 +
</div>
 +
</div>
 +
<div style="width: 321px; margin: 0 auto;">
 +
<img class="wech" width="321px" height="570px" src="https://static.igem.org/mediawiki/2014/f/fb/We3.png">
 +
</div>
 +
<div class="multi-columns">
 +
<div class="paragraphs">
-
<p></p>
+
<p><strong>1.3.4 Type in <em>safety</em> to get the contents of biosafety handbook</strong></p>
-
<!--
+
</div>
-
NewPP limit report
+
</div>
-
Preprocessor node count: 14/1000000
+
<div style="width: 321px; margin: 0 auto;">
-
Post-expand include size: 82/2097152 bytes
+
<img class="wech" width="321px" height="570px" src="https://static.igem.org/mediawiki/2014/b/b2/We4.png">
-
Template argument size: 0/2097152 bytes
+
</div>
-
Expensive parser function count: 0/100
+
<div class="multi-columns">
-
-->
+
<div class="paragraphs">
 +
 
 +
<p><strong>1.3.5 Enter the corresponding number of the info you want to know, then you will get the details</strong></p>
 +
</div>
 +
</div>
 +
<div style="width: 321px; margin: 0 auto;">
 +
<img class="wech" width="321px" height="570px" src="https://static.igem.org/mediawiki/2014/2/2c/We5.png">
 +
</div>
 +
<div class="multi-columns">
 +
<div class="paragraphs">
 +
 
 +
<p><strong>1.3.6 If you want info about other blocks, just change the entered number</strong></p>
 +
</div>
 +
</div>
 +
<div style="width: 321px; margin: 0 auto;">
 +
<img class="wech" width="321px" height="570px" src="https://static.igem.org/mediawiki/2014/b/b0/We6.png">
 +
</div>
 +
          <div class="cta-box">
 +
                    <a href="https://2014.igem.org/Team:HIT-Harbin/Modeling" class="custom-button">Learn More</a>
 +
                    <p>Click here and get more details about our project.</p>
 +
                </div>
 +
             
 +
               
 +
            </div>
-
<!-- Saved in parser cache with key 2013_igem_org:pcache:idhash:1769-0!1!0!!en!2 and timestamp 20140816124200 -->
 
-
<div class="printfooter">
 
-
Retrieved from "<a href="https://2013.igem.org/Team:HIT-Harbin/Safety">https://2013.igem.org/Team:HIT-Harbin/Safety</a>"</div>
 
-
<div id="catlinks"><div id="catlinks" class="catlinks catlinks-allhidden"></div></div> <!-- end content -->
 
-
<div class="visualClear"></div>
 
-
</div>
 
</div>
</div>
<div id="bottomNav"><a href="#top">Back&nbsp;To&nbsp;Top</a></div>
<div id="bottomNav"><a href="#top">Back&nbsp;To&nbsp;Top</a></div>
<script>toolbar('nav')</script>
<script>toolbar('nav')</script>

Latest revision as of 03:05, 18 October 2014

Safety

1.material level

There are 3 types of the biological material we have used this year, which are carriers, engineering bacteria and target fragments. Sources of these materials were igem standard library, synthesis and donation from our professor. In the "check in" section, we have backup all the coding protein sequences and obtained the license as well. We will analysis the detail of the safety of material point by point in the paragraphs below.

Strain: The strains for carrier expression we used this year are E.coli DH5α and yeast BY4741, of which the biological threat level is 1. They are known as harmless microbes, especially the common strains of yeast for brewing, which is a kind of edible strains, whose history of safe using can be traced back to 3000 years ago.

Carrier: In the experiment of submitting and enzyme-cutting and linking up, we used PSB1C3, which has proved to be harmless, as the operating carrier to should the official requirement. In the transduction of yeast, we used PRS304 and PRS306 as the carrier, which are commonly used in biological experiment. The carrier is of ammonia benzyl resistance, containing no dangerous pathogenic sequence.

Purpose: we used TEF2 and the optimized Lexaop + cyc1 as the promoter, and TADH as the separant and the terminator. They are common promoters and terminators in the yeast, with no virulence genes. In addition, lexa DBD is widely used as a common DNA binding protein, and ECFP is also a commonly used fluorescent protein. Moreover, mdr521 Mdr83-805-805 is the polychlorinated biphenyls (PCBS) receptor protein of mice , which widely exists in animals and has no pathogenic effect to people and livestock. To sum up, in the use of genetic materials, our project is absolutely safe.

2.application level

The track of our project this year is the environment. In terms of environment, we focus on the enrichment, detection and degradation of the serious chemical pollution, dioxin, in the environment. And that made our project an environmentally friendly project.

Compared with the previous methods of dioxin detection, such as enzyme-linked immunoassay and HRGC/HRMS, this project has advantages of low cost, safety, wide application and open nature. For details, please see the Project Advantages.

And, of course, this project is still in its developing and perfecting process, and the related researches and tests are only available in the laboratory for now. So we conducted strict monitoring of the safety of the laboratory and make sure the experimental staffs do their job. We never allow emissions of liquid waste and experimental equipment from the lab without sterilization.

3.safety software

Although every year we fill out the safety form as well as the “check in”, the safety of the parts is still what we're focused on. The existing detection methods about the safety of parts of igem is subjective to a certain degree, and the screening and safety assessment to the parts one by one take a lot of energy of staff and teams. We read some relevant paper concerning about safety and integrated the existing resources to develop the GENE Sequence Corporation, software aimed at safety test. Once you input the parts to be submitting in the interface, the software will compare this sequence with the related toxic protein sequences in the database, thus determine the safety of the parts submitted. In addition, the software can achieve the function of maximum retention of functional protein sequence and elimination of toxicity of the toxic protein sequences.The idea come very late but it is so brilliant so that we don't want to give up.For more details of the sofeware,welcome to our presentation!

Wechat Platformlevel

1.1 Overview

Hitgem is a portable type of inquiry platform for biosafety in microbiological and biomedical laboratories designed for iGemers and some researchers, based on Tencent weChat.

It has pros as follows: a)Users on mobile phone, PC, and iPad can get access to it since it is established via weChat; b)WeChat has its great amount of users so that this platform can be spread out rapidly; c)IGemers can check out the biosafety regulations about experiments anytime.

1.2 Background

The biosafety of synthetic biology is gathering people’s attention. What’s more, it is a must for every undergraduate team to give out instruction and guidance about safety. Meanwhile, weChat is an instant messaging software developed by Tencent China, whose weChat public platform offers API ports and has over hundred million users all over the world, such that it becomes the first choice as a portable publicizing means.

1.3 Guidance

1.3.1 Log in your weChat account

1.3.2 Choose Add Contacts, enter hitgem and search

1.3.3 Tap Follow button, then you will receive a greeting and brief instruction from hitgem

1.3.4 Type in safety to get the contents of biosafety handbook

1.3.5 Enter the corresponding number of the info you want to know, then you will get the details

1.3.6 If you want info about other blocks, just change the entered number

Learn More

Click here and get more details about our project.