Difference between revisions of "Team:Cadets2Vets"

Line 530: Line 530:
 
a:"View+%2FTeam%3AUofC_Calgary%2FIntegrated_Practices++View source+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dedit++History+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dhistory++Watch+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dwatch%26token%3D5070978bcdc390d663b782a9e51ba355%252B%255C++Page+%2FTeam%3AUofC_Calgary%2FIntegrated_Practices++Discussion+%2Fwiki%2Findex.php%3Ftitle%3DTalk%3ATeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dedit%26redlink%3D1++" });
 
a:"View+%2FTeam%3AUofC_Calgary%2FIntegrated_Practices++View source+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dedit++History+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dhistory++Watch+%2Fwiki%2Findex.php%3Ftitle%3DTeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dwatch%26token%3D5070978bcdc390d663b782a9e51ba355%252B%255C++Page+%2FTeam%3AUofC_Calgary%2FIntegrated_Practices++Discussion+%2Fwiki%2Findex.php%3Ftitle%3DTalk%3ATeam%3AUofC_Calgary%2FIntegrated_Practices%26action%3Dedit%26redlink%3D1++" });
 
</script>
 
</script>
 +
 +
<div id="content" class="mw-body" role="main">
 +
    <a id="top"></a>
 +
 +
            <div id="top_title">
 +
                <div class="logo_2016">
 +
                    <a href="https://2016.igem.org">
 +
                    <img src="https://static.igem.org/mediawiki/2016/8/8b/HQ_page_logo.jpg" width="100px">
 +
                    </a>
 +
                </div>
 +
 +
        <h1 id="firstHeading" class="firstHeading">
 +
            <span dir="auto">Team:UofC Calgary/Integrated Practices</span>
 +
        </h1>
 +
            </div>
 +
 +
            <div id="HQ_page">
 +
                <div id="bodyContent">
 +
            <div id="mw-content-text" lang="en" dir="ltr" class="mw-content-ltr"><p>
 +
<style>
 +
 +
/* Reset the wiki style by overriding with a reset stylesheet (written by Florian Albrecht)
 +
  the relevant wiki css rules are reset by using rules with higher priority */
 +
 +
 +
/* Start general reset ================================================== */
 +
 +
html body {
 +
    font-size: inherit;
 +
    font-family: inherit;
 +
    background-color: transparent;
 +
    color: inherit;
 +
    padding: 0;
 +
}
 +
 +
div#globalWrapper {
 +
    font-size: inherit;
 +
    margin: 0;
 +
    padding: 0;
 +
    position: static;
 +
    width: auto;
 +
}
 +
 +
 +
/* Start top-section reset ============================================== */
 +
 +
div#top-section {
 +
    border: 0;
 +
    height: auto;
 +
    margin: 0;
 +
    position: static;
 +
    width: auto;
 +
}
 +
 +
div#p-logo {
 +
    height: auto;
 +
    position: static;
 +
    width: auto;
 +
    z-index: auto;
 +
}
 +
 +
div#p-logo a, div#p-logo a:hover {
 +
    text-decoration: none;
 +
}
 +
 +
div#menubar {
 +
    font-family: inherit;
 +
    font-size: inherit;
 +
    line-height: inherit;
 +
    position: static;
 +
    top: 0px;
 +
    white-space: normal;
 +
    width: auto;
 +
    z-index: auto;
 +
}
 +
 +
div.left-menu, div.left-menu a {
 +
    color: inherit;
 +
    left: 0;
 +
    text-align: left;
 +
    text-transform: none;
 +
}
 +
 +
div#menubar ul {
 +
    color: inherit;
 +
    list-style: disc outside none;
 +
    margin: 0;
 +
    padding: 0;
 +
}
 +
 +
div#menubar li {
 +
    cursor: auto;
 +
    display: list-item;
 +
    padding: 0;
 +
    margin: 0;
 +
    position: static;
 +
}
 +
 +
div.left-menu li a {
 +
    padding: 0;
 +
}
 +
 +
div.left-menu:hover {
 +
    color: inherit;
 +
    background-color: transparent;
 +
}
 +
 +
div.left-menu:hover a {
 +
    color: inherit;
 +
}
 +
 +
div.right-menu, div.right-menu a {
 +
    color: inherit;
 +
    right: 0;
 +
    text-align: left;
 +
}
 +
 +
div.right-menu li a {
 +
    background-color: transparent;
 +
    color: inherit;
 +
    padding: 0;
 +
}
 +
 +
div.right-menu li a:hover {
 +
    color: inherit;
 +
    text-decoration: none;
 +
}
 +
 +
div#search-controls {
 +
    background-color: transparent;
 +
    height: auto;
 +
    position: static;
 +
    right: 0;
 +
    text-align: left;
 +
    top: 0;
 +
    width: auto;
 +
    z-index: auto;
 +
}
 +
 +
 +
/* Start content reset ================================================== */
 +
 +
div#content {
 +
    background: transparent;
 +
    border: 0;
 +
    color: inherit;
 +
    line-height: inherit;
 +
    margin: 0;
 +
    padding: 0;
 +
    position: static;
 +
    width: auto;
 +
    z-index: auto;
 +
}
 +
 +
body li {
 +
    margin: 0;
 +
}
 +
 +
body h1, body h2, body h3, body h4, body h5, body h6 {
 +
    background: transparent;
 +
    border: 0;
 +
    color: inherit;
 +
    padding: 0;
 +
}
 +
 +
body .firstHeading {
 +
    margin: 0;
 +
}
 +
 +
div#contentSub {
 +
    color: inherit;
 +
    font-size: inherit;
 +
    line-height: inherit;
 +
    margin: 0;
 +
    width: auto;
 +
}
 +
 +
div#catlinks {
 +
    background-color: transparent;
 +
    border: 0;
 +
    clear: both;
 +
    margin: 0;
 +
    padding: 0;
 +
}
 +
 +
 +
/* Start footer reset =================================================== */
 +
 +
div#footer-box {
 +
    background-color: transparent;
 +
    border: 0;
 +
    margin: 0;
 +
    padding: 0;
 +
    width: auto;
 +
}
 +
 +
div#footer {
 +
    color: inherit;
 +
    font-size: inherit;
 +
    text-align: left;
 +
}
 +
 +
div#f-poweredbyico, div#f-copyrightico {
 +
    float: none;
 +
}
 +
 +
div#footer li {
 +
    margin: 0;
 +
    display: list-item;
 +
}
 +
</style>
 +
<style>
 +
#sideMenu{
 +
            width: 200px;
 +
    position: absolute;
 +
    top: 20px;
 +
    left: 1020px;
 +
    z-index: 10;
 +
    padding-top: 0px;
 +
    padding-bottom: 15px;
 +
    padding-left: 15px;
 +
    padding-right: 15px;
 +
    background-color: white;
 +
    text-align: left;
 +
display: none;
 +
z-index: 9996;
 +
}
 +
#content{
 +
width: 100%;
 +
        padding: 0px;
 +
        margin-left: 0px;
 +
}
 +
#top_title{
 +
overflow: hidden;
 +
display: none;
 +
}
 +
#top_menu_14{
 +
height: 20px;
 +
}
 +
#top_menu_under{
 +
height: 0px;
 +
}
 +
#globalWrapper{
 +
      padding-bottom: 20px;
 +
}
 +
#HQ_page p {
 +
    font-size: 16px;
 +
}
 +
</style>
  
 
</html>
 
</html>

Revision as of 17:13, 9 June 2017

HOME
TEAM
PROJECT
Description
Design
Experiments
Notebook
InterLab
Contribution
Model
Results
Demonstrate
Improve
Attributions
PARTS
Parts
Basic Parts
Composite Parts
Part Collection
SAFETY
HUMAN PRACTICES
Silver HP
Integrated and Gold
Public Engagement
AWARDS
Applied Design
Entrepreneurship
Hardware
Measurement
Model
Plant
Software
JUDGING FORM

Cadets2Vets

INTEGRATED PRACTICES
Read More
×

Loading ...

Welcome to iGEM 2017!

Your team has been approved and you are ready to start the iGEM season!

Before you start:

Please read the following pages:

Styling your wiki

You may style this page as you like or you can simply leave the style as it is. You can easily keep the styling and edit the content of these default wiki pages with your project information and completely fulfill the requirement to document your project.

While you may not win Best Wiki with this styling, your team is still eligible for all other awards. This default wiki meets the requirements, it improves navigability and ease of use for visitors, and you should not feel it is necessary to style beyond what has been provided.

Wiki template information

We have created these wiki template pages to help you get started and to help you think about how your team will be evaluated. You can find a list of all the pages tied to awards here at the Pages for awards link. You must edit these pages to be evaluated for medals and awards, but ultimately the design, layout, style and all other elements of your team wiki is up to you!

Editing your wiki

On this page you can document your project, introduce your team members, document your progress and share your iGEM experience with the rest of the world!

Use WikiTools - Edit in the black menu bar to edit this page

Tips

This wiki will be your team’s first interaction with the rest of the world, so here are a few tips to help you get started:

Inspiration

You can also view other team wikis for inspiration! Here are some examples:

Uploading pictures and files

You can upload your pictures and files to the iGEM 2017 server. Remember to keep all your pictures and files within your team's namespace or at least include your team's name in the file name.
When you upload, set the "Destination Filename" to
T--YourOfficialTeamName--NameOfFile.jpg. (If you don't do this, someone else might upload a different file with the same "Destination Filename", and your file would be erased!)

UPLOAD FILES

iGEM : Integrated practices

Integrated Human Practices

Our human practices reflection is based on the interactions between the conception of our device and the society. How could our work be integrated in the prevention of STIs? The goal was to conduct a rigorous reflexion on the project. First we used the knowledge acquired during meetings and surveys we carried to build an ethical matrix.
The help provided by our human sciences instructors was very valuable as they guided us through interesting ways of thinking.

Ethical matrix - Click to enlarge

Once the matrix was established, on the one hand, we confronted it with the results of the survey in the matrix synthesis.
On the other hand, it was used as an instrument to have a human overview of the project to take a needed step back as everyone was focused on its parts. An ethical matrix was a useful framework to assist us in our deliberation about technical choices but also social choices.

The matrix synthesis was realized to have a humanist point of view integrated into our project. In this perspective, we used the approach of the ethic of care (Joan Tronto, Moral boundaries: a political argument for ethic of care, 1993) to interpret our results.
We identified 4 statements: innovation, perception, risk, responsibility to improve our project according to two phases of the ethic of care.

CARING ABOUT

The innovation deals with human consequences of our technology.
Early detection, short delivery time of results, low cost impact the use of the diagnosis. The early detection allows to improve patient's care, thus the treatment can begin very early. The short delivery time of results is compatible with mobile prevention campaign and emergency situations. Low cost is for better test accessibility and increase the user population. All those decisions were made to develop an attractive test that would answer the technical expectations of healthcare professional.

The perception of the test by the user was also analyzed to establish the preliminary basis of acceptability issues. The human relationship of the user during the test realization and the management of intimacy were our main reflection axis.

TAKING CARE OF

Integration of the risks was also necessary. We identified 3 major risks. The contamination risk implies to use safe biological materials. The reliability deals with false positive and false negative. It is a technical issue that is related to our technology. The goal is to reduce them as much as possible. The use decay risk introduced by the user.

The risk principle results in the concept of responsibility. Support is good way to reduce those risks, being supervised by the medical staff can be very reassuring during the test execution. The announcement of the results also questions the presence of medical staff according to the serious consequences of some STIs. The easy access and the simplicity of use are necessary to guarantee an equal right to get diagnosed.
Nowadays, the responsibility is not restricted to the user, it must also respect the environment. That’s what motivated our technical choices for the device.

The matrix was also intended to be a decision helper tool. It was very useful when taking important decision (e.g. changing the revelation system).
Matching technical solutions to ethical values (accessibility, respect of the user, biosafety) can be really complex but stimulating!

Decisions taken thanks to the matrix


Sample choices: blood for a non invasive test and easily standardized sample.
Materials choices: paper, biosourced plastic…for an eco friendly cycle of life.
Early-detection: RT instead of the p24 to detect the early stage infection of HIV.
Reliability: a system that minimizes the false negative risk by using two epitopes instead of one.
Usability: redaction of a usernote to improve the user experience.
Biosafety: latex beads instead of RT proteins or HbSAg as bio-safe migration controls.

This work can serve as an inspiring example to other 2016 iGEM teams: Stanford-Brown and Michigan. We could organize an ethical debate about our technology. Our work on an ethical matrix is documented but there are still a lot of questions (writen in red in the matrix). With others, we can build upon to answer to doubt.
We were able to come up with a device that combines the expertise of physicians specializing in STIs, potential patients’ expectations, curiosity and foresight of young engineering students. So this device can be usable and useful.

footer id="footer">



Designed by Team iGEM Cadets2Vets

×

Loading ...

iGEM : Integrated practices

Team:INSA-Lyon/Integrated Practices

Loading menubar.....

Team:INSA-Lyon/Integrated Practices

Team:UofC Calgary/Integrated Practices - 2016.igem.org

Loading menubar.....

Team:UofC Calgary/Integrated Practices