Team:Imperial College London/M1/PeptideDelivery

From 2009.igem.org

(Difference between revisions)
(40px Module 1: Protein Production Overview)
 
(40 intermediate revisions not shown)
Line 1: Line 1:
{{Imperial/09/TemplateTop}}
{{Imperial/09/TemplateTop}}
-
= [[Image:II09_Thumb_m1.png| 40px]]<font size='5'> <b>Module 1: Protein Production Overview</b></font>=
 
-
{{Imperial/09/Tabs/M1}}
+
==Peptide Delivery System==
 +
===The Problem===
 +
Many short chain peptide drugs are suseptible to breakdown in the stomach making them suitable candidates for encapsulation.<br><br>
-
==<b>Peptide Delivery</b>==
+
[[Image:MethPep.png|300px|left]]
 +
When synthesised, all polypeptides begin with the same amino acid: methionine. This often removes the desired bioactivity of the compounds.
 +
Some larger polypeptides are cleaved by proteases within the body into smaller functional peptides that do not begin with methionine (as shown on the image to the left.)
 +
<br>
-
Many peptide drugs are suseptible to breakdown in the stomach making them suitable candidates for encapsulation.
+
Making use of the peptide processing pathways within the body, we propose a universal template that can be used for the synthesis of all short chain peptides. By encoding a linker region that is designed to be recognised and cleaved by proteases within the gut, we get past the production difficulties associated with peptides, and allow for the release of these peptides into the gut. What is more, our system does not require the expression any additional genes!<br>
-
When synthesised, all polypeptides begin with the same amino acid: methionine. However, many polypeptides are subsequently chopped into smaller functional peptides that do not begin with methionine.
 
-
[[Image:MethPep.png|400px|left]]
+
===Peptide Processing===
-
<br>
+
-
If we were to use natural polypeptide processing pathways, we would be forced to equip <b><i>The E.ncapsulator</i></b> with different enzymes for different polypeptides. We have avoided this inelegant solution and instead created a universal processing pathway that is compatible with all peptides. What is more, our system does not require the expression any additional genes!<br>
+
To enable <b><i>The E.ncapsulator</i></b> to produce peptides without inhibiting their functionality, we have developed a removable linker region that starts with the amino acid methionine. Following the release of the peptide in the intestine, a naturally occuring enzyme (enteropeptidase) removes the linker region from the front of the peptide releasing the remainder in its functional form. The use of this linker region can be extended to any polypeptide that does not begin with methionine.
-
<html><a href="https://2009.igem.org/Team:Imperial_College_London/PPS"><img style="vertical-align:bottom;" width=90px align="left" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Learnmore.png"></a></html><br><br>&nbsp; About how our universal peptide processing system works.
+
[[Image:Opiorphin.png|left|400px]]
-
<br>
+
This image shows the universal template for peptide production. The methionine start is shown in RED, the protease recognition site is shown in BLUE and opiorphin is shown in GREEN. The RED & BLUE sections make up the removable linker region cleaved in the gut.
-
<br>
+
<br><br><br><br><br>
-
<br>
+
-
===Opiorphin===
 
-
To showcase peptide delivery, we have selected the pentapeptide (five amino acids) opiorphin. This peptide is naturally found in human saliva and plays a role in pain relief and pleasure. The delivery of opiorphin by <i>The E.ncapsulator</i>, marks the iGEM first entry to tackle psychological problems such as chronic pain and depression.<br>
+
{{Imperial/09/Division}}
 +
<center>
 +
===Module 1: Enzyme Production===
 +
</center>
 +
<html><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1"><img style="vertical-align:bottom;" width="20%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Homepageimage3.png"></a><a href="https://2009.igem.org/Team:Imperial_College_London/M1/EnzymeDelivery"><img style="vertical-align:bottom;" width="20%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Homepageimage3.png"></a><a
 +
href="https://2009.igem.org/Team:Imperial_College_London/M1/Genetic"><img style="vertical-align:bottom;" width="20%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_geneticcircuit1.png"></a><a
 +
href="https://2009.igem.org/Team:Imperial_College_London/Temporal_Control/M2/Wetlab"><img style="vertical-align:bottom;" width="20%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Wetlabmainimage9.png"></a><html><a
-
<html><a href="https://2009.igem.org/Team:Imperial_College_London/Opiorphin"><img style="vertical-align:bottom;" width=90px align="left" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Learnmore.png"></a></html><br><br>&nbsp; About opiorphin.
+
href="https://2009.igem.org/Team:Imperial_College_London/M2/Modelling"><img style="vertical-align:bottom;" width="20%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Drylabmainimage6.png"></a><center></html>
-
{{Imperial/09/Division}}
+
<html><table border="0" style="background-color:transparent;" width="100%">
 +
<tr><td width="0%"></td>
-
<html><center><a href="https://2009.igem.org/Team:Imperial_College_London/Project_Overview"><img width=150px src="https://static.igem.org/mediawiki/2009/d/d8/II09_M1ArrowLeft.png"></a><a href="https://2009.igem.org/Team:Imperial_College_London/M2"><img width=150px src="https://static.igem.org/mediawiki/2009/d/d9/II09_M1ArrowRight.png"></a></center>
+
<td width="20%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1"><b>Module 1 Overview</b></a></center></td>
-
</html>
+
 
 +
<td width="20%"><center><a href="/Team:Imperial_College_London/M1/EnzymeDelivery"><b>Enzyme Delivery </b></a></center></td>
 +
 
 +
<td width="20%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1/Genetic"><b>Genetic Circuit</b></a></center></td>
 +
 
 +
<td width="20%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/Temporal_Control/M2/Wetlab"><b>Wet Lab</b></a></center></td>
 +
 
 +
<td width="20%"><center><a
 +
href="https://2009.igem.org/Team:Imperial_College_London/M2/Modelling"><b>Modelling</b></a></center></td>
-
<br>
 
-
{{Imperial/09/Division}}
 
-
<!-- <center><b></b></center> -->
 
-
<html><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1/Genetic"><img style="vertical-align:bottom;" width="23%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Homepageimage3.png"></a><a href="https://2009.igem.org/Team:Imperial_College_London/Temporal_Control/M1/Wetlab"><img style="vertical-align:bottom;" width="23%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Homepageimage4.png"></a><a href="https://2009.igem.org/Team:Imperial_College_London/M1/Modelling"><img style="vertical-align:bottom;" width="23%" src="http://i691.photobucket.com/albums/vv271/dk806/II09_Homepageimage5.png"></a><html><a
 
-
href="https://2009.igem.org/Team:Imperial_College_London/M1/Results"><img style="vertical-align:bottom;" width="27%" src="https://static.igem.org/mediawiki/2009/2/20/II09_WorldMap.png"></a><center></html>
 
-
<html><table border="0" style="background-color:transparent;" width="100%">
 
-
<tr><td width="0%"></td>
 
-
<td width="25%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1/Genetic"><b>Genetic Circuit</b></a></center></td>
 
-
<td width="25%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/Temporal_Control/M1/Wetlab"><b>WetLab</b></a></center></td>
 
-
<td width="25%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1/Modelling"><b>Modelling</b></a></center></td>
 
-
<td width="25%"><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1/Results"><b>Results</b></a></center></td>
 
<td width="1%"></td>
<td width="1%"></td>
</tr></table></html>
</tr></table></html>
-
<br>
+
<html><center><a href="https://2009.igem.org/Team:Imperial_College_London/M1"><img width=150px src="https://static.igem.org/mediawiki/2009/1/10/II09_TourArrow.png"></a>
 +
</html>
{{Imperial/09/TemplateBottom}}
{{Imperial/09/TemplateBottom}}

Latest revision as of 22:23, 19 October 2009


Contents

Peptide Delivery System

The Problem

Many short chain peptide drugs are suseptible to breakdown in the stomach making them suitable candidates for encapsulation.

MethPep.png

When synthesised, all polypeptides begin with the same amino acid: methionine. This often removes the desired bioactivity of the compounds. Some larger polypeptides are cleaved by proteases within the body into smaller functional peptides that do not begin with methionine (as shown on the image to the left.)

Making use of the peptide processing pathways within the body, we propose a universal template that can be used for the synthesis of all short chain peptides. By encoding a linker region that is designed to be recognised and cleaved by proteases within the gut, we get past the production difficulties associated with peptides, and allow for the release of these peptides into the gut. What is more, our system does not require the expression any additional genes!


Peptide Processing

To enable The E.ncapsulator to produce peptides without inhibiting their functionality, we have developed a removable linker region that starts with the amino acid methionine. Following the release of the peptide in the intestine, a naturally occuring enzyme (enteropeptidase) removes the linker region from the front of the peptide releasing the remainder in its functional form. The use of this linker region can be extended to any polypeptide that does not begin with methionine.


Opiorphin.png

This image shows the universal template for peptide production. The methionine start is shown in RED, the protease recognition site is shown in BLUE and opiorphin is shown in GREEN. The RED & BLUE sections make up the removable linker region cleaved in the gut.






Mr. Gene   Geneart   Clontech   Giant Microbes