"
Team:Wellesley HCI/Safety
From 2012.igem.org
Safety
1. Would any of your project ideas raise safety issues in terms of:
researcher safety,
The Wellesley Human-Computer Interaction team is a computational team, and worked on designing software that not only improve clarity and efficiency in designing synthetic biological parts, but also increase public awareness through education of the next-generation of scientists through outreach.
public safety,
To foster appreciation of laboratory processes and understand common safety concerns raised by synthetic biologists, our computational team received hands-on training at the Synthetic Biology Center at MIT. We carried out two separate experiments inspired by a previous iGEM experiments: Eau d’Coli and e.Chromi; and learned a lot of the basic lab techniques biology students in introductory cellular biology laboratories. We also discussed extensively safety concerns in the field, from everyday technical concerns (e.g. labeling petri dishes, the correct to remove gloves) to recently implemented policies (considering public and environmental safety). From the training we began to appreciate the challenges and troubleshooting methods involved with working in a synthetic biology lab and realized the importance of communication and collaboration. The themes of communication and collaboration were emphasized in the design and testing of the MoClo Planner. We designed our software and user studies for testing with paired collaborators and took meticulous notes of the communication and collaborative techniques students used in designing their biological constructs.
environmental safety?
In addition to wet lab training, various domain experts were interviewed throughout the summer and fall semester, from synthetic biology lab instructors and professors to pharmaceutical lab technicians and patent officers on the ethics, biosafety, and biosecurity concerns involved in designing, implementing, and testing synthetic biology software with human users (see Acknowledgements). The questions and concerns raised in our dialogue with domain experts informed our design process greatly, and also made us realize that greater education and public awareness were needed. We were inspired to create an art project, SynFluo (link to SynFluo) that educated high school students on the theory and basic safety concerns of biological contamination in a wet-lab environment. We presented SynFluo to Framingham High School and MIT/Wellesley Upward Bound summer program students. We allowed them to brainstorm and ask questions on the safety concerns involved in synthetic biology experimentation. SynFluo allowed students to kinesthetically work with Microsoft Surfaces and manipulate Sifteo cubes which simulated working with E.Chromi experiment. An animated contamination could also be simulated; allowing students to appreciation basic biosafety issues and understand the severity of impact if safety regulations are not followed.
2. Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues?
As a computational team, we did not create new BioBrick devices, but simulated the hierarchical creation of these devices in the MoClo Planner software. In effect, laboratory safety can be increased by exposure to software simulating synthetic biology experiments, as our user study student subjects expressed increased understanding and appreciation of both the theory and technical aspects of Golden Gate Modular Cloning after testing the MoClo Planner software. Various errors and warning messages were created in the software itself to educate students on how to create a BioBrick which were refined with each user study. We used Eugene, a software program created by the Densmore Lab at Boston University, as part of the back-end algorithm for creating rules and generating permutations of biological parts in Level 1 of our program. In addition, we created our own software rules in the primer designer regulating the use of fusion sites and the order of our synthetic biology constructs as they become Level 2 modules (see Design). While we did not create concrete BioBrick parts, our efforts indirectly inspire safer creation of BioBricks in the future.
3. Is there a local biosafety group, committee, or review board at your institution?
The Institutional Biosafety Committee, under the Wellesley College Office of Environmental Healthy & Safety regulates biosafety concerns on campus. However, we are a computational team and do not work with biological organisms or hazards in our local lab environment.
The Wellesley Human-Computer Interaction lab does test iterations of our software projects with human subjects. Before each testing session, participants were asked to sign consent forms detailing the voluntary nature of the study, the task involved in the study, and informed the participants that if at any time during the study they experienced discomfort they are permitted to stop and leave. We were extremely sensitive to a user’s physical, mental, and emotional demands during each study, taking notes on physical and verbal cues from students; we were very assuring during the study, and informed our users that any crashes or technical difficulties were our fault as designers and programmers and in no way their fault or responsibility. After each study the user task was altered or refined further to clarify the task and increase student comfort in testing out our software project, and participants were compensated with gift cards as appreciation for their assistance.
4. Do you have any other ideas 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?
An overall trend we noticed this summer in dealing with safety concerns in the wet-lab is that communication, collaboration, and proper documentation of experimental procedures and data all have important impacts on the success of synthetic biology experiments. We have documented all our software concerns and videos concerning safety in our iGEM 2012 website, to allow for intuitive use of our software and for future references to computational teams, and encourage iGEM teams of both wet-lab and computational tracks to document their research meticulously.
