What happens at each stage
Over two semesters, teams take a clinician's unmet problem through design reviews to a tested prototype. Schedule proposed.
August
Problem intake
Clinicians submit unmet problems from their own practice. The chapter reviews each one for whether a student team could make real progress in two semesters.
September
Team formation
Students from medicine, engineering, business, and design form teams around the problems that survived review.
October
Design Review 0
Teams present the problem itself: who it affects, how often, what currently happens, and where the current approach fails. No solutions yet.
January
Design Review 1
Teams present candidate approaches against explicit design requirements, and the evidence behind choosing one.
March
Design Review 2
Teams present a working prototype and what testing it revealed, including what did not work.
April
Expo
Teams present their work publicly to clinicians, faculty, and invited guests.
Time commitment
Teams meet weekly and present at each design review. Everyone on a team is carrying a full course load alongside it; the chapter will publish the expected hours once the first cycle has run and there is a real number to give.
Weekly
One team meeting
Plus the work between them.
Per review
One presentation
Prepared and presented by the team.
Overall
Two semesters
One cycle, across the fall and spring semesters.
Two ways in
The program only runs if both halves show up.
Clinicians
Bring a problem
You do not need a solution in mind. The problem is the contribution, and the form explains what makes one worth a team's year.
Students
Join a team
Medicine, engineering, business, and design. What each discipline contributes, and when applications open, are on the join page.