CS6440

Introduction to Health Informatics

Deliverable 0

Team Formation (A) & Team Confirmation (B)

(This page is subject to change. Note it does not technically open until Week 3)

Deliverable 0 has two parts – Part A and Part B. Complete these assignments by providing the following information listed below and submit as a PDF. (NOTE TO CAMPUS STUDENTS – There are a few differences for you regarding these deliverables, refer to Dr. Duke in class for more details).

Team Formation (A)

Due: January 27, 2019 by 11:59PM UTC-12.

Submit your Team Formation Assignment as a PDF (“Team Formation – <Last Name, First Name>.pdf” format) via Canvas.

IF YOU DO NOT HAVE A TEAM: You are responsible for finding/forming a team. If you do not have a team by the deadline of this deliverable, you will be manually paired by the TAs. You will be paired with whomever is left to pair with – those of which may not be in your time zone, have your preferences, and so on. It is in your best interest to find a team. Do not rely on the TAs to pair you, as you will most likely not get your team until much later than everyone (plus the statement before). You must list “NO TEAM” underneath “Team Members”. You are still expected to put Team Name, list your email, domain, Github user name, etc. even if you are not in a team – For the project role, list the roles you prefer in order.

You are not expected to have a topic at this point, because they have not been released just yet!

Provide the following information:

  • Team Name – You must have a team name.
  • Team Members (First, Last, GT Username, GT Github Username) – can list this in a table, list or whatever makes the most sense to you. **
  • Team GT emails (non-alias)
  • Team Preferred emails
  • Project Roles: Developer, QA, Project Manager (these are the core roles)
  • Technical Expertise: Development (you must be specific, with languages, etc. Do not just type Development), HCI (you must be specific with your experience, do not just type HCI), Healthcare (you must be specific with your experience, do not just type healthcare), etc. of the team as a whole. **
  • Top 3 Times everyone can meet (in the EST time zone) **
  • **(Optional) List your Geographic location for each team member. This is important for project bidding.**
  • **(Optional) List any IP restrictions you may or may not have. This is important for project bidding.**
  • Primary Form of contact (ie, Piazza, Slack, G+, Phone, etc.)
  • Secondary Form of Contact (ie, Piazza, Slack, G+, Phone, etc.) Everyone on the Team must submit this assignment. You should work together as a team to answer the questions, but you are to submit it individually.
  • Submit your Team Formation Assignment as a PDF (“Team Formation – <Last Name, First Name>.pdf” format) via Canvas. By: January 27, 2019 at 11:59PM UTC-12, to secure your teams.

During Week 4, the week after you have submitted Team Formation (A), your teams will be confirmed and you all will see the project topics populate here. At this time you and your teammates need to take the time to review the projects and their requirements carefully, to prepare for Team Confirmation (B).

 

Team Confirmation (B)

Due: February 10, 2019 by 11:59PM UTC-12

Submit your Team Confirmation Assignment as a XLS (“Team Confirmation – Team Name.xls” format) via Canvas.

By now, you should have a team, with a chosen topic and domain. You will lose points if you submit this assignment and do not have a team. The only exceptions to this are those established by the team of instructors and the student, prior to the due date of this assignment. They will be told they are are part of the exception, hence if you have to ask, then you are not included in this exception.

Provide the following information:

  • Team Name – You must have a team name.
  • Team Members (First, Last, GT Username, GT Github Username) – can list this in a table, list or whatever makes the most sense to you. **
  • Team GT emails (non-alias)
  • Team Preferred emails
  • Top 10 Preferred Project Topics (whether they are related to External/TA mentors or your own idea)** You must list the project number and name(if you are listing a External/TA mentor project).
  • Your Topic’s Domain (if you have an approved and confirmed topic) Check Piazza for more information on domains.
  • Project Roles: Developer, QA, Project Manager (these are the core roles)
  • Technical Expertise: Development (you must be specific, with languages, etc. Do not just type Development), HCI (you must be specific with your experience, do not just type HCI), Healthcare (you must be specific with your experience, do not just type healthcare), etc. of the team as a whole. **
  • Top 3 Times everyone can meet (in the EST time zone) **
  • **(Optional) List your Geographic location for each team member. This is important for project bidding.**
  • List any IP restrictions you may or may not have. This is important for project bidding.**
  • Primary Form of contact (ie, Piazza, Slack, G+, Phone, etc.)
  • Secondary Form of Contact (ie, Piazza, Slack, G+, Phone, etc.) Everyone on the Team must submit this assignment. You should work together as a team to answer the questions, but you are to submit it individually.
  • Submit your Team Confirmation Assignment as a XLS (“Team Confirmation – Team Name.xls” format) via Canvas. By: February 10, 2019 at 11:59PM UTC-12, to secure your teams.

 

Example Submission:   Team-Formation-Template

Team name Best Example Team 
Preferred Project Topics 1.            Project 12 Concussion and traumatic brain injury in pediatric patients
2.            Project 27 Identification of Patients Requiring Statin Therapy
3.            Project 43 Blood pressure screening: adults
4.            Project 42 Healthy diet and physical activity counseling to prevent cardiovascular 
disease: adults with cardiovascular risk factors
5.            Project 33 Multi-site EMR surveillance and clinical decision support for prophylaxis
Members Role Technical Expertise GT Username GT Email (non-alias) Preferred Email GT Github Username Location IP Restrictions
Betsey Conners Developer Python, JavaScript and Java, Cross Platform Mobile app development bconners12 bconners12@gatech.edu bconners12@gatech.edu bconners12 Berlin, Germany None
Bob Ghoman Project Manager Workflow/Process Optimization, Project Management, Communications, Python, Ruby, APIs boghoman4 boghoman4@gatech.edu butterfingers@hotmail.com boghoman4 New York, New York None
Susie Sue Developer Software Data/ML/Visualization susiesue susiesue@gatech.edu susiesue@gatech.edu susiesue Georgia, US None
Mattia Kodinsky QA Manager and Developer Python, R, SQL; Healthcare knowledge with MIMIC and HER; ML Deep Learning Experience. mkodinsky35 mkodinsky35@gatech.edu mkodinsky@yahoo.com mkodinsky35 Madrid, Spain None
George Brown Developer Python, SQL, sysadmin, some java gbrown45 gbrown45@gatech.edu gbrown27@gmail.com gbrown45 Dublin, Ireland None
Doug Williams Project Manager Python, JavaScript and Java, Cross Platform Mobile app development dougwill9 dougwill9@gatech.edu doug.will@gatech.edu dougwill9 Cape Town, SA None
Meeting Times (Daily) Monday – Wednesday, 12:00 – 13:00 ET
Primary Form of Contact Slack https://omscseuroteam.slack.com
Secondary form of contact Email/Hangouts

(…and so on…)

 **Part of the Project Bidding Process.