Team:Virginia/Project Overview
From 2013.igem.org
(2 intermediate revisions not shown) | |||
Line 236: | Line 236: | ||
<p><a href="https://2013.igem.org/Team:Virginia/Results">Results</a></p> | <p><a href="https://2013.igem.org/Team:Virginia/Results">Results</a></p> | ||
<p><a href="https://2013.igem.org/Team:Virginia/Modeling">Modeling</a></p> | <p><a href="https://2013.igem.org/Team:Virginia/Modeling">Modeling</a></p> | ||
+ | <p><a href="https://2013.igem.org/Team:Virginia/Software">Software</a></p> | ||
+ | |||
<p><a href="https://2013.igem.org/Team:Virginia/Chassis_Improvements">Chassis Improvements</a></p></span> | <p><a href="https://2013.igem.org/Team:Virginia/Chassis_Improvements">Chassis Improvements</a></p></span> | ||
</li> | </li> | ||
Line 247: | Line 249: | ||
</li> | </li> | ||
<li> | <li> | ||
- | + | <span class="title">Human Practices</span> | |
<span class="text"> | <span class="text"> | ||
<p><a href="https://2013.igem.org/Team:Virginia/Human_Practices_Overview">Overview</a></p> | <p><a href="https://2013.igem.org/Team:Virginia/Human_Practices_Overview">Overview</a></p> | ||
<p><a href="https://2013.igem.org/Team:Virginia/Safety Considerations">Safety Considerations</a></p> | <p><a href="https://2013.igem.org/Team:Virginia/Safety Considerations">Safety Considerations</a></p> | ||
- | <p><a href="https://2013.igem.org/Team:Virginia/ | + | <p><a href="https://2013.igem.org/Team:Virginia/High_School_Education_Series">High School Education Series</a></p> |
<p><a href="https://2013.igem.org/Team:Virginia/Documentary">Documentary</a></p> | <p><a href="https://2013.igem.org/Team:Virginia/Documentary">Documentary</a></p> | ||
- | <p><a href="https://2013.igem.org/Team:Virginia/ | + | <p><a href="https://2013.igem.org/Team:Virginia/Media_Coverage">Media Coverage</a></p> |
+ | </span> | ||
</li> | </li> | ||
<li> | <li> | ||
Line 268: | Line 271: | ||
<span><u>Project Overview</u></span> | <span><u>Project Overview</u></span> | ||
<br><br> | <br><br> | ||
- | <p><u> | + | <p><u> Opportunity: Synthesizing a Better Drug Delivery Vector </u></p> |
- | <p> <p style="text-indent: 5em;"> | + | <p> <p style="text-indent: 5em;">Every freely administered drug causes side effects. Cancer is a classic example. Because of off-target toxicity, many cancer patients have to hope that their chemotherapy kills their cancer before it kills them. </p> |
+ | <p style="text-indent: 5em;"> Many drug delivery nano-vectors have been developed to address this issue. However, most have severely limiting disadvantages. For example, liposomes, the vector projected to have the largest market share in the next ten years, are often expensive to produce and leaky in functionality. </p> | ||
+ | <p><p style="text-indent: 5em;">Bacteria have several properties that would make them an interesting alternative drug delivery vectors. | ||
+ | <ul><li>Their surface membranes can be modified for targeting </li> | ||
+ | <li>Biological and can accommodate Biobricks </li> | ||
+ | <li>Easily grown and manufactured, unlike many other drug delivery vectors. </li> | ||
+ | </ul></p> | ||
<br> | <br> | ||
- | + | <p style="text-indent: 5em;"> Unfortunately, as in the case of many potential synthetic biology applications, the utility of bacteria as vectors is limited by safety concerns. Our initial investigation on this problem led us to a forgotten discovery from the 1950’s—the bacterial minicell. </p> | |
- | + | <p style="text-indent: 5em;"> Minicells are small, achromosomal products of aberrant cell division. Because they lack chromosomes , they cannot replicate, mutate, or express virulent bacteria genes. However, they still express transfected plasmids, which means that minicells remain fully compatible with standardized biobrick parts. While largely neglected for decades, minicells are only now resurfacing, in the wake of the recent, explosive growth of the modern biotechnology industry. This past summer, we engineered the bacterial minicell into a safe, alternative chassis for drug delivery applications. </p> | |
- | While largely neglected for decades, minicells are only now resurfacing, in the wake of the recent, explosive growth of the modern biotechnology industry. | + | |
- | </p> | + | |
</div></div></div> | </div></div></div> | ||
Latest revision as of 01:54, 29 October 2013
Opportunity: Synthesizing a Better Drug Delivery Vector
Every freely administered drug causes side effects. Cancer is a classic example. Because of off-target toxicity, many cancer patients have to hope that their chemotherapy kills their cancer before it kills them.
Many drug delivery nano-vectors have been developed to address this issue. However, most have severely limiting disadvantages. For example, liposomes, the vector projected to have the largest market share in the next ten years, are often expensive to produce and leaky in functionality.
Bacteria have several properties that would make them an interesting alternative drug delivery vectors.
- Their surface membranes can be modified for targeting
- Biological and can accommodate Biobricks
- Easily grown and manufactured, unlike many other drug delivery vectors.
Unfortunately, as in the case of many potential synthetic biology applications, the utility of bacteria as vectors is limited by safety concerns. Our initial investigation on this problem led us to a forgotten discovery from the 1950’s—the bacterial minicell.
Minicells are small, achromosomal products of aberrant cell division. Because they lack chromosomes , they cannot replicate, mutate, or express virulent bacteria genes. However, they still express transfected plasmids, which means that minicells remain fully compatible with standardized biobrick parts. While largely neglected for decades, minicells are only now resurfacing, in the wake of the recent, explosive growth of the modern biotechnology industry. This past summer, we engineered the bacterial minicell into a safe, alternative chassis for drug delivery applications.