Difference between revisions of "Safety/Check In"

(Undo revision 31059 by Sifuentes anita (talk))
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Main2017}}
 
{{Main2017}}
−
<html></html>
+
{{HTML/JSDisabled}}
  
−
{{HTML/JSDisabled}}
 
 
<html>
 
<html>
  
−
<link rel="stylesheet" type="text/css" href="https://igem.org/Template:CSS/Forms?action=raw&ctype=text/css" />
+
<link rel="stylesheet" type="text/css" href="https://igem.org/wiki/index.php?title=HQ:Forms.css&action=raw&ctype=text/css" />
−
 
+
 
<style type="text/css">
 
<style type="text/css">
 
#formbody .twoColumnInline {
 
#formbody .twoColumnInline {
Line 31: Line 29:
 
}
 
}
  
−
p.faq
+
 
−
{
+
−
text-indent: 2em;
+
−
color: #337f53;
+
−
font-style: italic;
+
−
}
+
 
</style>
 
</style>
  
 
<script type="text/javascript">
 
<script type="text/javascript">
 
var form_info = {};
 
var form_info = {};
−
form_info.name="2016_check_in";
+
form_info.name="2017_check_in";
−
form_info.display_title='2016 Check-In';
+
form_info.display_title='2017 Check-In';
−
form_info.year="2016";
+
form_info.year="2017";
 
form_info.default_mode = "edit";
 
form_info.default_mode = "edit";
 
form_info.owner_type = "team";
 
form_info.owner_type = "team";
 
form_info.permissions = {view: ["public"],
 
form_info.permissions = {view: ["public"],
−
edit: ["group_members"],
+
edit: ["group_members", "super_users"],
−
submit: ["group_members"],
+
submit: ["group_members", "super_users"],
 
admin: ["super_users"]};
 
admin: ["super_users"]};
 
form_info.validate_unspecified_fields = "required";
 
form_info.validate_unspecified_fields = "required";
−
form_info.ajax_URL = "https://2016.igem.org/cgi/forms/form.cgi";
+
form_info.ajax_URL = "https://old.igem.org/cgi/forms/form.cgi";
 
</script>
 
</script>
−
<script src="https://igem.org/Template:JS/KForms_2pt4?action=raw&ctype=text/javascript"></script>
 
  
−
<!--<div class="oneColumn alert_box">
+
<script src="https://old.igem.org/wiki/index.php?title=HQ:Safety_Forms.js&action=raw&ctype=text/javascript"></script>
−
<center>Check-In Form Bug: The submit button is currently not working, however, your form's progress will be saved. Please bear with us while we fix this issue.
+
−
</center>
+
−
</div>-->
+
  
−
<div class="oneColumn">
+
<div class="column full_size">
  
−
 
+
<h1>Safety Check-Ins</h1>
−
<h2>Submit a Check-In before you acquire or use any organism or part that is not on the <a href="https://2016.igem.org/Safety/White_List">White List</a>.</h2>
+
<h3>Submit a Check-In before you acquire or use any organism or part that is not on the <a href="https://2017.igem.org/Safety/White_List">White List</a>.</h3>
  
 
<p>Check-Ins are a way for you to quickly and easily ask iGEM's safety experts to review your plans for safely acquiring and using a higher risk organism/part, and to approve your plans or suggest changes.</p>
 
<p>Check-Ins are a way for you to quickly and easily ask iGEM's safety experts to review your plans for safely acquiring and using a higher risk organism/part, and to approve your plans or suggest changes.</p>
−
 
−
<p>You should submit a Check-In <strong>before you acquire or use certain materials in your lab.</strong> Specifically, you should send us a Check-In for any organism or part that is not on the <a href="https://2016.igem.org/Safety/White_List">White List</a>. We expect to reply to most Check-Ins within a few days at most. Once the iGEM Safety Committee has approved your Check-In by email, you may begin working with the material (organism or part). You may Check-In for as many organisms/parts as you wish, and any team member may send a Check-In at any time until the Jamboree.</p>
 
  
 
<ul>
 
<ul>
Line 75: Line 62:
 
</ul>
 
</ul>
  
−
<div class="click_open"> <h5>Frequently Asked Questions about Check-Ins (click to show/hide)</h5> <div class="click_icon">▼</div>
+
</div>
  
−
<div class="click_content">
+
<div class="column half_size">
−
        <ul>
+
<p>You should submit a Check-In <strong>before you acquire or use certain materials in your lab.</strong> Specifically, you should send us a Check-In for any organism or part that is not on the <a href="https://2017.igem.org/Safety/White_List">White List</a>. We expect to reply to most Check-Ins within a few days at most.  
−
        <li><p class="faq">What if I am unsure whether my organism/part requires a Check-In?</p>
+
</p>
−
        <p>Ask us! Email safety AT igem DOT org to ask questions about what requires a Check-In. Or, because the Check-In form is short and easy, you can submit a Check-In even if you are unsure whether it is necessary.</p></li>
+
−
        <li><p class="faq">We want to do a little preliminary work with an organism/part, but we might not use it for our final project. Do we still have to Check-In before we acquire the organism/part?</p>
+
−
        <p>Yes! Please Check-In for every organism/part you want to acquire that is not on the White List, even if you will not use it in your final project. You can tell us in the "Further Comments" section that it is not for your final project, or that you are unsure. We have made the Check-In form short and easy, so you can Check-In for many parts, even ones you are not sure about using.</p></li>
+
−
        <li><p class="faq">Uh-oh! We misunderstood the White List, and we already started working with an organism/part that requires a Check-In. What do we do?</p>
+
−
        <p>Just let us know. Email safety AT igem DOT org to describe the situation, and send us a Check-In promptly. Tell us in the "Further Comments" section what you have done with the organism/part already.</p></li>
+
−
        <li><p class="faq">We are going to use a lot of parts. May we combine them on a single Check-In?</p>
+
−
        <p>If the parts all come from the same parent organism, you may combine them on a single Check-In, but make sure you give complete information about each part. If the parts come from different parent organisms, please send separate Check-Ins.</p></li>
+
−
        <li><p class="faq">You approved our Check-In for an organism/part. Do we still need to ask our university/institution about it? What about checking local laws?</p>
+
−
        <p>Yes! The iGEM Safety Committee does not replace institutional review boards, or your local government. You are responsible for obtaining from your university or government any approvals that might be necessary. Your university or government might have different rules about what organisms/parts require special approval.</p></li>
+
−
        <li><p class="faq">We are only using organisms/parts from the White List, and therefore we do not need to submit any Check-Ins. Do we still need to ask our university/institution about our project? What about checking local laws?</p>
+
−
        <p>Yes! Again, the iGEM Safety Committee does not replace institutional review boards, or your local government. Even if you are only using organisms/parts that are generally considered "safe", you still have the responsibility to follow good laboratory procedures. Also, you are responsible for ensuring that your project complies with the rules of your university/institution, and with the laws of your nation.</p></li>
+
−
        </ul>
+
 
</div>
 
</div>
 +
 +
<div class="column half_size">
 +
<p>
 +
Once the iGEM Safety Committee has approved your Check-In by email, you may begin working with the material (organism or part). You may Check-In for as many organisms/parts as you wish, and any team member may send a Check-In at any time until the Jamboree.</p>
 
</div>
 
</div>
  
−
</html>{{HTML/Temp/FormTitleAndMode}}<html>
 
  
−
<div id="formbody" class="bordered">
+
 
 +
 
 +
 
 +
<div class="clear extra_space"></div>
 +
 
 +
<div class="column full_size">
 +
 
 +
 
 +
 
 +
 
 +
<div class="expand_content first"> <h2>Frequently Asked Questions about Check-Ins</h2> </div>
 +
<div class="expand_content control_button"> </div>
 +
<div class="expand_content more">
 +
 
 +
 
 +
 
 +
<div class="column half_size">
 +
<h5> What if I am unsure whether my organism/part requires a Check-In?</h5>
 +
<p>Ask us! Email safety AT igem DOT org to ask questions about what requires a Check-In. Or, because the Check-In form is short and easy, you can submit a Check-In even if you are unsure whether it is necessary.</p>
 +
 
 +
<br>
 +
 
 +
<h5>We want to do a little preliminary work with an organism/part, but we might not use it for our final project. Do we still have to Check-In before we acquire the organism/part?</h5>
 +
<p>Yes! Please Check-In for every organism/part you want to acquire that is not on the White List, even if you will not use it in your final project. You can tell us in the "Further Comments" section that it is not for your final project, or that you are unsure. We have made the Check-In form short and easy, so you can Check-In for many parts, even ones you are not sure about using.</p>
 +
 
 +
<br>
 +
 
 +
<h5>Uh-oh! We misunderstood the White List, and we already started working with an organism/part that requires a Check-In. What do we do?</h5>
 +
<p>Just let us know. Email safety AT igem DOT org to describe the situation, and send us a Check-In promptly. Tell us in the "Further Comments" section what you have done with the organism/part already.</p>
 +
 
 +
</div>
 +
 
 +
<div class="column half_size">
 +
 
 +
<h5> We are going to use a lot of parts. May we combine them on a single Check-In?</h5>
 +
<p>If the parts all come from the same parent organism, you may combine them on a single Check-In, but make sure you give complete information about each part. If the parts come from different parent organisms, please send separate Check-Ins.</p>
 +
 
 +
<br>
 +
 
 +
<h5> You approved our Check-In for an organism/part. Do we still need to ask our university/institution about it? What about checking local laws?</h5>
 +
<p>Yes! The iGEM Safety Committee does not replace institutional review boards, or your local government. You are responsible for obtaining from your university or government any approvals that might be necessary. Your university or government might have different rules about what organisms/parts require special approval.</p>
 +
 
 +
<br>
 +
 
 +
<h5>We are only using organisms/parts from the White List, and therefore we do not need to submit any Check-Ins. Do we still need to ask our university/institution about our project? What about checking local laws?</h5>
 +
<p>Yes! Again, the iGEM Safety Committee does not replace institutional review boards, or your local government. Even if you are only using organisms/parts that are generally considered "safe", you still have the responsibility to follow good laboratory procedures. Also, you are responsible for ensuring that your project complies with the rules of your university/institution, and with the laws of your nation.</p>
 +
 
 +
</div>
 +
 
 +
</div>
 +
 
 +
<div class="clear extra_space"></div>
 +
 
 +
 
 +
 
 +
 
 +
 
 +
<div class="admins_only" id="admin_link">
 +
<p>Orange stuff is only visible to wiki superusers (<a href="#" id="hide_admin">hide orange stuff</a>)</p>
 +
<p><b><a class="change_mode" data-mode="admin">Go to Admin Mode</a></b> / <a class="change_team" data-team="1874">Go to Team Example</a> / Go to Username: <input type="text" id="author_select" autocomplete="off"></p>
 +
</div>
 +
 
 +
 
 +
 
 +
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 +
 
 +
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 +
 
 +
THIS IS WHERE THE FORM BEGINS
 +
 
 +
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 +
 
 +
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
 +
 
 +
 
 +
<div class="column full_size" style="text-align:center; margin:auto;"><h1> Safety Check In Form </h1> </div>
 +
<div class="clear"></div>
 +
<div class="line_divider"></div>
 +
 
 +
<div id="formbody">
 +
 
 +
<fieldset>
 +
 
 +
<h2>1.- Team Selection </h2>
 +
 
 +
 
 +
 
 +
<div id="formtitlemodewrapper" class="column half_size">
 +
<p class="question">
 +
<!-- <span id="form_title_display"></span> --> <span id="owner_name_display"></span> <span id="prompt_to_choose_team"> Please choose a team</span>
 +
</p>
 +
 
 +
<h4 id="modes"></h4>
 +
 
 +
<select id="team_list_dropdown">
 +
<option id="no_team_selected" value="">Choose team...</option>
 +
</select>
 +
 
 +
 
 +
<div id='aj_form_errors'> </div>
 +
 
 +
</div>
 +
 
 +
 
 +
 
 +
 
 +
<div id="submitted_warning"  class="column half_size">
 +
<p>This form has been submitted.</p>
 +
<p>You can <a href="#" id="popwin_unsubmit">unsubmit the form</a> if you wish to make further edits.</p>
 +
<p><a href="#" id="popwin_dismiss">Click here to dismiss this message</a></p>
 +
</div>
 +
 
 +
 
 +
</fieldset>
 +
 
 +
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 +
 
 +
GENERAL INFORMATION
 +
 
 +
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
 +
 
 +
 
 +
<fieldset>
 +
 
 +
<h2>2.- Check In Information </h2>  
  
 
<div>
 
<div>
Line 124: Line 226:
 
<p style="text-align: center;"><button type="button" id="start_new_sub_form">Start New Check-In</button></p>
 
<p style="text-align: center;"><button type="button" id="start_new_sub_form">Start New Check-In</button></p>
 
</div>
 
</div>
 +
 +
</fieldset>
  
 
<div class="clear"></div>
 
<div class="clear"></div>
 +
 +
 +
 +
 +
<!-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 +
 +
TEAM MEMBER
 +
 +
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
 +
 +
 +
 +
 
<fieldset>
 
<fieldset>
−
<legend class="qnum">Team member who should be contacted about this Check-In:</legend>
+
 
 +
<h2>3.- Contact Information </h2>
 +
<div id="private_contact_information">
 
<p>Name <input type="text" name="Team member Name" data-form-field="corr_team_member_name"></p>
 
<p>Name <input type="text" name="Team member Name" data-form-field="corr_team_member_name"></p>
 
<p>Email <input type="text" name="Team member Email" data-validate-as="email" class="validate-on-change" data-form-field="corr_team_member_email"></span></p>
 
<p>Email <input type="text" name="Team member Email" data-validate-as="email" class="validate-on-change" data-form-field="corr_team_member_email"></span></p>
 +
</div>
 
</fieldset>
 
</fieldset>
 +
 +
 +
 +
  
 
<fieldset>
 
<fieldset>
−
<legend class="qnum">1. Organism Information: <span id="organism_name_display"></span></legend>
 
  
−
<p class="question"><span class="qnum">a)</span> What Risk Group is this organism? <a target="_blank" href="https://2016.igem.org/Safety/Risk_Groups">[Help about Risk Groups]</a></p>
+
<h2>4.- Organism Information</h2>
  
−
<div id="why_not_rg4">
+
<p class="question"><span class="qnum">a)</span> What Risk Group is this organism? <a target="_blank" href="https://2017.igem.org/Safety/Risk_Groups">[Help about Risk Groups]</a></p>
−
<p>iGEM teams should not use:</p>
+
 
−
<ul>
+
<div class="column half_size">
−
<li>Risk Group 3 organisms</li>
+
−
<li>Risk Group 4 organisms</li>
+
−
<li>Parts derived from Risk Group 4 organisms</li>
+
−
</ul>
+
−
<p>If you are planning to use any of these, contact safety (AT) igem (DOT) org right away!!</p>
+
−
</div>
+
  
 
<ul>
 
<ul>
Line 156: Line 273:
 
<li><label><input type="radio" name="1. a) Organism Risk Group" data-form-field="organism_risk_group" value="rg_unknown"> Unknown (please comment):</label> <textarea rows="2" name="Unknown Risk Group (comment)" data-form-field="rg_unknown_describe" data-validation="[value=rg_unknown]"></textarea></li>
 
<li><label><input type="radio" name="1. a) Organism Risk Group" data-form-field="organism_risk_group" value="rg_unknown"> Unknown (please comment):</label> <textarea rows="2" name="Unknown Risk Group (comment)" data-form-field="rg_unknown_describe" data-validation="[value=rg_unknown]"></textarea></li>
 
</ul>
 
</ul>
 +
</div>
 +
 +
<div class="column half_size message_box">
 +
<p>iGEM teams should not use:</p>
 +
<ul>
 +
<li>Risk Group 3 organisms</li>
 +
<li>Risk Group 4 organisms</li>
 +
<li>Parts derived from Risk Group 4 organisms</li>
 +
</ul>
 +
<p>If you are planning to use any of these, contact safety (AT) igem (DOT) org right away!!</p>
 +
</div>
 +
 +
<div class="clear"></div>
 +
 +
  
 
<br />
 
<br />
 
<p class="question"><span class="qnum">b)</span> Is the organism on the <a href="http://australiagroup.net/en/human_animal_pathogens.html">Australia Group List</a>, or on the <a href="http://www.selectagents.gov/SelectAgentsandToxinsList.html">U.S. Select Agents and Toxins List</a>?</p>
 
<p class="question"><span class="qnum">b)</span> Is the organism on the <a href="http://australiagroup.net/en/human_animal_pathogens.html">Australia Group List</a>, or on the <a href="http://www.selectagents.gov/SelectAgentsandToxinsList.html">U.S. Select Agents and Toxins List</a>?</p>
−
<p>If Yes, please email safety (at) igem (dot) org. These organisms and their parts are restricted for international shipment. See <a href="https://2016.igem.org/Safety/What_is_Safety#Shipment">Safe Shipment</a> for more information.</p>
+
<p>If Yes, please email safety (at) igem (dot) org. These organisms and their parts are restricted for international shipment. See <a href="https://2017.igem.org/Safety/What_is_Safety#Shipment">Safe Shipment</a> for more information.</p>
 
<textarea rows="2" name="1. b) International Shipment Restrictions" data-form-field="on_restricted_lists"></textarea>
 
<textarea rows="2" name="1. b) International Shipment Restrictions" data-form-field="on_restricted_lists"></textarea>
 +
 +
 +
 
</fieldset>
 
</fieldset>
  
 
<fieldset>
 
<fieldset>
−
<legend class="qnum">2. Part Information: <span id="part_name_display"></span></legend>
+
<h2> 5. Part Information </h2>  <span id="part_name_display"></span>
 +
 
 
<div id="part_information_fieldset_inner">
 
<div id="part_information_fieldset_inner">
 
<p class="question"><span class="qnum">a)</span> What is the natural function of this part in its parent organism?</p>
 
<p class="question"><span class="qnum">a)</span> What is the natural function of this part in its parent organism?</p>
Line 175: Line 311:
  
 
<br />
 
<br />
−
<p class="question"><span class="qnum">c)</span> Is it a virulence factor, or does it mimic one? <a target="_blank" href="https://2016.igem.org/Safety/What_is_Safety#Lab_Work">[Help about Virulence Factors]</a></p>
+
<p class="question"><span class="qnum">c)</span> Is it a virulence factor, or does it mimic one? <a target="_blank" href="https://2017.igem.org/Safety/What_is_Safety#Lab_Work">[Help about Virulence Factors]</a></p>
 
<textarea rows="3" name="2. c) Is the Part a Virulence Factor?" data-form-field="part_virulence_factor" data-validation="[data-form-field=sub_form_whole_or_part][value=part]"></textarea>
 
<textarea rows="3" name="2. c) Is the Part a Virulence Factor?" data-form-field="part_virulence_factor" data-validation="[data-form-field=sub_form_whole_or_part][value=part]"></textarea>
 
 
Line 181: Line 317:
 
<p class="question"><span class="qnum">d)</span> Does the part, by itself, pose any safety risks? If Yes, what are the risks?</p>
 
<p class="question"><span class="qnum">d)</span> Does the part, by itself, pose any safety risks? If Yes, what are the risks?</p>
 
<textarea rows="3" name="2. d) Part Risks" data-form-field="part_risks" data-validation="[data-form-field=sub_form_whole_or_part][value=part]"></textarea>
 
<textarea rows="3" name="2. d) Part Risks" data-form-field="part_risks" data-validation="[data-form-field=sub_form_whole_or_part][value=part]"></textarea>
 +
 +
 +
<p class="question"><span class="qnum">e)</span> Does the part, when combined with other parts, pose any safety risks? If Yes, what are the risks? </p>
 +
<textarea rows="3" name="2. d) Part Risks" data-form-field="part_risks_combined" data-validation="[data-form-field=sub_form_whole_or_part][value=part]"></textarea>
 +
 +
 +
 
</div>
 
</div>
−
</fieldset>
 
  
−
<br />
 
 
<p class="question"><span class="qnum">3.</span> What will you use this organism/part for?</p>
 
<p class="question"><span class="qnum">3.</span> What will you use this organism/part for?</p>
 
<p>How does it fit into the overall function of your project?</p>
 
<p>How does it fit into the overall function of your project?</p>
Line 213: Line 354:
 
<textarea rows="2" data-validation="optional" name="7. Comments about this form" data-form-field="comments_about_this_form"></textarea>
 
<textarea rows="2" data-validation="optional" name="7. Comments about this form" data-form-field="comments_about_this_form"></textarea>
  
−
<br />
+
 
−
<br />
+
</fieldset>
 +
 
 +
<fieldset>
 +
 
 +
 
 
<div class="submit_buttons_box">
 
<div class="submit_buttons_box">
−
<p class="question">Finished? <input type="submit" data-form-field="submit" value="Submit Form"></p>
+
<h2> 6.- Sign off </h2>
−
<p class="question">Need to make changes? <input type="submit" data-form-field="return_form" value="Unsubmit Form"></p>
+
 
−
<p class="question">Want to erase this Check-In? <input type="submit" data-form-field="delete_form" value="Delete Form"></p>
+
<div class="column third_size" style="text-align:center; margin:auto;">
 +
<p class="question">Finished? <br><br>
 +
 
 +
<input type="submit" data-form-field="submit" value="Submit Form"></p>
 
</div>
 
</div>
−
<br />
+
<div class="column third_size" style="text-align:center; margin:auto;">
 +
<p class="question">Need to make changes? <br> <br>
  
 +
<input type="submit" data-form-field="return_form" value="Unsubmit Form"></p>
 +
</div>
 +
<div class="column third_size" style="text-align:center; margin:auto;">
 +
<p class="question">Want to erase this Check-In? <br><br>
 +
<input type="submit" data-form-field="delete_form" value="Delete Form"></p>
 +
</div>
 +
 +
</div>
 +
</fieldset>
 
</html>{{HTML/Temp/FormsAdmin}}<html>
 
</html>{{HTML/Temp/FormsAdmin}}<html>
  
Line 229: Line 387:
 
</div> <!-- End oneColumn -->
 
</div> <!-- End oneColumn -->
 
</html>
 
</html>
−
{{2016Bottom}}
 
 
<html>
 
<html>
 
<script type="text/javascript">
 
<script type="text/javascript">

Latest revision as of 09:09, 26 June 2017

MENU
Loading...


You have JavaScript disabled.

This page requires JavaScript in order to function correctly. Please enable JavaScript in your browser, then try again.

Safety Check-Ins

Submit a Check-In before you acquire or use any organism or part that is not on the White List.

Check-Ins are a way for you to quickly and easily ask iGEM's safety experts to review your plans for safely acquiring and using a higher risk organism/part, and to approve your plans or suggest changes.

  • We encourage STUDENTS, instead of instructors, to complete this form.
  • While you type, this form will remember your answers. When you are finished, press the "Submit" button at the bottom to send your form to the iGEM Safety Committee.
  • If you need help, or if you are unsure whether an organism/part requires a Check-In, email safety (at) igem (dot) org to ask.

You should submit a Check-In before you acquire or use certain materials in your lab. Specifically, you should send us a Check-In for any organism or part that is not on the White List. We expect to reply to most Check-Ins within a few days at most.

Once the iGEM Safety Committee has approved your Check-In by email, you may begin working with the material (organism or part). You may Check-In for as many organisms/parts as you wish, and any team member may send a Check-In at any time until the Jamboree.

Frequently Asked Questions about Check-Ins

What if I am unsure whether my organism/part requires a Check-In?

Ask us! Email safety AT igem DOT org to ask questions about what requires a Check-In. Or, because the Check-In form is short and easy, you can submit a Check-In even if you are unsure whether it is necessary.


We want to do a little preliminary work with an organism/part, but we might not use it for our final project. Do we still have to Check-In before we acquire the organism/part?

Yes! Please Check-In for every organism/part you want to acquire that is not on the White List, even if you will not use it in your final project. You can tell us in the "Further Comments" section that it is not for your final project, or that you are unsure. We have made the Check-In form short and easy, so you can Check-In for many parts, even ones you are not sure about using.


Uh-oh! We misunderstood the White List, and we already started working with an organism/part that requires a Check-In. What do we do?

Just let us know. Email safety AT igem DOT org to describe the situation, and send us a Check-In promptly. Tell us in the "Further Comments" section what you have done with the organism/part already.

We are going to use a lot of parts. May we combine them on a single Check-In?

If the parts all come from the same parent organism, you may combine them on a single Check-In, but make sure you give complete information about each part. If the parts come from different parent organisms, please send separate Check-Ins.


You approved our Check-In for an organism/part. Do we still need to ask our university/institution about it? What about checking local laws?

Yes! The iGEM Safety Committee does not replace institutional review boards, or your local government. You are responsible for obtaining from your university or government any approvals that might be necessary. Your university or government might have different rules about what organisms/parts require special approval.


We are only using organisms/parts from the White List, and therefore we do not need to submit any Check-Ins. Do we still need to ask our university/institution about our project? What about checking local laws?

Yes! Again, the iGEM Safety Committee does not replace institutional review boards, or your local government. Even if you are only using organisms/parts that are generally considered "safe", you still have the responsibility to follow good laboratory procedures. Also, you are responsible for ensuring that your project complies with the rules of your university/institution, and with the laws of your nation.

Safety Check In Form

1.- Team Selection

Please choose a team

This form has been submitted.

You can unsubmit the form if you wish to make further edits.

Click here to dismiss this message

2.- Check In Information

Choose an existing Check-In:

Or, start a new Check-In:

This Check-In is for a:

Organism name:
(Include name of species, strain, and/or cell line.)

(If this Check-In is for a part: Enter the name of the organism that the part originally comes from, not the name of the chassis organism that you will put the part into.)

3.- Contact Information

Name

Email

4.- Organism Information

a) What Risk Group is this organism? [Help about Risk Groups]

iGEM teams should not use:

  • Risk Group 3 organisms
  • Risk Group 4 organisms
  • Parts derived from Risk Group 4 organisms

If you are planning to use any of these, contact safety (AT) igem (DOT) org right away!!


b) Is the organism on the Australia Group List, or on the U.S. Select Agents and Toxins List?

If Yes, please email safety (at) igem (dot) org. These organisms and their parts are restricted for international shipment. See Safe Shipment for more information.

5. Part Information

a) What is the natural function of this part in its parent organism?


b) Is the part toxic to humans?

For example, a protein toxin such as Botox (Botulinum toxin), or if it is an enzyme that synthesizes a toxic small molecule.


c) Is it a virulence factor, or does it mimic one? [Help about Virulence Factors]


d) Does the part, by itself, pose any safety risks? If Yes, what are the risks?

e) Does the part, when combined with other parts, pose any safety risks? If Yes, what are the risks?

3. What will you use this organism/part for?

How does it fit into the overall function of your project?


4. How will you acquire this organism/part?

(e.g. from a culture collection, from another lab, isolating the part from the organism by PCR, ordering the part from a DNA synthesis company)


5. Are you taking any additional safety precautions when you use this organism/part?

(e.g. handling it in a separate lab area, wearing additional protective equipment)


6. Further Comments

Anything else you want to tell us about this organism/part and how you will use it


7. Comments about this form: Is it easy or difficult to use? Are the questions confusing?

6.- Sign off

Finished?

Need to make changes?

Want to erase this Check-In?

iGEM HQ Use Only

Form Status:     

Admin Comment: