Difference between revisions of "Team:Ionis Paris/Ethics"

Line 163: Line 163:
 
         <!-- ====END BLOG TABLE==== -->
 
         <!-- ====END BLOG TABLE==== -->
 
          
 
          
        <!-- ====START SOCIAL Link==== -->
+
    <!-- ====START SOCIAL Link==== -->
        <div class="footer_social">
+
    <div class="footer_social">
            <div class="container-fluid">
+
        <div class="container-fluid">
                <div class="row">
+
            <div class="row">
                    <ul class="ft_top clearfix">
+
                <ul class="ft_top clearfix">
                        <li class="waves-effect waves-light">
+
                    <li class="waves-effect waves-light">
                            <a href="https://www.facebook.com/ionisigem/?fref=ts" target="_blank">
+
                        <a href="https://www.facebook.com/ionisigem/?fref=ts" target="_blank">
                                <i class="zmdi zmdi-facebook "></i>Facebook
+
                            <i class="zmdi zmdi-facebook "></i>Facebook
                            </a>
+
                        </a>
                        </li>  
+
                    </li>
                        <li class="waves-effect waves-light">
+
                    <li class="waves-effect waves-light">
                            <a href="https://twitter.com/igem_ionis" target="_blank">
+
                        <a href="https://twitter.com/igem_ionis" target="_blank">
                                <i class="zmdi zmdi-twitter"></i>Twitter
+
                            <i class="zmdi zmdi-twitter"></i>Twitter
                            </a>
+
                        </a>
                        </li>  
+
                    </li>
                        <li class="waves-effect waves-light">
+
                    <li class="waves-effect waves-light">
                            <a href="https://www.youtube.com/channel/UC0RyQsB5YpweSRBYQlAdZDA" target="_blank">
+
                        <a href="https://www.youtube.com/channel/UC0RyQsB5YpweSRBYQlAdZDA" target="_blank">
                                <i class="zmdi zmdi-youtube"></i>youtube
+
                            <i class="zmdi zmdi-youtube"></i>youtube
                            </a>
+
                        </a>
                        </li>  
+
                    </li>
                        <li class="waves-effect waves-light">
+
                    <li class="waves-effect waves-light">
                            <a href="https://www.linkedin.com/company/igem-ionis" target="_blank">
+
                        <a href="https://www.linkedin.com/company/igem-ionis" target="_blank">
                                <i class="zmdi zmdi-linkedin"></i>LinkedIn
+
                            <i class="zmdi zmdi-linkedin"></i>LinkedIn
                            </a>
+
                        </a>
                        </li>  
+
                    </li>
+
 
                    </ul>
+
                </ul>
                </div>
+
 
             </div>
 
             </div>
 
         </div>
 
         </div>
        <!-- ====END FOOTER TOP==== -->
+
    </div>
       
+
    <!-- ====END FOOTER TOP==== -->
        <!-- ====START FOOTER AREA==== -->
+
 
        <footer class="footer_area">
+
    <!-- ====START FOOTER AREA==== -->
            <div class="footer_middle">
+
    <footer class="footer_area">
                <div class="container">
+
        <div class="footer_middle">
                    <div class="row">
+
            <div class="container">
                        <div class="col-xs-12">
+
                <div class="row">
                            <div class="scroll_area">
+
                    <div class="col-xs-12">
                                <div class="sroll_top">
+
                        <div class="scroll_area">
                                  <a href="#back_to_the_top"> <i class="zmdi zmdi-chevron-up btn waves-effect"> </i> </a
+
                            <div class="sroll_top">
                                </div>
+
                                <a href="#ancre"> <i class="zmdi zmdi-chevron-up btn waves-effect"> </i> </a>
 
                             </div>
 
                             </div>
 
                         </div>
 
                         </div>
 
                     </div>
 
                     </div>
 +
                </div>
 +
                <div class="row">
 
                     <div class="row">
 
                     <div class="row">
                      <div class="row">
 
 
                         <div class="col-lg-5 col-md-5 col-sm-12">
 
                         <div class="col-lg-5 col-md-5 col-sm-12">
 
                             <div class="middle_content">
 
                             <div class="middle_content">
                                 <h4>IONIS IGEM</h4>
+
                                 <h4>iGEM IONIS</h4>
                                 <p> We're a group of six different schools from the IONIS Education Group. For this competition we wanted to take advantages of the multiple schools and activity field given by the IONIS education group to create a solid project.</p>
+
                                 <p> We're a group of six different schools from the IONIS Education Group. For this
                              <a href="https://2016.igem.org/Team:Ionis_Paris/Team">Read More</a>
+
                                    competition we wanted to take advantages of the multiple schools and activity field
 +
                                    given by the IONIS education group to create a solid project.</p>
 +
                                <a href="https://2016.igem.org/Team:Ionis_Paris/Team">Read More</a>
 
                             </div>
 
                             </div>
 
                         </div>
 
                         </div>
             
+
 
 
                         <div class="col-lg-3 col-lg-offset-1 col-md-4 col-sm-7">
 
                         <div class="col-lg-3 col-lg-offset-1 col-md-4 col-sm-7">
 
                             <div class="footer_Widgets">
 
                             <div class="footer_Widgets">
Line 230: Line 232:
 
                                             <a href="mailto:igem.ionis@gmail.com">email: igem.ionis@gmail.com</a>
 
                                             <a href="mailto:igem.ionis@gmail.com">email: igem.ionis@gmail.com</a>
 
                                         </li>
 
                                         </li>
                                     
+
 
 
                                     </ul>
 
                                     </ul>
 
                                 </div>
 
                                 </div>
Line 236: Line 238:
 
                         </div>
 
                         </div>
  
                       
 
  
 
                     </div>
 
                     </div>
Line 248: Line 249:
 
                             <div class="col-md-7 fix_p_l">
 
                             <div class="col-md-7 fix_p_l">
 
                                 <nav>
 
                                 <nav>
                                     <ul class="ft_bottom">    
+
                                     <ul class="ft_bottom">
 
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris">Home</a></li>
 
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris">Home</a></li>
                                         <li><a href="https://2016.igem.org/At_the_lab.html">At the Lab</a></li>
+
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris/Working_at_La_Paillasse">in the Lab</a></li>
                                         <li><a href="https://2016.igem.org/CelloCad"> Side Projects</a></li>
+
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris/Measurement"> Side Projects</a></li>
                                         <li><a href="Results">Results</a></li>
+
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris/Parts">Results</a></li>
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris/Human_Practice">Human Practice</a></li>
+
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris/HPintro">Human
                                         <li><a href="https://2016.igem.org/Team.html">Team</a></li>
+
                                            Practice</a></li>
 +
                                         <li><a href="https://2016.igem.org/Team:Ionis_Paris/Team">Team</a></li>
 
                                     </ul>
 
                                     </ul>
 
                                 </nav>
 
                                 </nav>
Line 260: Line 262:
 
                             <div class="col-md-5 fix_p">
 
                             <div class="col-md-5 fix_p">
 
                                 <div class="ft_paragraph">
 
                                 <div class="ft_paragraph">
                                     <p>©IONIS_IGEM_2016</a>.</p>  
+
                                     <p>©IONIS_IGEM_2016</a>.</p>
 
                                 </div>
 
                                 </div>
                             </div>
+
                             </div>
 
                         </div>
 
                         </div>
 
                     </div>
 
                     </div>
 
                 </div>
 
                 </div>
             </div>            
+
             </div>
        </footer>
+
    </footer>
        <!-- ====END FOOTER AREA==== -->
+
    <!-- ====END FOOTER AREA==== -->
     
+
 
        <!-- Nos scripts -->
+
    <!-- ====Google Maps API==== -->
<!-- TODO: Debug these scripts
+
    <script src="https://maps.googleapis.com/maps/api/js"></script>
        <script type="text/javascript" src="https://2016.igem.org/wiki/index.php?title=Template:IONIS_PARIS_JS_Venobox&action=raw&ctype=text/javascript"></script>
+
        <script type="text/javascript" src="https://2016.igem.org/wiki/index.php?title=Template:IONIS_PARIS_JS_MDB&action=raw&ctype=text/javascript"></script>
+
        <script type="text/javascript" src="https://2016.igem.org/wiki/index.php?title=Template:IONIS_PARIS_JS_Carousel&action=raw&ctype=text/javascript"></script>
+
-->
+
        <script type="text/javascript" src="https://2016.igem.org/wiki/index.php?title=Template:IONIS_PARIS_JS&action=raw&ctype=text/javascript"></script>
+
  
 +
    <!-- Nos scripts -->
 +
    <script type="text/javascript" src="https://2016.igem.org/wiki/index.php?title=Template:IONIS_PARIS_JS&action=raw&ctype=text/javascript"></script>
  
     
 
 
</html>
 
</html>

Revision as of 12:22, 18 October 2016

Ethics

Risks assessment




Quantifly is an ambitious and innovative project that, like other projects of its kind, presents risks and challenges which make it more inspiring and challenging to develop. What makes Quantifly unique is that every risk we face is a challenge that we try to overcome with great passion and motivation, taking the project always further and further.

The main risks we have identified can be linked to the use of biological elements. We are indeed planning to use genetically engineered bacteria, which implies an ethical dimension, given that those bacteria would be used in the open world. This problematic is our biggest challenge and we are working on a containment method similar to an airlock that would allow an efficient sampling of the air with no bacteria escaping the collection tube that would allow us to separate bacteria from the environment. The first tests will be run in the laboratory, under simulated environmental conditions.

Another issue is related to bacteria themselves. Our system aims to develop bacteria as detection and measurement tools, but life and living organisms are not fully controllable, whereas human-made tools are lifeless objects that we can control. Therefore, a number of parameters linked to the bacteria can interfere with the functioning of our biosensor in a way that we cannot predict until we experience it. Though the mechanism we added to the cell is simple in the fact that it is a simple transcription factor activating a luciferase expression, we don’t know how well it will handle real-life conditions and how bacteria will react and maybe adapt to this uncommon reaction.

Although our biggest challenges come from biology, we also identified a mechanical risk in the drone. When using our drone, we might come to the possibility that the drone will have an accident. We designed a security system for this event that will allow us to handle such accident without harm and pollution. This standard system, present on many drones, would allow us to avoid losing control of it.

We are also aware of the issues caused by the use of a drone in urban areas. However, many solutions exist that would allow us to bypass such problems. As an example, we could adopt an economic model based on the sale of a service, not a product. Though this concern is not our priority during the current Development phase of our project, we are already considering it as we are under conception of a business model that would allow the pursuit of our project after the iGEM competition if the team members are motivated to do so. This business model is taking into account the management model and the specifications of how we could make our project evolve. Through this reflexion we want to show that we are anticipating what can potentially come after the jamboree and how we can think about risks that may not be dangerous for the competition, but could prove to be issues if we were to continue afterwards.

All those risks present a question that we have to take in reflexion, in order to assess any potential issue that could imply danger for the team while working, or for anyone in the application of our product. In this objective, we try to anticipate anything that could go south, and we developed several solutions to prevent anything unexpected to happen.




Biosafeties

How to keep it safe ?




Of course, biosafety was a primordial part of our project, given that we have been working on genetically modified organisms. We conducted a reflexion about the different ways to make our project the safest for us and for the environment in the case it would become a concrete application. It was our will to push the thinking to fully developed biosafety measures for our project. In this way, we wished to demonstrate our anticipation of the concretisation of our product.

The safety applications that we put to light can be grouped in two categories: the biological safeties, and the mechanical safeties. The biological area focuses on all the means that can be integrated in our biosensor, being genetic modifications or epigenetic mechanisms that will influence the cell behaviour if conditions are required. Those are taking a significant amount of time to create in the lab, and though we did research and develop the idea, we did not have enough time in the iGEM competition to implement them. We will however present them in this part to show our reflexion.

We thought of several tracks to follow for our biological safeties:

  • Kill switch: The kill switch is a well-known method to prevent a micro-organism culture from contaminating its environment. It can have various forms ( toxin/antitoxin system which will be further developed, genetic switch-off, genetically engineered logical gate) and it allows to induce cell death as soon as the condition that activates the kill switch is fulfilled. It is one of the best option we can use in our system to allow a strict biological control of our micro-organism.

  • Bacteria traceability: through a tag (fluorescence, radioactivity, or just genetic tagging of a constitutive compound) we could keep track of the micro-organism when it would come to a leak in the open environment. This method would allow to follow, contain and eventually prevent any further contamination of the micro-organism – bacteria for Quantifly – in a dangerous or harmful way for the environment.

  • Cellular cycle inactivation: with the inactivation of the micro-organism’s cellular cycle, we can prevent it from replicating and thus we are sterilizing it. This method has the advantage to prevent colonies proliferation. We can also keep control of the population in our product, but it involves a heavy manipulation in the lab to inactivate a whole cell culture and the lifespan of such cells is really short as it is a matter of minutes before cell death would activate. Though this method could be a mean of control in case of environmental contamination, it is not the appropriate technique to use in our project.

  • ATP production limitation: This track is thought as a genetic engineering to have our micro-organism produce less ATP, producing just enough energy to make sure it can survive but not develop (as the cell replication requires important amounts of energy). By limiting the ATP production in the cell, we are ensuring it won’t be able to go through its cycle, and we can control again the population growth. However it will certainly put micro-organisms in stress conditions, which cannot guarantee the functioning of our biosensor.

  • Toxin/anti-toxin system: the aim of this method would be to have our micro-organism produce a toxin to which it is not naturally immune, and in completion the medium in which the cultures are done provides the anti-toxin, allowing the micro-organism to survive in our controlled environment. As soon as the micro-organism escapes this environment, it will die from the intoxication. This method is one of the best we can have at the biological level since it makes our micro-organism dependant to the medium we are controlling and it is directly preventing any contamination in or from our cultures.

As biological safeties focus on the control and /or prevention of our micro-organism contamination, which is quite heavy to achieve in the given time for our project, the mechanical safety measures are, for some of them, simpler to input in the development of our product. They are directly linked to the mechanical aspect of the project, being the drone and its software. We thought of several options that could guarantee the control of the device and assure total safety for the manipulations it is designed to do. Thus, we will detail these different options and we will explain the reflexion behind the idea and how we could implement them on our device.

  • Organic detergent in tubes: the idea is to create an envelope around the micro-organism’s tube on the drone that will contain organic detergent. Thus, if the drone were to crash and the tubes break, the cultures would make contact with the detergent, leading to their complete destruction on-spot.

  • Injection system: another way of using the organic detergent is to create an injection system that would function on an altimeter and when an intense fall in altitude is detected, detergent would be injected in cultures, inducing the destruction of the culture.

  • Tubes’ material: as well as a crash procedure, we want to anticipate on this event by working on the cultures’ tubes material. The use of glass would be prohibited since the durability of such resource is not good at all in the case of a shock. The ideal material would be a strong and resistant plastic such as polyvinyl chloride (PVC) that can endure a several meters fall and the impact with the ground, while preventing cultures to spread in the environment.

  • Parachute: A simple safety we can input on the drone is a parachute that would be activated when altitude is falling too fast, preventing the drone to brutally crash on the ground.

  • Drone systems reboot for control loss: another issue we can come across is the failure of the systems of the drone, which can lead to a fall down. If such thing should happen, the presence of a reboot input (red button) can restart the drone while still in the air, allowing to retake control of the device quickly preventing an accident.

  • Global positioning system control: besides of falling, another issue for the drone can be to get out of the area defined for the measures, which could create a dysfunction in the drone piloting and/or flying abilities. A solution we thought is to input in the software a GPS detection of the drone to the area designed, and when the drone gets out of the zone, it will automatically come back into the measurement area.

The biosafeties as well as the mechanical solutions are compiling into a complex and safe device that can still be easily manipulated. The most careful way to do is to create safety measures in a layer format. The ideal is to concretise all of those safety leads, but we can basically work on a three-layer concept coordinating biological safeties such as a kill switch or a toxin/ani-toxin system coupled to an organic detergent injection system in case of falling as well as a parachute. The stacking of different safety measures is the best option given that it covers most of the risks we can face.