Team:SDU-Denmark/safety-b
From 2010.igem.org
(Difference between revisions)
Line 86: | Line 86: | ||
=== Our ideas on 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! === | === Our ideas on 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! === | ||
+ | |||
+ | ==== watermarking standard ==== | ||
+ | |||
+ | To increase public safety we propose to introduce a water-marking standard. | ||
+ | |||
+ | Following the example of Craig Venter, who, in may 2010, created the first watermark in a bacteria, containing several readable messages, we propose to create a watermarking standard to help protect the intellectual rights of the developing team, as well as the safety of the community at large. | ||
+ | |||
+ | We believe that a watermark should contain the following: | ||
+ | |||
+ | -the name of the organism | ||
+ | -the name of the developing team | ||
+ | -a link to the parts-registry containing: | ||
+ | -a full description of the organism | ||
+ | -the risk-assessment performed by the creating team, if available | ||
+ | -the intended use of the organism | ||
+ | -copyright information | ||
+ | -information on how to neutralise organism, and, if available, kill-code | ||
+ | |||
+ | |||
+ | We have set the following criteria for a good watermark: | ||
+ | |||
+ | -It should contain all the above information | ||
+ | -It should not interfere with the other functions of the bacteria | ||
+ | -It should be persistent in the bacteria, i.e. not be removed from the genome due to natural evolution | ||
+ | -It should be easy to find, easy to read and easy to insert by the developing team | ||
+ | |||
+ | notes | ||
+ | The watermark must be inserted into the genome, and not in a plasmid, as it would in theory be able to pass it's watermark on unto other naturally occurring bacteria. | ||
+ | |||
+ | The watermark should be relatively small, as it should not interfere with the functionality of the bacteria. >< Should be connected to a vital function as not to be removed due to natural evolution, perhaps linked to the bacterias metabolism. | ||
+ | |||
+ | Standarlized location or function in the bacteria targeted for insertion of watermark, to make it as easy as possible to locate watermark in rogue bacteria. Should be possible to develop specialized enzyme to cut genome at the desired location, making the creation of a standardized watermarking kit possible. | ||
+ | |||
+ | A full description of the modified organism | ||
+ | A full description of the modified organism should ideally contain the following information | ||
+ | |||
+ | A. characteristics of the host and donor organisms | ||
+ | 1. Name(s) of the organism(s) in question | ||
+ | 2. Origin of organism(s) in question | ||
+ | 3. Information on the reproductive cyclus of the parental organisms as well as the host | ||
+ | 4. Description of any previous genetic modification | ||
+ | 5. Stability | ||
+ | 6. Details concerning pathogenesis, virulence, infectivity or toxicity | ||
+ | 7. characteristics of endogene vectors: | ||
+ | -sequence | ||
+ | -mobilisation | ||
+ | -specificity | ||
+ | -the presence of resistance-genes | ||
+ | 8. host spectrum, | ||
+ | 9. potentially significant physiological traits and the stability of these traits | ||
+ | 10. natural habitat | ||
+ | 11. significant role in environmental processes | ||
+ | 12. Competition or symbiosis with other naturally occurring organisms | ||
+ | 13. Ability to create survival structures (i.e. the ability to create spores) | ||
+ | |||
+ | B. characteristics of the genetically modified organism | ||
+ | 1. origin of the genetic material used to modify the organism, as well as the intended functions of this material | ||
+ | 2. Description of the modification, including the method of vector insertion in the host organism, as well as the method used to create the genetically modified production-organism | ||
+ | 3. the function of the genetic modification | ||
+ | 4. origin and characteristics of the vector | ||
+ | 5. structure and size of vector in the genetically modified production-organism | ||
+ | 6. stability of the organism with respect to genetic traits | ||
+ | 7. mobiliseringshyppigheden of the inserted vector and/or the organism’s ability to transfer genetic material | ||
+ | 8. activity of the expressed protein | ||
+ | |||
+ | C. Health concerns | ||
+ | 1. Toxic or allergenic properties | ||
+ | 2. Product risks | ||
+ | 3. The genetic modified organism’s pathogenic properties compared with the donor – or the host organisms or possibly the donor organism | ||
+ | 4. Colonization ability | ||
+ | 5. If the organism is pathogenic to humans, who are immune competent: | ||
+ | a) Cause illness and the pathogenic mechanism, including invasiveness and virulence | ||
+ | b) infectivity | ||
+ | c) infective dose | ||
+ | d) host range, possibility of change | ||
+ | e) possibility for survival outside the human host | ||
+ | f) The presence of vectors or other distribution areas | ||
+ | g) Biological stability | ||
+ | h) resistance patterns against antibiotics | ||
+ | i) allergencity | ||
+ | j) chance for suitable disease treatment | ||
+ | |||
+ | |||
+ | D. Environmental concerns | ||
+ | 1. factors that might affect the organism’s ability for survival, reproduction and it’s ability to spread in the environment. | ||
+ | 2. techniques for detection, identification and surveillance of the modified organism | ||
+ | 3. techniques for detection of transfer of genetic material to other organisms | ||
+ | 4. known and expected habitats of the modified organism | ||
+ | 5. description of ecosystems into which the organism could spread in the event of an accident | ||
+ | 6. expected result of interaction between the modified organism and naturally occurring bacteria that would be affected in the event of an accident | ||
+ | 7. known and expected effects on animals and plants, with regards to pathogenesis, virulence, infectivity, toxicity, allergenicity, colonisation | ||
+ | 8.known or expected contribution to bio-geo-chemic processes | ||
+ | 9. methods for decontamination of the area in the event of an accident | ||
+ | |||
+ | The above list is from https://www.retsinformation.dk/Forms/R0710.aspx?id=12325 | ||
+ | |||
+ | |||
+ | Copyright information | ||
+ | It should contain all relevant copyright information, as to protect the intellectual property of the creating team. But what exactly is to be considered the subject of copyright? Is it the individual parts? Their functions? Or can one only claim copyright for the entire system? | ||
+ | |||
+ | |||
+ | Information on how to neutralize bacteria | ||
+ | This clause is intended as security measure. Should the bacteria be released into the environment, the parts-registry site should contain information on how to neutralize the bacteria. | ||
+ | |||
+ | If the bacteria has an kill-code inserted, the site should describe how to enact the self-destruct mechanism. | ||
+ | |||
+ | ==== kill-code ==== | ||
+ | |||
+ | Why should we consider inserting kill-codes in genetically modified organisms | ||
+ | What should an efficient kill-code contain | ||
+ | Which bacteria should have a kill-code inserted | ||
+ | When should one enact a kill | ||
+ | Should it be mandatory or optional | ||
+ | Availability of the kill-code | ||
+ | |||
+ | Why should we consider kill-codes | ||
+ | Why should we consider inserting an self-destruct device into modified bacteria? | ||
+ | No system is completely safe. Accidents, no matter how statistically unlikely, will occur. This is especially true when human beings are involved. | ||
+ | |||
+ | An efficient kill-code should | ||
+ | |||
+ | -be activated by an efficient signal | ||
+ | -be persistent | ||
+ | -terminate the bacteria within a very short time span | ||
+ | -not interfere with other functions in the bacteria | ||
+ | |||
+ | Efficient signal | ||
+ | What is to be considered an efficient signal? It should be a signal that | ||
+ | |||
+ | -We can control | ||
+ | |||
+ | -We can induce at will | ||
+ | |||
+ | -That is unlikely to affect other organisms in any harmful way | ||
+ | |||
+ | Would it be sensible to use a naturally occurring signal? Would be beneficial should the bacteria be released into the environment, where the naturally occurring signal would help destroy the rogue bacteria within the shortest possible time span. Of course, it would only be usable if the laboratory does not itself emit, or at least is able to shield the organism, from the activating signal. | ||
+ | An example could be that the kill-code is activated by light of a certain wave-length. If the sun emits this wave-length of light, it should destroy any bacteria that might have been released into nature. It is very easy to shield the organism from the light of the sun in the laboratory, and thus we will not accidentally destroy controlled organisms. Thus we could satisfy the three criteria I have listed above: we can control light of a certain wave-length, at least in a laboratory environment. We can induce this light at will and, thirdly, this light will not harm any other organisms. | ||
+ | One of the major cons of using a naturally occurring signal is that it would be almost impossible to use the organism, in case it would serve any environmental purposes. | ||
+ | |||
+ | Persistence | ||
+ | The kill-code would be left useless should the bacteria dispose of the code through natural evolution within a very short time. Should the bacteria accidentally or, being subject to malign use, intentionally be released into the environment, we would be unable to enact the built-in kill-code, if the code is not linked in some manner to a vital part of the bacterium's genome. If the code is linked to an essential part of the bacterium's genome, it should be unable to dispose of the code without self-termination, thus ensuring persistence. Without the requirement for persistence, the kill-code would give a false sense of security, not knowing if the code is still present in the organism in question. | ||
+ | |||
+ | Termination within a short time span | ||
+ | The shorter the amount of time before the signal is enacted, 'till the rogue bacteria is destroyed, the less harm it is likely to cause. | ||
+ | |||
+ | Non-interference with other functions | ||
+ | |||
+ | Which type of bacteria should contain kill-codes | ||
+ | We suggest level 3 and 4 bacteria would be edible for insertion of a kill-code. Level 1 bacteria pose little to no threat to human beings or the environment, and insertion of a kill-code would not be relevant. Level 2 organisms too would not pose any notable threat, and insertion of a kill-code would be overkill. | ||
+ | Level 3 and 4 organisms however pose moderate to serious threat to human beings, animals, plants and the environment at large. Should any of these organisms escape into the outside world, they would cause considerable harm to the milieu. | ||
</div> | </div> |
Revision as of 15:59, 6 September 2010